dns.pizza

Renewal History

truecaller.com

truecaller.com has been renewed 16 times, usually 1 year at a time, about 5 weeks before expiry. The longest single renewal was 9 years, around 2025, out to 2035. No near-death on record.

Renewals on record
16
Longest renewal
9 years
Expires
Jan 26, 2035
as of the latest snapshot
Snapshots
643
2009–2026

Every renewal, newest first

  1. 2025
    between Apr 25, 2025 and May 25, 2025
    +9 yearsexpiry Jan 26, 2026 → Jan 26, 2035Early
    8 to 9 months before expiry
  2. 2024
    between Dec 19, 2024 and Dec 23, 2024
    +1 yearexpiry Jan 26, 2025 → Jan 26, 2026Early
    5 weeks before expiry
  3. 2024
    between Dec 8, 2023 and Jan 7, 2024
    +1 yearexpiry Jan 26, 2024 → Jan 26, 2025Early
    3 to 7 weeks before expiry
  4. 2022
    between Dec 8, 2022 and Dec 30, 2022
    +1 yearexpiry Jan 26, 2023 → Jan 26, 2024Early
    4 to 7 weeks before expiry
  5. 2022
    between Dec 20, 2021 and Jan 3, 2022
    +1 yearexpiry Jan 26, 2022 → Jan 26, 2023Early
    3 to 5 weeks before expiry
    Registry confirmed an explicit renewal
  6. 2020
    between Dec 20, 2020 and Dec 24, 2020
    +1 yearexpiry Jan 26, 2021 → Jan 26, 2022Early
    5 weeks before expiry
    Registry confirmed an explicit renewal
  7. 2019
    between Dec 10, 2019 and Dec 28, 2019
    +1 yearexpiry Jan 26, 2020 → Jan 26, 2021Early
    4 to 7 weeks before expiry
    Registry confirmed an explicit renewal
  8. 2019
    between Dec 22, 2018 and Jan 11, 2019
    +1 yearexpiry Jan 26, 2019 → Jan 26, 2020Early
    2 to 5 weeks before expiry
    Registry confirmed an explicit renewal
  9. 2017
    between May 1, 2017 and May 9, 2017
    +1 yearexpiry Jan 26, 2018 → Jan 26, 2019Early
    9 months before expiry
    Transferred: Ascio Technologies, Inc → Amazon Registrar, Inc.
  10. 2016
    between Dec 17, 2016 and Dec 27, 2016
    +1 yearexpiry Jan 26, 2017 → Jan 26, 2018Early
    4 to 6 weeks before expiry
  11. 2016
    between Jul 14, 2014 and Jun 27, 2016
    +2 yearsexpiry Jan 26, 2015 → Jan 26, 2017Around expiry
    snapshots too far apart to say how early
    Transferred: Loopia (REG-3) → Ascio Technologies, Inc
  12. 2014
    between Jan 24, 2014 and Jan 26, 2014
    +1 yearexpiry Jan 26, 2014 → Jan 26, 2015Around expiry
    snapshots too far apart to say how early
  13. Jan 25, 2013
    +1 yearexpiry Jan 26, 2013 → Jan 26, 2014Early
    1 to 2 days before expiry
  14. 2012
    between Jan 13, 2012 and Feb 16, 2012
    +1 yearexpiry Jan 26, 2012 → Jan 26, 2013Around expiry
    snapshots too far apart to say how early
  15. 2011
    between May 14, 2010 and May 9, 2011
    +1 yearexpiry Jan 26, 2011 → Jan 26, 2012Around expiry
    snapshots too far apart to say how early
    Transferred: REGISTRAR-3 → Loopia (REG-3)
  16. 2010
    between Jul 15, 2009 and May 14, 2010
    +1 yearexpiry Jan 26, 2010 → Jan 26, 2011Around 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: 643 snapshots of truecaller.com from the who.is WHOIS/RDAP archive, 2009-07-07 to 2026-05-14. Ledger built 2026-09-27.

Back to truecaller.com report