Renewal History
myrewardsgroup.com
myrewardsgroup.com has been renewed 8 times, usually 1 year at a time. The longest single renewal was 3 years, around 2017, out to 2018. No near-death on record.
Every renewal, newest first
- 2026between Dec 17, 2023 and Jan 21, 2026+2 yearsexpiry Mar 6, 2024 → Mar 7, 2026Around expirysnapshots too far apart to say how early
- 2023between Jan 11, 2022 and Dec 17, 2023+2 yearsexpiry Mar 6, 2022 → Mar 6, 2024Around expirysnapshots too far apart to say how early
- 2022between Aug 17, 2020 and Jan 11, 2022+1 yearexpiry Mar 7, 2021 → Mar 6, 2022Around expirysnapshots too far apart to say how early
- 2020between Nov 9, 2019 and Apr 30, 2020+1 yearexpiry Mar 7, 2020 → Mar 7, 2021Around expirysnapshots too far apart to say how early
- 2019between Nov 1, 2018 and Aug 20, 2019+1 yearexpiry Mar 7, 2019 → Mar 7, 2020Around expirysnapshots too far apart to say how earlyTransferred: Name.com, Inc. → GoDaddy.com, LLC
- 2018between Jan 3, 2018 and Jul 5, 2018+1 yearexpiry Mar 7, 2018 → Mar 7, 2019Around expirysnapshots too far apart to say how early
- 2017between Jun 5, 2014 and May 31, 2017+3 yearsexpiry Mar 7, 2015 → Mar 7, 2018Around expirysnapshots too far apart to say how early
- 2014between Dec 5, 2013 and Mar 13, 2014+1 yearexpiry Mar 7, 2014 → Mar 7, 2015Around expirysnapshots 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: 24 snapshots of myrewardsgroup.com from the who.is WHOIS/RDAP archive, 2013-10-23 to 2026-01-21. Ledger built 2026-09-27.