dns.pizza

Renewal History

iranebay.com

iranebay.com has been renewed 9 times, usually 1 year at a time, about 3 weeks after expiry. The longest single renewal was 3 years, around 2018, out to 2018. It came close to lapsing once.

Renewals on record
9
Longest renewal
3 years
Expires
Sep 6, 2026
as of the latest snapshot
Snapshots
105
2007–2026
Close calls
1
4 drops & re-registration

Every renewal, newest first

  1. 2025
    between Sep 21, 2025 and Oct 19, 2025
    +1 yearexpiry Sep 6, 2025 → Sep 6, 2026In grace period
    2 to 6 weeks after expiry
    Registry auto-renew
  2. 2025
    between Aug 27, 2025 and Sep 21, 2025
    +1 yearexpiry Sep 6, 2025 → Sep 6, 2026Around expiry
    snapshots too far apart to say how early
  3. 2024
    between Nov 17, 2020 and Oct 22, 2024
    Re-registeredexpiry Oct 17, 2021 → Sep 6, 2025Dropped & re-registered
    a new registration, not a renewal
    Transferred: Atak Domain → CSL Computer Service Langenbach GmbH d/b/a joker.comRegistry showed it unregistered
  4. 2020
    between May 2, 2020 and Nov 17, 2020
    Re-registeredexpiry May 25, 2020 → Oct 17, 2021Dropped & re-registered
    a new registration, not a renewal
    Transferred: Alibaba Cloud Computing (Beijing) Co., Ltd. → Atak Domain
  5. 2019
    between Apr 10, 2018 and Jun 30, 2019
    Re-registeredexpiry Mar 8, 2019 → May 25, 2020Dropped & re-registered
    a new registration, not a renewal
    Transferred: TUCOWS, INC. → Alibaba Cloud Computing (Beijing) Co., Ltd.
  6. 2018
    between Mar 14, 2018 and Mar 23, 2018
    +1 yearexpiry Mar 8, 2018 → Mar 8, 2019In grace period
    1 to 2 weeks after expiry
  7. 2018
    between Nov 6, 2014 and Mar 14, 2018
    +3 yearsexpiry Mar 8, 2015 → Mar 8, 2018Around expiry
    snapshots too far apart to say how early
  8. 2014
    between Nov 24, 2013 and Feb 23, 2014
    +1 yearexpiry Mar 8, 2014 → Mar 8, 2015Early
    up to 3 months before expiry
  9. 2013
    between Sep 24, 2012 and Nov 24, 2013
    Re-registeredexpiry Dec 21, 2012 → Mar 8, 2014Dropped & re-registered
    a new registration, not a renewal
  10. 2012
    between Dec 12, 2011 and Sep 24, 2012
    +1 yearexpiry Dec 21, 2011 → Dec 21, 2012Around expiry
    snapshots too far apart to say how early
  11. 2011
    between Sep 14, 2010 and Jan 3, 2011
    +1 yearexpiry Dec 21, 2010 → Dec 21, 2011Around expiry
    snapshots too far apart to say how early
  12. 2010
    between Sep 8, 2009 and Mar 13, 2010
    +1 yearexpiry Dec 21, 2009 → Dec 21, 2010Around expiry
    snapshots too far apart to say how early
  13. 2009
    between Jul 3, 2008 and Feb 13, 2009
    +1 yearexpiry Dec 21, 2008 → Dec 21, 2009Around 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: 105 snapshots of iranebay.com from the who.is WHOIS/RDAP archive, 2007-12-24 to 2026-05-26. Ledger built 2026-09-27.

Back to iranebay.com report