robox.cloud
IPv6
Not checked yet. aaaa.bot has no recent IPv6 result for robox.cloud. Run the check on aaaa.bot →
Lineage
Our records: Jan 21, 2016 → Nov 1, 2026Oldest registry snapshot we hold: 2023 · 1 renewal on record · DNS at afternic.com + verify.hn · 2 nameserver changes seen. These dates are when our records begin, not when the domain was registered.
What changed
- Missing from the zone file, then back between Sep 25, 2026 and Oct 31, 2026Listed on 2026-09-25, missing from the next held snapshot, listed again on 2026-10-31. A registry hold also removes a name, so this is not proof it was dropped.
- DNS moved to afternic.com + verify.hn between Sep 25, 2026 and Oct 31, 2026ns1.dns-expired.com, ns2.dns-expired.com → ns1.afternic.com, ns2.afternic.com, verification-e7ktf2ehupufe4sbe7xxk3.ns101.verify.hn.
- DNS moved to dns-expired.com between Aug 13, 2026 and Aug 14, 2026ns1.afternic.com, ns2.afternic.com → ns1.dns-expired.com, ns2.dns-expired.com.
- Renewed +2 years between Apr 8, 2023 and Sep 26, 2024Expiry moved from 2023-06-04 to 2025-06-04, at Regional Network Information Center, JSC dba RU-CENTER.
Registrar and renewals: 3 WHOIS/RDAP snapshots, 2023-04-08 to 2024-11-27 (ledger built 2026-09-27). Every renewal
Nameservers, registry zone files: 164 .cloud zone-file snapshots held, 2016-01-21 to 2026-11-01.
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 robox.cloud changes?
Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.