Renewal History
027esf.com
027esf.com has been renewed 4 times, usually 2 years at a time. No near-death on record.
Every renewal, newest first
- 2025between Jan 29, 2025 and Sep 24, 2025+1 yearexpiry Aug 21, 2025 → Aug 21, 2026Around expirysnapshots too far apart to say how early
- 2025between May 18, 2023 and Jan 29, 2025+2 yearsexpiry Aug 21, 2023 → Aug 21, 2025Around expirysnapshots too far apart to say how early
- 2023between May 24, 2022 and May 18, 2023+1 yearexpiry Aug 21, 2022 → Aug 21, 2023Around expirysnapshots too far apart to say how early
- 2022between Oct 19, 2018 and May 24, 2022Re-registeredexpiry Jun 7, 2019 → Aug 21, 2022Dropped & re-registereda new registration, not a renewalTransferred: Alibaba Cloud Computing (Beijing) Co., Ltd. → Gname.com Pte. Ltd.
- 2018between Jul 12, 2016 and Oct 19, 2018+2 yearsexpiry Jun 7, 2017 → Jun 7, 2019Around expirysnapshots too far apart to say how earlyTransferred: HICHINA ZHICHENG TECHNOLOGY LTD. → 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 027esf.com from the who.is WHOIS/RDAP archive, 2016-07-12 to 2025-12-31. Ledger built 2026-09-27.