dns.pizza

Renewal History

broadcom.com

broadcom.com has been renewed 16 times, usually 1 year at a time, about 3 weeks before expiry. The longest single renewal was 2 years, around 2016, out to 2017. No near-death on record.

Renewals on record
16
Longest renewal
2 years
Expires
May 10, 2027
as of the latest snapshot
Snapshots
452
2007–2026
Close calls
0
1 drop & re-registration

Every renewal, newest first

  1. 2026
    between Apr 6, 2026 and May 12, 2026
    +1 yearexpiry May 10, 2026 → May 10, 2027Around expiry
    snapshots too far apart to say how early
  2. 2025
    between Apr 24, 2025 and May 7, 2025
    +1 yearexpiry May 10, 2025 → May 10, 2026Early
    up to 2 weeks before expiry
  3. 2024
    between May 4, 2024 and May 6, 2024
    +1 yearexpiry May 10, 2024 → May 10, 2025Early
    4 to 6 days before expiry
  4. 2023
    between May 5, 2023 and May 13, 2023
    +1 yearexpiry May 10, 2023 → May 10, 2024Around expiry
    snapshots too far apart to say how early
  5. 2022
    between Apr 13, 2022 and May 14, 2022
    +1 yearexpiry May 10, 2022 → May 10, 2023Around expiry
    snapshots too far apart to say how early
  6. 2021
    between Apr 7, 2021 and May 15, 2021
    +1 yearexpiry May 10, 2021 → May 10, 2022Around expiry
    snapshots too far apart to say how early
  7. 2020
    between May 4, 2020 and Jun 5, 2020
    +1 yearexpiry May 10, 2020 → May 10, 2021Around expiry
    snapshots too far apart to say how early
  8. 2019
    between Apr 29, 2019 and May 30, 2019
    +1 yearexpiry May 10, 2019 → May 10, 2020Around expiry
    snapshots too far apart to say how early
  9. 2018
    between Apr 21, 2018 and Jun 18, 2018
    +1 yearexpiry May 10, 2018 → May 10, 2019Around expiry
    snapshots too far apart to say how early
  10. 2017
    between Feb 20, 2017 and May 4, 2017
    +1 yearexpiry May 10, 2017 → May 10, 2018Early
    up to 3 months before expiry
    Transferred: Ascio Technologies, Inc → CSC CORPORATE DOMAINS, INC.
  11. 2016
    between Apr 28, 2014 and Jun 27, 2016
    +2 yearsexpiry May 10, 2015 → May 10, 2017Around expiry
    snapshots too far apart to say how early
  12. 2014
    between Apr 7, 2014 and Apr 22, 2014
    +1 yearexpiry May 10, 2014 → May 10, 2015Early
    3 to 5 weeks before expiry
  13. 2013
    between Apr 23, 2012 and Nov 24, 2013
    Re-registeredexpiry May 10, 2012 → May 10, 2014Dropped & re-registered
    a new registration, not a renewal
  14. 2011
    between Apr 3, 2011 and Nov 22, 2011
    +1 yearexpiry May 10, 2011 → May 10, 2012Around expiry
    snapshots too far apart to say how early
  15. 2010
    between Mar 30, 2010 and Apr 10, 2010
    +1 yearexpiry May 10, 2010 → May 10, 2011Early
    4 to 6 weeks before expiry
  16. 2009
    between Feb 2, 2009 and Apr 18, 2009
    +1 yearexpiry May 10, 2009 → May 10, 2010Early
    1 to 3 months before expiry
  17. 2008
    between Apr 9, 2008 and Apr 26, 2008
    +1 yearexpiry May 10, 2008 → May 10, 2009Early
    2 to 4 weeks before expiry

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: 452 snapshots of broadcom.com from the who.is WHOIS/RDAP archive, 2007-05-19 to 2026-05-18. Ledger built 2026-09-27.

Back to broadcom.com report