dns.pizza

Renewal History

ngoindex.org

ngoindex.org has been renewed 5 times, usually 1 year at a time. It came close to lapsing once.

Renewals on record
5
Longest renewal
1 year
Expires
Nov 30, 2023
as of the latest snapshot
Snapshots
28
2016–2024
Close calls
1

Every renewal, newest first

  1. 2023
    between Sep 14, 2022 and Mar 4, 2023
    +1 yearexpiry Nov 30, 2022 → Nov 30, 2023Around expiry
    snapshots too far apart to say how early
    Redemption / pending delete seen
  2. 2022
    between Mar 27, 2021 and Aug 2, 2022
    +1 yearexpiry Nov 30, 2021 → Nov 30, 2022Around expiry
    snapshots too far apart to say how early
    Transferred: Alibaba Cloud Computing (Beijing) Co., Ltd. → Gname.com Pte. Ltd.
  3. 2021
    between Nov 26, 2020 and Jan 10, 2021
    +1 yearexpiry Nov 30, 2020 → Nov 30, 2021Around expiry
    snapshots too far apart to say how early
    Registry auto-renew
  4. 2019
    between Nov 20, 2019 and Dec 20, 2019
    +1 yearexpiry Nov 30, 2019 → Nov 30, 2020Around expiry
    snapshots too far apart to say how early
  5. 2019
    between Nov 28, 2018 and Jan 13, 2019
    +1 yearexpiry Nov 30, 2018 → Nov 30, 2019Around 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: 28 snapshots of ngoindex.org from the who.is WHOIS/RDAP archive, 2016-09-09 to 2024-01-30. Ledger built 2026-09-27.

Back to ngoindex.org report