Renewal History
xn--barnklder-p-ntet-0nbhq.com
xn--barnklder-p-ntet-0nbhq.com has been renewed 8 times, usually 1 year at a time. No near-death on record.
Every renewal, newest first
- 2025between May 29, 2025 and Aug 13, 2025+1 yearexpiry Jul 24, 2025 → Jul 24, 2026Around expirysnapshots too far apart to say how early
- 2024between Jun 24, 2024 and Jul 31, 2024+1 yearexpiry Jul 24, 2024 → Jul 24, 2025Around expirysnapshots too far apart to say how early
- 2023between Feb 8, 2023 and Nov 3, 2023+1 yearexpiry Jul 24, 2023 → Jul 24, 2024Around expirysnapshots too far apart to say how early
- 2022between Apr 1, 2022 and Jun 11, 2022+1 yearexpiry Jul 24, 2022 → Jul 24, 2023Early1 to 4 months before expiry
- 2021between Nov 13, 2020 and Oct 3, 2021+1 yearexpiry Jul 24, 2021 → Jul 24, 2022Around expirysnapshots too far apart to say how early
- 2020between Dec 30, 2019 and May 17, 2020+1 yearexpiry Jul 24, 2020 → Jul 24, 2021Early2 to 7 months before expiry
- 2019between Nov 26, 2018 and Sep 29, 2019+1 yearexpiry Jul 24, 2019 → Jul 24, 2020Around expirysnapshots too far apart to say how early
- 2018between Sep 20, 2017 and Aug 6, 2018+1 yearexpiry Jul 24, 2018 → Jul 24, 2019Around expirysnapshots 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: 36 snapshots of xn--barnklder-p-ntet-0nbhq.com from the who.is WHOIS/RDAP archive, 2017-09-20 to 2025-08-13. Ledger built 2026-09-27.