Renewal History
rbx.com
rbx.com has been renewed 9 times, usually 1 year at a time, about 5 weeks before expiry. The longest single renewal was 3 years, around 2016, out to 2017. No near-death on record.
Every renewal, newest first
- 2024between Jun 19, 2024 and Jul 2, 2024+2 yearsexpiry Jul 25, 2024 → Jul 25, 2026Early3 to 5 weeks before expiry
- 2022between Jun 22, 2022 and Jun 29, 2022+2 yearsexpiry Jul 24, 2022 → Jul 25, 2024Early4 to 5 weeks before expiry
- 2020between Jun 12, 2020 and Jun 27, 2020+2 yearsexpiry Jul 24, 2020 → Jul 24, 2022Early4 to 6 weeks before expiry
- 2019between Nov 26, 2018 and Jan 9, 2019+1 yearexpiry Jul 25, 2019 → Jul 24, 2020Early6 to 8 months before expiryTransferred: GMO INTERNET, INC. → MarkMonitor, Inc.
- 2018between Apr 27, 2018 and Jul 23, 2018+1 yearexpiry Jul 25, 2018 → Jul 25, 2019Earlyup to 3 months before expiry
- 2017between Apr 15, 2017 and May 10, 2017+1 yearexpiry Jul 25, 2017 → Jul 25, 2018Early2 to 3 months before expiry
- 2016between Mar 31, 2014 and Jul 11, 2016+3 yearsexpiry Jul 25, 2014 → Jul 25, 2017Around expirysnapshots too far apart to say how early
- 2013between Jul 26, 2013 and Jul 28, 2013+1 yearexpiry Jul 25, 2013 → Jul 25, 2014In grace period1 to 3 days after expiry
- 2011between Nov 28, 2010 and Sep 21, 2011+1 yearexpiry Jul 25, 2012 → Jul 25, 2013Early10 to 20 months 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: 291 snapshots of rbx.com from the who.is WHOIS/RDAP archive, 2010-10-22 to 2026-05-17. Ledger built 2026-09-27.