ax-dc-msedge.net
IPv6
Not checked yet. aaaa.bot has no recent IPv6 result for ax-dc-msedge.net. Run the check on aaaa.bot →
Lineage
Our records: Oct 18, 2013 → Nov 1, 2026Oldest registry snapshot we hold: 2024 · 2 renewals on record · DNS at ax-dc-msedge.net · 1 nameserver change seen. These dates are when our records begin, not when the domain was registered.
What changed
- Renewed +1 year between Jan 6, 2026 and Feb 11, 2026Expiry moved from 2026-03-06 to 2027-03-06, at MarkMonitor, Inc.
- Renewed +1 year between Sep 6, 2024 and Jul 15, 2025Expiry moved from 2025-03-06 to 2026-03-06, at MarkMonitor, Inc.
- DNS moved to ax-dc-msedge.net between Mar 19, 2024 and Sep 6, 2024ns1-32.azure-dns.com, ns2-32.azure-dns.net, ns3-32.azure-dns.org, ns4-32.azure-dns.info → ns1.ax-dc-msedge.net, ns2.ax-dc-msedge.net, ns3.ax-dc-msedge.net, ns4.ax-dc-msedge.net. Old set last seen in WHOIS on 2024-03-19; new set first seen in WHOIS on 2024-09-06.
Registrar and renewals: 14 WHOIS/RDAP snapshots, 2024-03-19 to 2026-05-19 (ledger built 2026-09-27). Every renewal
Nameservers, registry zone files: 105 .net zone-file snapshots held, 2013-10-18 to 2026-11-01.
Nameservers, WHOIS snapshots: 9 WHOIS/RDAP snapshots that listed nameservers, 2024-03-19 to 2026-06-01 (who.is archive). A change is placed between the nearest observations on either side, from whichever source made them; where the two sources disagree, both are shown.
Hatched = the span we hold records for. A coloured bar runs only between observations that named the same registrar or operator; nothing is assumed in between.
Each mark sits at the first observation of the new state; its bracket runs back to the last observation of the old one.
Want to know when ax-dc-msedge.net changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.