Renewal History

xn--b20bv4q25aq3kcmmklp.com

xn--b20bv4q25aq3kcmmklp.com has been renewed 3 times, usually 1 year at a time. No near-death on record.

Renewals on record
3
Longest renewal
1 year
Expires
Aug 19, 2026
as of the latest snapshot
Snapshots
8
2011–2025
Close calls
0
1 drop & re-registration

Every renewal, newest first

  1. 2025
    between Sep 2, 2024 and Sep 7, 2025
    +1 yearexpiry Aug 19, 2025 → Aug 19, 2026Around expiry
    snapshots too far apart to say how early
    Transferred: KOREA SERVER HOSTING INC. → ITEASY Inc.
  2. 2024
    between Jun 29, 2024 and Sep 2, 2024
    +1 yearexpiry Aug 19, 2024 → Aug 19, 2025Around expiry
    snapshots too far apart to say how early
  3. 2023
    between Mar 1, 2023 and Dec 28, 2023
    +1 yearexpiry Aug 19, 2023 → Aug 19, 2024Around expiry
    snapshots too far apart to say how early
  4. 2023
    between Dec 23, 2011 and Jan 22, 2023
    Re-registeredexpiry Jan 22, 2012 → Aug 19, 2023Dropped & re-registered
    a new registration, not a renewal
    Transferred: Korea Information Certificate Authority, Inc. dba DomainCA.com → KOREA SERVER HOSTING INC.

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: 8 snapshots of xn--b20bv4q25aq3kcmmklp.com from the who.is WHOIS/RDAP archive, 2011-12-23 to 2025-09-07. Ledger built 2026-09-27.