Renewal History
tapgoogle.com
tapgoogle.com has been renewed 3 times, usually 1 year at a time, about 2.5 days after expiry. It came close to lapsing once.
Every renewal, newest first
- 2025between May 7, 2019 and Jun 2, 2025Re-registeredexpiry Apr 22, 2019 → Mar 3, 2026Dropped & re-registereda new registration, not a renewalTransferred: Onlinenic Inc → GoDaddy.com, LLCRegistry showed it unregistered
- 2018between Mar 4, 2018 and Jun 27, 2018+1 yearexpiry Apr 22, 2018 → Apr 22, 2019Around expirysnapshots too far apart to say how early
- 2017between Jul 3, 2012 and May 23, 2017Re-registeredexpiry Dec 27, 2012 → Apr 22, 2018Dropped & re-registereda new registration, not a renewal
- 2012between May 27, 2010 and Mar 2, 2012Re-registeredexpiry Oct 9, 2010 → Dec 27, 2012Dropped & re-registereda new registration, not a renewal
- 2010between Sep 22, 2009 and May 20, 2010+1 yearexpiry Oct 9, 2009 → Oct 9, 2010Around expirysnapshots too far apart to say how early
- Oct 12, 2008+1 yearexpiry Oct 9, 2008 → Oct 9, 2009In grace period2 to 3 days after expiry
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: 48 snapshots of tapgoogle.com from the who.is WHOIS/RDAP archive, 2007-05-20 to 2025-07-04. Ledger built 2026-09-27.