Renewal History
ee-cloud.com
ee-cloud.com has been renewed once, usually 1 year at a time. It came close to lapsing 2 times.
Every renewal, newest first
- 2025between Mar 18, 2025 and Oct 14, 2025+1 yearexpiry Jul 4, 2025 → Jul 4, 2026Around expirysnapshots too far apart to say how early
- 2024between Jun 3, 2023 and Aug 4, 2024Re-registeredexpiry Apr 16, 2023 → Jul 4, 2025Dropped & re-registereda new registration, not a renewalTransferred: NAMECHEAP INC → Gname.com Pte. Ltd.Redemption / pending delete seen
- 2023between Jan 27, 2021 and Jun 3, 2023Re-registeredexpiry Nov 5, 2021 → Apr 16, 2023Dropped & re-registereda new registration, not a renewalTransferred: DNSPod, Inc. → NAMECHEAP INCRedemption / pending delete seen
- 2021between Dec 19, 2018 and Jan 27, 2021Re-registeredexpiry Aug 6, 2019 → Nov 5, 2021Dropped & re-registereda new registration, not a renewalTransferred: Alibaba Cloud Computing (Beijing) Co., Ltd. → DNSPod, Inc.
- 2018between Jun 1, 2014 and Dec 19, 2018Re-registeredexpiry Aug 16, 2014 → Aug 6, 2019Dropped & re-registereda new registration, not a renewalTransferred: CRAZY DOMAINS FZ-LLC → Alibaba Cloud Computing (Beijing) Co., Ltd.
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: 20 snapshots of ee-cloud.com from the who.is WHOIS/RDAP archive, 2014-06-01 to 2026-02-28. Ledger built 2026-09-27.