dns.pizza

Renewal History

mobile-8.com

mobile-8.com has been renewed 6 times, usually 1 year at a time. The longest single renewal was 2 years, around 2010, out to 2011. It came close to lapsing 2 times.

Renewals on record
6
Longest renewal
2 years
Expires
Aug 13, 2026
as of the latest snapshot
Snapshots
70
2009–2026
Close calls
2
8 drops & re-registration

Every renewal, newest first

  1. 2026
    between Feb 12, 2025 and Jan 1, 2026
    Re-registeredexpiry Jun 17, 2025 → Aug 13, 2026Dropped & re-registered
    a new registration, not a renewal
    Transferred: Hongkong Kouming International Limited → Sav.com, LLC
  2. 2024
    between May 9, 2024 and Jul 2, 2024
    Re-registeredexpiry Mar 27, 2025 → Jun 17, 2025Dropped & re-registered
    a new registration, not a renewal
    Transferred: Network Solutions, LLC → Hongkong Kouming International Limited
  3. 2024
    between Feb 13, 2024 and May 9, 2024
    Re-registeredexpiry Jan 4, 2025 → Mar 27, 2025Dropped & re-registered
    a new registration, not a renewal
    Transferred: CloudBreakDomains, LLC → Network Solutions, LLC
  4. 2024
    between Oct 30, 2023 and Feb 13, 2024
    +1 yearexpiry Jan 4, 2024 → Jan 4, 2025Around expiry
    snapshots too far apart to say how early
  5. 2023
    between Dec 6, 2022 and Jan 21, 2023
    Re-registeredexpiry Oct 15, 2022 → Jan 4, 2024Dropped & re-registered
    a new registration, not a renewal
    Transferred: Register.com, Inc. → CloudBreakDomains, LLCRedemption / pending delete seen
  6. 2021
    between Sep 17, 2021 and Oct 17, 2021
    Re-registeredexpiry Jul 29, 2021 → Oct 15, 2022Dropped & re-registered
    a new registration, not a renewal
    Transferred: DropCatch.com 1350 LLC → Register.com, Inc.Redemption / pending delete seen
  7. 2020
    between Apr 13, 2020 and Aug 5, 2020
    +1 yearexpiry Jul 29, 2020 → Jul 29, 2021Around expiry
    snapshots too far apart to say how early
  8. 2020
    between Jul 18, 2019 and Jan 13, 2020
    +1 yearexpiry Jul 29, 2019 → Jul 29, 2020Around expiry
    snapshots too far apart to say how early
  9. 2018
    between Jul 12, 2018 and Aug 19, 2018
    +1 yearexpiry Jul 29, 2018 → Jul 29, 2019Around expiry
    snapshots too far apart to say how early
  10. 2018
    between May 23, 2017 and Jul 12, 2018
    Re-registeredexpiry May 13, 2017 → Jul 29, 2018Dropped & re-registered
    a new registration, not a renewal
  11. 2016
    between Mar 21, 2014 and Jul 20, 2016
    Re-registeredexpiry Mar 4, 2015 → May 13, 2017Dropped & re-registered
    a new registration, not a renewal
    Transferred: PLISK → DropCatch.com 531 LLC
  12. 2014
    between Jan 8, 2014 and Mar 21, 2014
    Re-registeredexpiry Dec 27, 2013 → Mar 4, 2015Dropped & re-registered
    a new registration, not a renewal
    Transferred: CSL Computer Service Langenbach GmbH d/b/a joker.com → PLISK
  13. 2012
    between Nov 18, 2011 and Jun 27, 2012
    +2 yearsexpiry Dec 27, 2011 → Dec 27, 2013Around expiry
    snapshots too far apart to say how early
  14. 2010
    between Aug 7, 2009 and Jan 21, 2010
    +2 yearsexpiry Dec 27, 2009 → Dec 27, 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: 70 snapshots of mobile-8.com from the who.is WHOIS/RDAP archive, 2009-08-04 to 2026-01-01. Ledger built 2026-09-27.

Back to mobile-8.com report