dns.pizza

Renewal History

pulscen.ru

pulscen.ru has been renewed 16 times, usually 1 year at a time. No near-death on record.

Renewals on record
16
Longest renewal
1 year
Expires
May 25, 2026
as of the latest snapshot
Snapshots
183
2009–2026

Every renewal, newest first

  1. 2025
    between Apr 11, 2025 and Jul 31, 2025
    +1 yearexpiry May 25, 2025 → May 25, 2026Around expiry
    snapshots too far apart to say how early
  2. 2024
    between Apr 30, 2024 and May 25, 2024
    +1 yearexpiry May 25, 2024 → May 25, 2025Around expiry
    snapshots too far apart to say how early
  3. 2023
    between Apr 3, 2023 and May 30, 2023
    +1 yearexpiry May 25, 2023 → May 25, 2024Around expiry
    snapshots too far apart to say how early
  4. 2022
    between May 4, 2022 and Jun 9, 2022
    +1 yearexpiry May 25, 2022 → May 25, 2023Around expiry
    snapshots too far apart to say how early
  5. 2021
    between May 15, 2021 and Jun 27, 2021
    +1 yearexpiry May 25, 2021 → May 25, 2022Around expiry
    snapshots too far apart to say how early
  6. 2020
    between May 21, 2020 and Jul 21, 2020
    +1 yearexpiry May 25, 2020 → May 25, 2021Around expiry
    snapshots too far apart to say how early
  7. 2019
    between May 19, 2019 and Jun 28, 2019
    +1 yearexpiry May 25, 2019 → May 25, 2020Around expiry
    snapshots too far apart to say how early
  8. 2018
    between Oct 5, 2017 and Jun 23, 2018
    +1 yearexpiry May 25, 2018 → May 25, 2019Around expiry
    snapshots too far apart to say how early
  9. 2017
    between Apr 17, 2017 and Oct 5, 2017
    +1 yearexpiry May 25, 2017 → May 25, 2018Around expiry
    snapshots too far apart to say how early
  10. 2016
    between Apr 6, 2016 and Jul 7, 2016
    +1 yearexpiry May 26, 2016 → May 26, 2017Around expiry
    snapshots too far apart to say how early
  11. 2015
    between May 14, 2015 and Jun 10, 2015
    +1 yearexpiry May 26, 2015 → May 26, 2016Around expiry
    snapshots too far apart to say how early
  12. 2014
    between Apr 23, 2014 and Jun 26, 2014
    +1 yearexpiry May 26, 2014 → May 26, 2015Around expiry
    snapshots too far apart to say how early
  13. 2013
    between Apr 23, 2013 and May 29, 2013
    +1 yearexpiry May 26, 2013 → May 26, 2014Around expiry
    snapshots too far apart to say how early
  14. 2012
    between May 9, 2012 and Jun 14, 2012
    +1 yearexpiry May 26, 2012 → May 26, 2013Around expiry
    snapshots too far apart to say how early
  15. 2011
    between Apr 10, 2011 and Jun 5, 2011
    +1 yearexpiry May 26, 2011 → May 26, 2012Around expiry
    snapshots too far apart to say how early
  16. 2010
    between Mar 12, 2010 and May 31, 2010
    +1 yearexpiry May 26, 2010 → May 26, 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: 183 snapshots of pulscen.ru from the who.is WHOIS/RDAP archive, 2009-08-08 to 2026-05-17. Ledger built 2026-09-27.

Back to pulscen.ru report