dns.pizza

Renewal History

fenerbahce.org

fenerbahce.org has been renewed 12 times, usually 1 year at a time, about 3 months before expiry. The longest single renewal was 5 years, around 2025, out to 2030. No near-death on record.

Renewals on record
12
Longest renewal
5 years
Expires
Apr 26, 2030
as of the latest snapshot
Snapshots
214
2011–2026

Every renewal, newest first

  1. 2025
    between Apr 9, 2025 and Apr 26, 2025
    +5 yearsexpiry Apr 26, 2025 → Apr 26, 2030Around expiry
    snapshots too far apart to say how early
    Registry confirmed an explicit renewal
  2. 2024
    between Jan 18, 2024 and Feb 20, 2024
    +1 yearexpiry Apr 26, 2024 → Apr 26, 2025Early
    2 to 3 months before expiry
    Transferred: Register.com, Inc. → IHS Telekom, Inc.
  3. 2023
    between Apr 11, 2023 and May 15, 2023
    +1 yearexpiry Apr 26, 2023 → Apr 26, 2024Around expiry
    snapshots too far apart to say how early
    Registry auto-renew
  4. 2022
    between Apr 12, 2022 and May 20, 2022
    +1 yearexpiry Apr 26, 2022 → Apr 26, 2023Around expiry
    snapshots too far apart to say how early
    Registry auto-renew
  5. 2021
    between Apr 1, 2021 and May 30, 2021
    +1 yearexpiry Apr 26, 2021 → Apr 26, 2022Around expiry
    snapshots too far apart to say how early
    Registry auto-renew
  6. 2020
    between Apr 4, 2020 and May 17, 2020
    +1 yearexpiry Apr 26, 2020 → Apr 26, 2021Around expiry
    snapshots too far apart to say how early
    Registry auto-renew
  7. 2019
    between Feb 15, 2019 and Aug 6, 2019
    +1 yearexpiry Apr 26, 2019 → Apr 26, 2020Around expiry
    snapshots too far apart to say how early
  8. 2018
    between Apr 19, 2018 and May 5, 2018
    +1 yearexpiry Apr 26, 2018 → Apr 26, 2019Around expiry
    snapshots too far apart to say how early
    Registry auto-renew
  9. 2017
    between Apr 13, 2017 and May 21, 2017
    +1 yearexpiry Apr 26, 2017 → Apr 26, 2018Around expiry
    snapshots too far apart to say how early
    Registry auto-renew
  10. 2016
    between Apr 8, 2014 and Jul 2, 2016
    +3 yearsexpiry Apr 26, 2014 → Apr 26, 2017Around expiry
    snapshots too far apart to say how early
  11. 2014
    between May 6, 2012 and Feb 26, 2014
    +1 yearexpiry Apr 26, 2013 → Apr 26, 2014Around expiry
    snapshots too far apart to say how early
  12. 2012
    between Feb 12, 2012 and May 6, 2012
    +1 yearexpiry Apr 26, 2012 → Apr 26, 2013Around 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: 214 snapshots of fenerbahce.org from the who.is WHOIS/RDAP archive, 2011-07-19 to 2026-05-12. Ledger built 2026-09-27.

Back to fenerbahce.org report