Tech Stack Detector — What Your Site Tells Strangers
This identifies the technologies a site reveals about itself: frameworks, server software, analytics, CDNs, CMS platforms, and often their versions. It reads the same signals anyone can — response headers, markup patterns, script sources, cookie names — which is precisely why it is worth running against your own site.
When it helps
Two reasons that pull in different directions. On someone else's site, it is competitive and practical research — what a comparable product is built on. On your own, it is a disclosure audit, and the results are usually more revealing than intended: a framework advertising its exact version in a header, a server banner naming a release with published vulnerabilities, an internal tool exposed by a cookie name. None of that needs to be public, and all of it shortens an attacker's reconnaissance.
Worth running automatically
Version disclosure changes with every deploy and every dependency upgrade, usually without anyone deciding to change it. A framework update can reintroduce a header that was previously suppressed, because the suppression lived in configuration that the upgrade reset. Checking on a schedule catches the reappearance. It also detects third-party scripts appearing on your site that nobody approved, which is a genuine supply-chain signal rather than a housekeeping one.
What you get out of it
Shows your site the way a stranger profiling it does. Most sites are disclosing more than their owners realise, and version banners reappear silently after upgrades that reset the configuration hiding them.