dns.pizza

Renewal History

beeline.ru

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

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

Every renewal, newest first

  1. 2025
    between Aug 15, 2025 and Sep 4, 2025
    +1 yearexpiry Aug 31, 2025 → Aug 31, 2026Around expiry
    snapshots too far apart to say how early
  2. 2024
    between Aug 28, 2024 and Sep 30, 2024
    +1 yearexpiry Aug 31, 2024 → Aug 31, 2025Around expiry
    snapshots too far apart to say how early
  3. 2023
    between Aug 18, 2023 and Sep 11, 2023
    +1 yearexpiry Aug 31, 2023 → Aug 31, 2024Around expiry
    snapshots too far apart to say how early
  4. 2022
    between Aug 1, 2022 and Sep 6, 2022
    +1 yearexpiry Aug 31, 2022 → Aug 31, 2023Around expiry
    snapshots too far apart to say how early
  5. 2021
    between Aug 20, 2021 and Sep 19, 2021
    +1 yearexpiry Aug 31, 2021 → Aug 31, 2022Around expiry
    snapshots too far apart to say how early
  6. 2020
    between Aug 2, 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 Aug 12, 2019 and Oct 8, 2019
    +1 yearexpiry Aug 31, 2019 → Aug 31, 2020Around expiry
    snapshots too far apart to say how early
  8. 2018
    between Jul 17, 2018 and Aug 20, 2018
    +1 yearexpiry Aug 31, 2018 → Aug 31, 2019Early
    2 to 6 weeks before expiry
  9. 2017
    between Jul 12, 2017 and Sep 17, 2017
    +1 yearexpiry Aug 31, 2017 → Aug 31, 2018Around expiry
    snapshots too far apart to say how early
  10. 2016
    between Sep 3, 2016 and Sep 21, 2016
    +1 yearexpiry Sep 1, 2016 → Sep 1, 2017In grace period
    up to 3 weeks after expiry
  11. 2015
    between Aug 16, 2015 and Sep 2, 2015
    +1 yearexpiry Sep 1, 2015 → Sep 1, 2016Around expiry
    snapshots too far apart to say how early
  12. 2014
    between Aug 2, 2014 and Aug 17, 2014
    +1 yearexpiry Sep 1, 2014 → Sep 1, 2015Early
    2 to 4 weeks before expiry
  13. 2013
    between Aug 13, 2013 and Aug 19, 2013
    +1 yearexpiry Sep 1, 2013 → Sep 1, 2014Early
    2 to 3 weeks before expiry
  14. 2012
    between Aug 3, 2012 and Aug 17, 2012
    +1 yearexpiry Sep 1, 2012 → Sep 1, 2013Early
    2 to 4 weeks before expiry
  15. 2011
    between Aug 8, 2011 and Aug 18, 2011
    +1 yearexpiry Sep 1, 2011 → Sep 1, 2012Early
    2 to 3 weeks before expiry
  16. 2010
    between Aug 9, 2010 and Aug 19, 2010
    +1 yearexpiry Sep 1, 2010 → Sep 1, 2011Early
    2 to 3 weeks before expiry
  17. 2009
    between Aug 10, 2009 and Aug 22, 2009
    +1 yearexpiry Sep 1, 2009 → Sep 1, 2010Early
    1 to 3 weeks 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: 564 snapshots of beeline.ru from the who.is WHOIS/RDAP archive, 2009-01-04 to 2026-05-12. Ledger built 2026-09-27.

Back to beeline.ru report