diff --git a/en/thing_25/README.md b/en/thing_25/README.md
index 66cbd942..c459d3e9 100644
--- a/en/thing_25/README.md
+++ b/en/thing_25/README.md
@@ -19,8 +19,8 @@ The leak type can vary but, when it happens, it can be deadly to the person, tea
 
 To appropriate the old saying that "a lie can travel halfway around the world while the truth is putting on its shoes," in this day and age a screw-up can be Dugg, Twittered, and Flibflarbed before anyone in the developer's timezone is awake to do anything about it.
 
-Even your source code isn't necessarily free of scrutiny. In 2004, when a tarball of the Windows 2000 source code made its way onto file sharing networks, some folks merrily grepped through it for profanity, insults, and [other funny content](http://www.kuro5hin.org/story/2004/2/15/71552/7795). (The comment `// TERRIBLE HORRIBLE NO GOOD VERY BAD HACK` has, I will admit, become appropriated by me from time to time since!)
+Even your source code isn't necessarily free of scrutiny. In 2004, when a tarball of the Windows 2000 source code made its way onto file sharing networks, some folks merrily grepped through it for profanity, insults, and [other funny content](https://web.archive.org/web/20040622214250/http://www.kuro5hin.org/story/2004/2/15/71552/7795). (The comment `// TERRIBLE HORRIBLE NO GOOD VERY BAD HACK` has, I will admit, become appropriated by me from time to time since!)
 
 In summary, when writing any text in your code — whether comments, logging, dialogs, or test data — always ask yourself how it will look if it becomes public. It will save some red faces all round.
 
-By [Rod Begbie](http://programmer.97things.oreilly.com/wiki/index.php/Rod_Begbie)
\ No newline at end of file
+By [Rod Begbie](http://programmer.97things.oreilly.com/wiki/index.php/Rod_Begbie)