dns.pizza

Renewal History

idfacebook.com

idfacebook.com has been renewed 6 times, usually 1 year at a time. The longest single renewal was 3 years, around 2016, out to 2017. No near-death on record.

Renewals on record
6
Longest renewal
3 years
Expires
Apr 11, 2025
as of the latest snapshot
Snapshots
20
2009–2024
Close calls
0
4 drops & re-registration

Every renewal, newest first

  1. 2024
    between Dec 18, 2023 and Sep 24, 2024
    Re-registeredexpiry Jan 6, 2024 → Apr 11, 2025Dropped & re-registered
    a new registration, not a renewal
    Transferred: DREAMHOST → Name.com, Inc.
  2. 2023
    between Jul 24, 2020 and Dec 18, 2023
    Re-registeredexpiry Jul 21, 2021 → Jan 6, 2024Dropped & re-registered
    a new registration, not a renewal
    Transferred: Sav.com → DREAMHOST
  3. 2020
    between May 19, 2020 and Jul 24, 2020
    Re-registeredexpiry May 15, 2020 → Jul 21, 2021Dropped & re-registered
    a new registration, not a renewal
    Transferred: XINNET TECHNOLOGY CORPORATION → Sav.com
  4. 2019
    between Nov 1, 2018 and Jun 29, 2019
    +1 yearexpiry May 15, 2019 → May 15, 2020Around expiry
    snapshots too far apart to say how early
  5. 2018
    between Aug 12, 2017 and Jun 25, 2018
    +1 yearexpiry May 15, 2018 → May 15, 2019Around expiry
    snapshots too far apart to say how early
  6. 2017
    between Aug 27, 2016 and Aug 12, 2017
    Re-registeredexpiry Feb 25, 2017 → May 15, 2018Dropped & re-registered
    a new registration, not a renewal
    Transferred: Dinahosting s.l. → XINNET TECHNOLOGY CORPORATION
  7. 2016
    between Jul 4, 2013 and Aug 27, 2016
    +3 yearsexpiry May 16, 2014 → Feb 25, 2017Around expiry
    snapshots too far apart to say how early
    Transferred: eName Technology Co.,Ltd. → Dinahosting s.l.
  8. 2013
    between May 18, 2011 and May 16, 2013
    +2 yearsexpiry May 16, 2012 → May 16, 2014Around expiry
    snapshots too far apart to say how early
  9. 2011
    between Nov 23, 2010 and May 18, 2011
    +1 yearexpiry May 16, 2011 → May 16, 2012Around expiry
    snapshots too far apart to say how early
  10. 2010
    between Feb 8, 2010 and Nov 23, 2010
    +1 yearexpiry Mar 7, 2010 → May 16, 2011Around expiry
    snapshots 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: 20 snapshots of idfacebook.com from the who.is WHOIS/RDAP archive, 2009-03-09 to 2024-09-24. Ledger built 2026-09-27.

Back to idfacebook.com report