dns.pizza

Renewal History

blizko.ru

blizko.ru has been renewed 17 times, usually 1 year at a time, about 4 weeks before expiry. No near-death on record.

Renewals on record
17
Longest renewal
1 year
Expires
Nov 28, 2026
as of the latest snapshot
Snapshots
111
2009–2026

Every renewal, newest first

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

Back to blizko.ru report