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
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026