IPv6
Not checked yet. aaaa.bot has no recent IPv6 result for aml.network. Run the check on aaaa.bot →
See where it lives on the IPv4 map →
Lineage
Our records: Dec 18, 2015 → Nov 13, 2026Oldest registry snapshot we hold: 2024 · 1 renewal on record · DNS at dns-redirect.com · 2 nameserver changes seen. These dates are when our records begin, not when the domain was registered.
Registrar
- Name.com, Inc.last seen Aug 2025Aug 2025
DNS provider
- GoDaddyDec 2015 – Apr 2018
- Name.comAug – Sep 2026
- dns-redirect.comNOWSeen from Nov 2026
What changed
- Missing from the zone file, then back between Sep 23, 2026 and Nov 12, 2026Listed on 2026-09-23, missing from the next held snapshot, listed again on 2026-11-12. A registry hold also removes a name, so this is not proof it was dropped.
- DNS moved to dns-redirect.com between Sep 23, 2026 and Nov 12, 2026ns1mpz.name.com, ns2gtx.name.com, ns3nrz.name.com, ns4ksy.name.com → ns1.dns-redirect.com, ns2.dns-redirect.com.
- DNS moved to Name.com between Apr 17, 2018 and Aug 5, 2026ns43.domaincontrol.com, ns44.domaincontrol.com → ns1mpz.name.com, ns2gtx.name.com, ns3nrz.name.com, ns4ksy.name.com.
- Renewed +1 year between Aug 5, 2025 and Aug 16, 2025Expiry moved from 2025-08-10 to 2026-08-10, at Name.com, Inc.
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.
Registrar and renewals: 34 WHOIS/RDAP snapshots, 2024-09-14 to 2026-04-06 (ledger built 2026-09-27). Every renewal
DNS provider, registry zone files: 169 .network zone-file snapshots held, 2015-12-18 to 2026-11-13.
Want to know when aml.network changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.