Renewal History
ifconfig.me
ifconfig.me has been renewed 7 times, usually 1 year at a time, about 4 weeks before expiry. The longest single renewal was 10 years, around 2025, out to 2026. It came close to lapsing once.
Every renewal, newest first
- 2026between Apr 6, 2026 and May 13, 2026+1 yearexpiry Apr 18, 2026 → Apr 18, 2027Around expirysnapshots too far apart to say how earlyRegistry auto-renew
- 2025between Jul 11, 2016 and May 2, 2025+10 yearsexpiry Apr 18, 2016 → Apr 18, 2026Late, past grace3 to 108 months after expiryTransferred: GMO Internet, Inc. R73-ME (49) → GoDaddy.com, LLCRegistry auto-renew
- 2015between Mar 17, 2015 and Mar 23, 2015+1 yearexpiry Apr 18, 2015 → Apr 18, 2016Early4 to 5 weeks before expiryRegistry confirmed an explicit renewal
- 2014between Mar 11, 2014 and Apr 5, 2014+1 yearexpiry Apr 18, 2014 → Apr 18, 2015Early2 to 5 weeks before expiry
- 2013between Nov 22, 2012 and Jan 30, 2013+1 yearexpiry Apr 18, 2013 → Apr 18, 2014Early3 to 5 months before expiry
- 2012between Oct 19, 2011 and Feb 27, 2012+1 yearexpiry Apr 18, 2012 → Apr 18, 2013Early2 to 6 months before expiry
- 2011between Oct 30, 2010 and Aug 14, 2011+1 yearexpiry Apr 18, 2011 → Apr 18, 2012Around 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: 89 snapshots of ifconfig.me from the who.is WHOIS/RDAP archive, 2010-10-30 to 2026-05-13. Ledger built 2026-09-27.