twitter.network
IPv6
Not checked yet. aaaa.bot has no recent IPv6 result for twitter.network. Run the check on aaaa.bot →
See where it lives on the IPv4 map →
Lineage
Our records: Dec 18, 2015 → Nov 11, 2026DNS at dyna-ns.net · 2 nameserver changes seen. These dates are when our records begin, not when the domain was registered.
DNS provider
- Oracle DynDec 2015 – Apr 2018
- abovedomains.comFeb 2026
- dyna-ns.netNOWSeen from Nov 2026
What changed
- DNS moved to dyna-ns.net between Feb 9, 2026 and Nov 9, 2026ns15.abovedomains.com, ns16.abovedomains.com → ns1.dyna-ns.net, ns2.dyna-ns.net. Old set last seen in WHOIS on 2026-02-09; new set first in the registry zone file on 2026-11-09.
- Missing from the zone file, then back between Apr 17, 2018 and Nov 9, 2026Listed on 2018-04-17, missing from the next held snapshot, listed again on 2026-11-09. A registry hold also removes a name, so this is not proof it was dropped.
- DNS moved to abovedomains.com between Apr 17, 2018 and Feb 9, 2026ns1.p34.dynect.net, ns2.p34.dynect.net, ns3.p34.dynect.net, ns4.p34.dynect.net → ns15.abovedomains.com, ns16.abovedomains.com. Old set last in the registry zone file on 2018-04-17; new set first seen in WHOIS on 2026-02-09.
Solid bar: the stretch we observed that name. Dot: a single sighting. Dotted line: no record between sightings of the same name. Nothing is drawn between different names.
DNS provider, registry zone files: 167 .network zone-file snapshots held, 2015-12-18 to 2026-11-11.
DNS provider, WHOIS snapshots: 1 WHOIS/RDAP snapshots that listed nameservers, 2026-02-09 to 2026-02-09 (who.is archive). Both sources feed one row per provider (hover a bar to see which); a change is placed between the nearest observations on either side, and where the two sources disagree, both are listed under What changed.
Want to know when twitter.network changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.