Renewal History
jmtracking.com
jmtracking.com has been renewed 3 times, usually 1 year at a time. It came close to lapsing once.
Every renewal, newest first
- 2025between Nov 17, 2022 and Feb 20, 2025Re-registeredexpiry Oct 17, 2023 → Feb 18, 2026Dropped & re-registereda new registration, not a renewalTransferred: Names Stop Here LLC → GoDaddy.com, LLCRedemption / pending delete seenRegistry showed it unregistered
- 2022between Aug 23, 2022 and Nov 17, 2022+1 yearexpiry Oct 17, 2022 → Oct 17, 2023Around expirysnapshots too far apart to say how early
- 2022between Mar 23, 2021 and Apr 2, 2022Re-registeredexpiry Sep 5, 2021 → Oct 17, 2022Dropped & re-registereda new registration, not a renewalTransferred: Hosting Concepts B.V. d/b/a Registrar.eu → Names Stop Here LLC
- 2020between Jun 11, 2020 and Nov 25, 2020Re-registeredexpiry Jun 19, 2020 → Sep 5, 2021Dropped & re-registereda new registration, not a renewalTransferred: DYNADOT LLC → Hosting Concepts B.V. d/b/a Openprovider
- 2019between May 4, 2019 and Jun 19, 2019+1 yearexpiry Jun 19, 2019 → Jun 19, 2020Around expirysnapshots too far apart to say how early
- 2018between Apr 2, 2018 and Jun 20, 2018+1 yearexpiry Jun 19, 2018 → Jun 19, 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: 53 snapshots of jmtracking.com from the who.is WHOIS/RDAP archive, 2017-08-06 to 2026-04-14. Ledger built 2026-09-27.