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
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.
StatusCake Team
Share this
More from StatusCake
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026
When AI Speeds Up Change, Knowing First Becomes the Constraint
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
James Barnes
January 14, 2026
Make Your Engineering Processes Resilient. Not Your Opinions About AI
4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development. For some teams, it’s an obvious productivity multiplier. For others, it’s viewed with suspicion. A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes
James Barnes
January 8, 2026