dns.pizza

Renewal History

azbyka.ru

azbyka.ru has been renewed 18 times, usually 1 year at a time, about 8 weeks before expiry. No near-death on record.

Renewals on record
18
Longest renewal
1 year
Expires
Apr 4, 2027
as of the latest snapshot
Snapshots
130
2009–2026

Every renewal, newest first

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

Back to azbyka.ru report