dns.pizza

Renewal History

tv4play.se

tv4play.se has been renewed 16 times, usually 1 year at a time, about 5 weeks before expiry. The longest single renewal was 2 years, around 2012, out to 2013. No near-death on record.

Renewals on record
16
Longest renewal
2 years
Expires
Feb 11, 2027
as of the latest snapshot
Snapshots
83
2009–2026

Every renewal, newest first

  1. 2026
    between Aug 7, 2025 and Feb 2, 2026
    +1 yearexpiry Feb 11, 2026 → Feb 11, 2027Early
    up to 6 months before expiry
  2. 2025
    between Jan 20, 2025 and Feb 20, 2025
    +1 yearexpiry Feb 11, 2025 → Feb 11, 2026Around expiry
    snapshots too far apart to say how early
  3. 2024
    between Dec 23, 2023 and Feb 23, 2024
    +1 yearexpiry Feb 11, 2024 → Feb 11, 2025Around expiry
    snapshots too far apart to say how early
  4. 2023
    between Jan 13, 2023 and Apr 27, 2023
    +1 yearexpiry Feb 11, 2023 → Feb 11, 2024Around expiry
    snapshots too far apart to say how early
  5. 2022
    between Jan 9, 2022 and Feb 8, 2022
    +1 yearexpiry Feb 11, 2022 → Feb 11, 2023Early
    up to 5 weeks before expiry
  6. 2021
    between Jan 28, 2021 and Feb 28, 2021
    +1 yearexpiry Feb 11, 2021 → Feb 11, 2022Around expiry
    snapshots too far apart to say how early
  7. 2020
    between Jan 13, 2020 and Feb 14, 2020
    +1 yearexpiry Feb 11, 2020 → Feb 11, 2021Around expiry
    snapshots too far apart to say how early
  8. 2019
    between Dec 20, 2018 and Feb 21, 2019
    +1 yearexpiry Feb 11, 2019 → Feb 11, 2020Around expiry
    snapshots too far apart to say how early
  9. 2018
    between Dec 23, 2017 and Jun 18, 2018
    +1 yearexpiry Feb 11, 2018 → Feb 11, 2019Around expiry
    snapshots too far apart to say how early
  10. 2017
    between Apr 12, 2016 and Nov 5, 2017
    +1 yearexpiry Feb 11, 2017 → Feb 11, 2018Around expiry
    snapshots too far apart to say how early
  11. 2016
    between Dec 4, 2015 and Jan 16, 2016
    +1 yearexpiry Feb 11, 2016 → Feb 11, 2017Early
    1 to 2 months before expiry
  12. 2015
    between Sep 9, 2014 and Jan 22, 2015
    +1 yearexpiry Feb 11, 2015 → Feb 11, 2016Early
    1 to 5 months before expiry
  13. 2014
    between Oct 10, 2013 and Jan 8, 2014
    +1 yearexpiry Feb 11, 2014 → Feb 11, 2015Early
    1 to 4 months before expiry
  14. 2013
    between Nov 25, 2012 and Aug 11, 2013
    +1 yearexpiry Feb 11, 2013 → Feb 11, 2014Around expiry
    snapshots too far apart to say how early
  15. 2012
    between May 4, 2010 and Nov 8, 2012
    +2 yearsexpiry Feb 11, 2011 → Feb 11, 2013Around expiry
    snapshots too far apart to say how early
    Transferred: Groth & Co → Melbourne IT CBS
  16. 2010
    between Jul 1, 2009 and May 4, 2010
    +1 yearexpiry Feb 11, 2010 → Feb 11, 2011Around 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: 83 snapshots of tv4play.se from the who.is WHOIS/RDAP archive, 2009-07-01 to 2026-04-16. Ledger built 2026-09-27.

Back to tv4play.se report