dns.pizza

Renewal History

auto.ru

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

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

Every renewal, newest first

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

Back to auto.ru report