dns.pizza

Renewal History

dk.ru

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

Renewals on record
17
Longest renewal
1 year
Expires
Aug 31, 2026
as of the latest snapshot
Snapshots
103
2009–2026

Every renewal, newest first

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

Back to dk.ru report