Renewal History
publiccomputingservices.org
publiccomputingservices.org has been renewed 5 times, usually 1 year at a time. No near-death on record.
Every renewal, newest first
- 2025between Apr 1, 2025 and Sep 21, 2025+1 yearexpiry Jun 21, 2025 → Jun 21, 2026Around expirysnapshots too far apart to say how early
- 2024between Dec 12, 2023 and Aug 4, 2024+1 yearexpiry Jun 21, 2024 → Jun 21, 2025Around expirysnapshots too far apart to say how early
- 2023between Aug 1, 2022 and Dec 12, 2023+1 yearexpiry Jun 21, 2023 → Jun 21, 2024Around expirysnapshots too far apart to say how early
- 2022between Aug 30, 2021 and Aug 1, 2022+1 yearexpiry Jun 21, 2022 → Jun 21, 2023Around expirysnapshots too far apart to say how earlyRegistry auto-renew
- 2021between May 15, 2021 and Aug 30, 2021+1 yearexpiry Jun 21, 2021 → Jun 21, 2022Around expirysnapshots too far apart to say how early
- 2021between Feb 15, 2017 and May 15, 2021Re-registeredexpiry Apr 4, 2017 → Jun 21, 2021Dropped & re-registereda new registration, not a renewalTransferred: GoDaddy.com, LLC → DYNADOT LLC
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: 12 snapshots of publiccomputingservices.org from the who.is WHOIS/RDAP archive, 2016-09-08 to 2025-09-21. Ledger built 2026-09-27.