dns.pizza

Renewal History

reverse.it

reverse.it has been renewed 14 times, usually 1 year at a time. The longest single renewal was 2 years, around 2015, out to 2016. No near-death on record.

Renewals on record
14
Longest renewal
2 years
Expires
May 9, 2026
as of the latest snapshot
Snapshots
57
2010–2026

Every renewal, newest first

  1. 2025
    between Feb 7, 2025 and Jul 18, 2025
    +1 yearexpiry May 9, 2025 → May 9, 2026Around expiry
    snapshots too far apart to say how early
  2. 2024
    between Apr 5, 2024 and Aug 3, 2024
    +1 yearexpiry May 9, 2024 → May 9, 2025Around expiry
    snapshots too far apart to say how early
  3. 2023
    between May 3, 2023 and Jun 9, 2023
    +1 yearexpiry May 9, 2023 → May 9, 2024Around expiry
    snapshots too far apart to say how early
  4. 2022
    between Feb 22, 2022 and Aug 27, 2022
    +1 yearexpiry May 9, 2022 → May 9, 2023Around expiry
    snapshots too far apart to say how early
  5. 2021
    between Apr 24, 2021 and Jun 8, 2021
    +1 yearexpiry May 9, 2021 → May 9, 2022Around expiry
    snapshots too far apart to say how early
  6. 2020
    between May 3, 2020 and Sep 12, 2020
    +1 yearexpiry May 9, 2020 → May 9, 2021Around expiry
    snapshots too far apart to say how early
  7. 2018
    between Jun 21, 2018 and Nov 23, 2018
    +1 yearexpiry Aug 18, 2018 → Aug 18, 2019Around expiry
    snapshots too far apart to say how early
  8. 2017
    between Jul 3, 2017 and Sep 29, 2017
    +1 yearexpiry Aug 18, 2017 → Aug 18, 2018Around expiry
    snapshots too far apart to say how early
  9. 2016
    between Mar 7, 2016 and Nov 29, 2016
    +1 yearexpiry Aug 18, 2016 → Aug 18, 2017Around expiry
    snapshots too far apart to say how early
  10. 2015
    between Mar 21, 2014 and Aug 27, 2015
    +2 yearsexpiry Feb 16, 2015 → Aug 18, 2016Around expiry
    snapshots too far apart to say how early
  11. 2014
    between Jan 25, 2014 and Mar 21, 2014
    +1 yearexpiry Feb 16, 2014 → Feb 16, 2015Around expiry
    snapshots too far apart to say how early
  12. 2014
    between Nov 8, 2012 and Jan 25, 2014
    +1 yearexpiry Feb 16, 2013 → Feb 16, 2014Around expiry
    snapshots too far apart to say how early
  13. 2012
    between Jun 28, 2011 and Aug 11, 2012
    +1 yearexpiry Feb 16, 2012 → Feb 16, 2013Around expiry
    snapshots too far apart to say how early
  14. 2011
    between Dec 6, 2010 and Jun 28, 2011
    +1 yearexpiry Feb 18, 2011 → Feb 16, 2012Around 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: 57 snapshots of reverse.it from the who.is WHOIS/RDAP archive, 2010-12-01 to 2026-04-24. Ledger built 2026-09-27.

Back to reverse.it report