dns.pizza

Renewal History

fascebook.com

fascebook.com has been renewed 13 times, usually 1 year at a time, about 5 months before expiry. The longest single renewal was 3 years, around 2016, out to 2017. No near-death on record.

Renewals on record
13
Longest renewal
3 years
Expires
Jul 21, 2026
as of the latest snapshot
Snapshots
143
2009–2026

Every renewal, newest first

  1. 2025
    between Jul 9, 2025 and Aug 9, 2025
    +1 yearexpiry Jul 21, 2025 → Jul 21, 2026Around expiry
    snapshots too far apart to say how early
  2. 2024
    between Jun 10, 2024 and Jul 11, 2024
    +1 yearexpiry Jul 21, 2024 → Jul 21, 2025Early
    1 to 6 weeks before expiry
  3. 2023
    between Apr 3, 2023 and May 15, 2023
    +1 yearexpiry Jul 21, 2023 → Jul 21, 2024Early
    2 to 4 months before expiry
  4. 2022
    between Jul 15, 2022 and Aug 19, 2022
    +1 yearexpiry Jul 21, 2022 → Jul 21, 2023Around expiry
    snapshots too far apart to say how early
  5. 2021
    between Jan 25, 2021 and Mar 2, 2021
    +1 yearexpiry Jul 21, 2021 → Jul 21, 2022Early
    5 to 6 months before expiry
    Transferred: GoDaddy.com, LLC → DYNADOT LLC
  6. 2020
    between Dec 2, 2019 and Jan 7, 2020
    +1 yearexpiry Jul 21, 2020 → Jul 21, 2021Early
    6 to 8 months before expiry
  7. 2019
    between Dec 9, 2018 and Jan 15, 2019
    +1 yearexpiry Jul 21, 2019 → Jul 21, 2020Early
    6 to 7 months before expiry
  8. 2018
    between Feb 14, 2017 and Jun 17, 2018
    +2 yearsexpiry Jul 21, 2017 → Jul 21, 2019Around expiry
    snapshots too far apart to say how early
  9. 2016
    between Dec 12, 2013 and Aug 4, 2016
    +3 yearsexpiry Jul 21, 2014 → Jul 21, 2017Around expiry
    snapshots too far apart to say how early
    Transferred: Domain.com → GoDaddy.com, LLC
  10. 2013
    between Nov 16, 2012 and Dec 12, 2013
    +1 yearexpiry Jul 21, 2013 → Jul 21, 2014Around expiry
    snapshots too far apart to say how early
  11. 2012
    between Sep 4, 2011 and Jan 22, 2012
    +1 yearexpiry Jul 21, 2012 → Jul 21, 2013Early
    6 to 11 months before expiry
  12. 2011
    between Jan 4, 2011 and Apr 4, 2011
    +1 yearexpiry Jul 21, 2011 → Jul 21, 2012Early
    4 to 7 months before expiry
  13. 2010
    between Oct 14, 2009 and Aug 3, 2010
    +1 yearexpiry Jul 21, 2010 → Jul 21, 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: 143 snapshots of fascebook.com from the who.is WHOIS/RDAP archive, 2009-10-14 to 2026-02-28. Ledger built 2026-09-27.

Back to fascebook.com report