dns.pizza

Renewal History

x-server.net

x-server.net has been renewed 12 times, usually 1 year at a time, about 5 months before expiry. The longest single renewal was 6 years, around 2019, out to 2019. No near-death on record.

Renewals on record
12
Longest renewal
6 years
Expires
Jun 11, 2027
as of the latest snapshot
Snapshots
60
2009–2026

Every renewal, newest first

  1. 2026
    between Jan 4, 2026 and Jan 21, 2026
    +1 yearexpiry Jun 11, 2026 → Jun 11, 2027Early
    5 months before expiry
  2. 2025
    between May 23, 2025 and Jun 7, 2025
    +1 yearexpiry Jun 11, 2025 → Jun 11, 2026Early
    1 to 3 weeks before expiry
  3. 2024
    between Jan 10, 2024 and Feb 11, 2024
    +1 yearexpiry Jun 11, 2024 → Jun 11, 2025Early
    4 to 5 months before expiry
  4. 2023
    between Nov 10, 2022 and Feb 6, 2023
    +1 yearexpiry Jun 11, 2023 → Jun 11, 2024Early
    4 to 7 months before expiry
  5. 2022
    between May 5, 2022 and Jun 23, 2022
    +1 yearexpiry Jun 11, 2022 → Jun 11, 2023Around expiry
    snapshots too far apart to say how early
  6. 2022
    between Nov 8, 2020 and Mar 5, 2022
    +1 yearexpiry Jun 11, 2021 → Jun 11, 2022Around expiry
    snapshots too far apart to say how early
  7. 2020
    between Feb 19, 2019 and Nov 8, 2020
    +2 yearsexpiry Jun 11, 2019 → Jun 11, 2021Around expiry
    snapshots too far apart to say how early
  8. 2019
    between Jun 29, 2012 and Feb 19, 2019
    +6 yearsexpiry Jun 11, 2013 → Jun 11, 2019Around expiry
    snapshots too far apart to say how early
    Transferred: CSL COMPUTER SERVICE LANGENBACH GMBH D/B/A JOKER.COM → Omnis Network, LLC
  9. 2012
    between Jan 29, 2012 and Jun 29, 2012
    +1 yearexpiry Jun 11, 2012 → Jun 11, 2013Around expiry
    snapshots too far apart to say how early
  10. 2011
    between May 5, 2011 and Sep 27, 2011
    +1 yearexpiry Jun 11, 2011 → Jun 11, 2012Around expiry
    snapshots too far apart to say how early
  11. 2011
    between Mar 22, 2010 and May 5, 2011
    +1 yearexpiry Jun 11, 2010 → Jun 11, 2011Around expiry
    snapshots too far apart to say how early
  12. 2009
    between Jun 7, 2009 and Jul 7, 2009
    +1 yearexpiry Jun 11, 2009 → Jun 11, 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: 60 snapshots of x-server.net from the who.is WHOIS/RDAP archive, 2009-05-02 to 2026-05-28. Ledger built 2026-09-27.

Back to x-server.net report