Renewal History

11111111111111111111111111111111111111111111111111111111111111.com

11111111111111111111111111111111111111111111111111111111111111.com has been renewed 6 times, usually 1 year at a time. It came close to lapsing 2 times.

Renewals on record
6
Longest renewal
1 year
Expires
Oct 15, 2025
as of the latest snapshot
Snapshots
45
2008–2025
Close calls
2
3 drops & re-registration

Every renewal, newest first

  1. 2024
    between Jul 25, 2024 and Nov 28, 2024
    +1 yearexpiry Oct 15, 2024 → Oct 15, 2025Around expiry
    snapshots too far apart to say how early
  2. 2024
    between May 10, 2023 and Jan 7, 2024
    +1 yearexpiry Oct 15, 2023 → Oct 15, 2024Around expiry
    snapshots too far apart to say how early
  3. 2022
    between Jul 26, 2022 and Nov 12, 2022
    +1 yearexpiry Oct 15, 2022 → Oct 15, 2023Around expiry
    snapshots too far apart to say how early
  4. 2021
    between Aug 22, 2021 and Dec 13, 2021
    Re-registeredexpiry Jul 28, 2021 → Oct 15, 2022Dropped & re-registered
    a new registration, not a renewal
    Transferred: NAMECHEAP INC → DYNADOT6 LLC
  5. 2020
    between Mar 20, 2020 and Aug 26, 2020
    Re-registeredexpiry Feb 4, 2020 → Jul 28, 2021Dropped & re-registered
    a new registration, not a renewal
    Transferred: Alibaba Cloud Computing (Beijing) Co., Ltd. → NAMECHEAP INCRedemption / pending delete seenRegistry showed it unregistered
  6. 2019
    between Nov 16, 2018 and Apr 3, 2019
    +1 yearexpiry Feb 4, 2019 → Feb 4, 2020Around expiry
    snapshots too far apart to say how early
    Redemption / pending delete seen
  7. 2018
    between Jul 29, 2017 and Jun 17, 2018
    +1 yearexpiry Feb 4, 2018 → Feb 4, 2019Around expiry
    snapshots too far apart to say how early
  8. 2017
    between Dec 22, 2016 and Jul 29, 2017
    +1 yearexpiry Feb 4, 2017 → Feb 4, 2018Around expiry
    snapshots too far apart to say how early
  9. 2016
    between Apr 4, 2008 and Sep 29, 2016
    Re-registeredexpiry Dec 16, 2008 → Feb 4, 2017Dropped & re-registered
    a new registration, not a renewal

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: 45 snapshots of 11111111111111111111111111111111111111111111111111111111111111.com from the who.is WHOIS/RDAP archive, 2008-04-04 to 2025-02-03. Ledger built 2026-09-27.