StatusCake

Scott Rigsby Foundation Domain Grabbed by Gambling Website

Scott Rigsby is no ordinary Ironman.  At the age of 18 he was involved in a motor vehicle accident which after 26 operations over the space of a decade left him as a double amputee.  After battling depression and alcohol addiction following his accident he found purpose in his life and went on to become the world record holder for double amputee athletes in both running and triathlon disciplines.  He set up the Scott Rigsby Foundation to similarly inspire others like him to live an active lifestyle and to take on and conquer challenges that may have seemed impossible before.

Earlier this year the foundation’s domain name, ScottRigsbyFoundation.org expired.  With the domain expired GoDaddy auctioned the domain; attracting several bidders it was sold for $155.

So why did a domain with such personal connections end up being bought by someone completely unconnected?  Over the years a website like Scott’s would have attracted a significant amount of web-traffic and with it acquired SEO value and backlinks.  Some people try to find “aged” domains with this kind of SEO profile and then keep a watch-list to wait and see if the owner forgets to renew the domain; grabbing them if they do become available.

This is what appears to have happened to Scott’s domain which has been repurposed by an online gambling website seeking presumably to benefit from the website’s historical reputation.  Whether buying domains to benefit from their rankings delivers SEO benefit is the subject of some debate, the Google Webmaster Trends Analysts Team suggests don’t bother, but many still follow this strategy.

Scott Rigsby is suing GoDaddy in the courts of Georgia for the loss of the domain; he argues that parts of his contract with GoDaddy were invalid and that they didn’t send him domain renwal reminders.  It is difficult to see how Scott’s law suit against GoDaddy will succeed and the process is will be all consuming in both time and money.  Whether other options such as a UDRP or false representation / trademark claim against the new domain owners might have been more effective have not been tested.

Scott is far from alone in finding his dropped domain name being caught by a third party; Dallas Cowboys and Microsoft have also faced similar issues.  As always prevention is better than cure.  Not only should domain name owners ensure they’ve set-up auto-renew and asked their domain name registrar to send renewal notices, but using a domain monitoring service to alert on domain expiration, as well as domain name record changes means that they can also be alerted for any changes which can give early warning to a domain name hijack.

For those looking to support Scott and his foundation their website can now be found at ScottRigsby.com, and you can follow him on Twitter.

Share this

More from StatusCake

What the Namecheap Outage Revealed About DNS Recovery

4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes

Monzo’s Stand-In Held Up on Wednesday. Some Customers Still Had a Bad Day.

3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and

What Broke GitHub on August 17 and How Retries Made the Incident Worse

3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests

Automate StatusCake Monitoring with viaSocket

3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect

Website Monitoring Checklist: What to Track Beyond Uptime

7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and

Want to know how much website downtime costs, and the impact it can have on your business?

Find out everything you need to know in our new uptime monitoring whitepaper 2021

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.