IPv6
Not checked yet. aaaa.bot has no recent IPv6 result for myq-cloud.com. Run the check on aaaa.bot →
Lineage
Our records: Oct 18, 2013 → Nov 2, 2026Oldest registry snapshot we hold: 2020 · 1 renewal on record · DNS at Amazon Route 53 · 1 nameserver change seen. These dates are when our records begin, not when the domain was registered.
Registrar
- Network Solutions, LLClast seen Oct 2022Jan 2021 – Oct 2022
DNS provider
- Microsoft Azure DNSJan 2020 – Jan 2026
- Amazon Route 53NOWSeen from May 2026
What changed
- DNS moved to Amazon Route 53 between Jan 21, 2026 and May 17, 2026ns1-07.azure-dns.com, ns2-07.azure-dns.net, ns3-07.azure-dns.org, ns4-07.azure-dns.info → ns-1396.awsdns-46.org, ns-1947.awsdns-51.co.uk, ns-28.awsdns-03.com, ns-568.awsdns-07.net. Old set last seen in WHOIS on 2026-01-21; new set first seen in WHOIS on 2026-05-17.
- Renewed +6 years between Jan 31, 2021 and Oct 18, 2022Expiry moved from 2021-11-27 to 2027-11-27, at Network Solutions, LLC.
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: 36 WHOIS/RDAP snapshots, 2020-01-09 to 2026-05-17 (ledger built 2026-09-27). Every renewal
DNS provider, registry zone files: 107 .com zone-file snapshots held, 2013-10-18 to 2026-11-02.
DNS provider, WHOIS snapshots: 25 WHOIS/RDAP snapshots that listed nameservers, 2020-01-09 to 2026-05-17 (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 myq-cloud.com changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.