blogverde.shop
Lineage
Apr 3, 2018 → Oct 26, 2026DNS at mysecurecloudhost.com · 3 nameserver changes seen.
What changed
- DNS moved to mysecurecloudhost.com between Oct 25, 2026 and Oct 26, 2026ns39.domaincontrol.com, ns40.domaincontrol.com → ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com, ns4.mysecurecloudhost.com.
- DNS moved to GoDaddy between Sep 18, 2026 and Oct 25, 2026ns1.dns-expired.com, ns2.dns-expired.com → ns39.domaincontrol.com, ns40.domaincontrol.com.
- Missing from the zone file, then back between Sep 18, 2026 and Oct 25, 2026Listed on 2026-09-18, missing from the next held snapshot, listed again on 2026-10-25. A registry hold also removes a name, so this is not proof it was dropped.
- DNS moved to dns-expired.com between Aug 6, 2026 and Aug 7, 2026grannbo.ns.cloudflare.com, oswald.ns.cloudflare.com → ns1.dns-expired.com, ns2.dns-expired.com.
Nameservers, registry zone files: 84 .shop zone-file snapshots held, 2018-04-03 to 2026-10-26.
Nameservers, WHOIS snapshots: 1 WHOIS/RDAP snapshots that listed nameservers, 2026-01-07 to 2026-01-07 (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 blogverde.shop changes?
Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.