dns.pizza

Renewal History

minitokyo.net

minitokyo.net has been renewed 13 times, usually 1 year at a time, about 12 days after expiry. The longest single renewal was 2 years, around 2016, out to 2017. No near-death on record.

Renewals on record
13
Longest renewal
2 years
Expires
Jan 7, 2027
as of the latest snapshot
Snapshots
96
2012–2026

Every renewal, newest first

  1. 2026
    between Jan 8, 2026 and Jan 23, 2026
    +1 yearexpiry Jan 7, 2026 → Jan 7, 2027In grace period
    up to 2 weeks after expiry
  2. 2025
    between Jan 8, 2025 and Feb 6, 2025
    +1 yearexpiry Jan 7, 2025 → Jan 7, 2026In grace period
    up to 4 weeks after expiry
  3. 2023
    between Jun 9, 2023 and Aug 30, 2023
    +1 yearexpiry Jan 7, 2024 → Jan 7, 2025Early
    4 to 7 months before expiry
    Transferred: Key-Systems GmbH → MijnInternetOplossing B.V.
  4. 2023
    between Sep 6, 2022 and Feb 24, 2023
    +1 yearexpiry Jan 7, 2023 → Jan 7, 2024Around expiry
    snapshots too far apart to say how early
  5. 2022
    between Jan 4, 2022 and Jan 11, 2022
    +1 yearexpiry Jan 7, 2022 → Jan 7, 2023Around expiry
    snapshots too far apart to say how early
  6. 2021
    between Sep 25, 2020 and Jan 9, 2021
    +1 yearexpiry Jan 7, 2021 → Jan 7, 2022Around expiry
    snapshots too far apart to say how early
  7. 2020
    between Dec 16, 2019 and Feb 24, 2020
    +1 yearexpiry Jan 7, 2020 → Jan 7, 2021Around expiry
    snapshots too far apart to say how early
  8. 2019
    between Nov 16, 2018 and Jan 12, 2019
    +1 yearexpiry Jan 7, 2019 → Jan 7, 2020Around expiry
    snapshots too far apart to say how early
  9. 2018
    between Nov 16, 2017 and Jul 9, 2018
    +1 yearexpiry Jan 7, 2018 → Jan 7, 2019Around expiry
    snapshots too far apart to say how early
  10. 2017
    between Dec 9, 2016 and Feb 9, 2017
    +1 yearexpiry Jan 7, 2017 → Jan 7, 2018Around expiry
    snapshots too far apart to say how early
  11. 2016
    between Feb 1, 2014 and Sep 8, 2016
    +2 yearsexpiry Jan 7, 2015 → Jan 7, 2017Around expiry
    snapshots too far apart to say how early
  12. 2014
    between Dec 23, 2013 and Jan 7, 2014
    +1 yearexpiry Jan 7, 2014 → Jan 7, 2015Around expiry
    snapshots too far apart to say how early
  13. 2013
    between Feb 29, 2012 and Nov 12, 2013
    +1 yearexpiry Jan 7, 2013 → Jan 7, 2014Around 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: 96 snapshots of minitokyo.net from the who.is WHOIS/RDAP archive, 2012-02-29 to 2026-04-30. Ledger built 2026-09-27.

Back to minitokyo.net report