Renewal History
xn--v3cfhq6bo4n.com
xn--v3cfhq6bo4n.com has been renewed 4 times, usually 2 years at a time. No near-death on record.
Every renewal, newest first
- 2024between Jul 24, 2020 and Jan 19, 2024Re-registeredexpiry Mar 31, 2021 → Aug 7, 2024Dropped & re-registereda new registration, not a renewalTransferred: DYNADOT LLC → GMO INTERNET, INC.
- 2020between Sep 15, 2018 and Jul 24, 2020+2 yearsexpiry Mar 31, 2019 → Mar 31, 2021Around expirysnapshots too far apart to say how early
- 2018between May 21, 2014 and Sep 15, 2018Re-registeredexpiry Jan 10, 2015 → Mar 31, 2019Dropped & re-registereda new registration, not a renewalTransferred: FABULOUS.COM PTY LTD. → DYNADOT LLC
- 2013between Sep 19, 2013 and Dec 14, 2013+1 yearexpiry Jan 10, 2014 → Jan 10, 2015Early1 to 4 months before expiry
- 2013between Mar 18, 2012 and Mar 8, 2013+1 yearexpiry Jan 10, 2013 → Jan 10, 2014Around expirysnapshots too far apart to say how early
- 2012between Aug 11, 2010 and Mar 18, 2012+2 yearsexpiry Jan 10, 2011 → Jan 10, 2013Around expirysnapshots too far apart to say how early
How this is worked out. Each renewal is a forward jump in the registry’s expiry date between two WHOIS or RDAP snapshots. The size of the jump is the number of years paid for. The renewal happened somewhere between the two snapshot dates, so how early or late it was is a range; when the snapshots are far apart, it is not stated.
For .com and .net the registry itself extends the expiry on the day it lapses and gives the registrar 45 days to pay or delete, so a jump right at expiry is not proof the owner paid. The ledger marks renewals the registry flagged as explicit, and near-deaths where it later showed a redemption or pending-delete status.
Source: 15 snapshots of xn--v3cfhq6bo4n.com from the who.is WHOIS/RDAP archive, 2010-08-11 to 2024-01-19. Ledger built 2026-09-27.