{"id":1335,"date":"2025-04-20T00:00:00","date_gmt":"2025-04-19T22:00:00","guid":{"rendered":"https:\/\/demo.sidekick.be\/itenium\/site-typo-scanner\/"},"modified":"2025-11-28T13:31:41","modified_gmt":"2025-11-28T12:31:41","slug":"site-typo-scanner","status":"publish","type":"post","link":"https:\/\/demo.sidekick.be\/itenium\/blog\/productivity\/site-typo-scanner\/","title":{"rendered":"Site Inspector"},"content":{"rendered":"

\ud83d\udcb8\ud83d\udcb8 Triplechecker<\/h1>\n

The git repository has been archived since January 2025 and they basically point you towards www.triplechecker.com<\/a> which is their cloud deploy.<\/p>\n

It worked very well\u2026 Finding a whopping 100 spelling errors on itenium.be, but after the first 7 errors, it asked me to sign up for a mere \u20ac15\/month. Uhm, no thanks.<\/p>\n

Docker Container<\/h1>\n

You can pretty easily host it yourself though!<\/p>\n

git clone https:\/\/github.com\/siteinspector\/siteinspector\ncd siteinspector\n# Open docker-compose.yml, search for \"SECRET_KEY_BASE:\"\n# and enter a random 30+ character key.\ndocker compose up -d\n<\/code><\/pre>\n
Surf to http:\/\/localhost:808<\/a><\/p>\n
\ud83d\udcc8 Profit!!<\/p>\n
Big oopsie<\/h1>\n
So one of the 100+ typos it found was on our home page, in the very first slide, a typo which has been screaming at our customers on our website for 8 years<\/strong>. Whoops!
(strenght<\/strong>en vs strength<\/strong>en)<\/small><\/p>\n
\"Strengthening<\/p>\n
Heh heh, maybe no one ever noticed? \ud83d\ude2c\ud83d\ude48\ud83e\udd2b<\/p>\n
Let AI figure it out<\/h1>\n
Since the siteinspector README just points you towards the paying service, I had the brilliant idea of asking AI to figure it out for me!<\/p>\n
Prompt<\/strong>: https:\/\/github.com\/siteinspector\/siteinspector<\/em>
You know this one? Know how I can run it against my website?<\/em><\/p>\n
Yes! siteinspector<\/code> is a Ruby gem that audits websites for things like redirects, headers, security, and more.<\/p>\n
Here\u2019s how to run it against your website:<\/p>\n
\u2705 1. Install Ruby (if needed)
 \u2705 2. Install siteinspector gem
 \u2705 3. Run it against your site<\/p>\n
gem install siteinspector\nsiteinspector https:\/\/itenium.be\n<\/code><\/pre>\n
AI Slopsquatting<\/h2>\n
ERROR:  Could not find a valid gem 'siteinspector' (>= 0) in any repository\nERROR:  Possible alternatives: site-inspector\n<\/code><\/pre>\n
That\u2019s right, the gem doesn\u2019t exist. And site-inspector<\/code> is something different.<\/p>\n
<\/a>benbalter\/site-inspector<\/a>: Ruby Gem to sniff information about a domain\u2019s technology and capabilities.<\/p>\n
It was a potential slopsquat<\/strong> attack; an emerging danger of AI!
 Let\u2019s use the same steps mechanism it used on me to run a potentially disastrous command to illustrate.<\/p>\n
\u2705 1. AI hallucinates some dependency that looks real.
 \u2705 2. A malicious party registers this dependency and puts malware in it.
 \u2705 3. An unsuspecting developer runs the command and \ud83d\udca5<\/p>\n
Extras<\/h1>\n
Other interesting reads<\/b><\/p>\n