Fingerprint the stack behind a URL - with versions, confidence and CVE pivots - from headers, cookies, markup and assets.
Tech Fingerprint identifies the technology stack behind a URL - web server, language, CMS, application frameworks, JavaScript frameworks and libraries, CDN/WAF, analytics and chat widgets - by analyzing response headers, cookies, HTML markup and asset signatures.
It goes beyond naming the tech: where the signal allows, it extracts the version, attaches a confidence level and shows the evidence (which header, cookie or asset gave it away). Detected library versions are checked against a built-in vulnerable-version database, so known-weak components (e.g. old jQuery, Lodash, Bootstrap) come back with their exact CVEs inline.
A deep scan option fetches the referenced JS/CSS to read precise versions from file banners, flag source maps and leaked keys (Firebase, Stripe, Google, AWS), and compute the favicon hash with a Shodan pivot to find other hosts running the same app. A bulk mode fingerprints a whole list of hosts into a stack matrix - ideal straight after Subdomain Discovery.
Detected JavaScript library versions are matched against a built-in, curated vulnerable-version database (Retire.js-style) - so a result like jQuery 3.2.1 shows its actual CVEs instantly and offline. For server products, use the one-click CVE Lookup pivot.
Best-effort from public signals; versions can be hidden or spoofed. Each result carries a confidence level and the evidence behind it. The deep scan reads asset file banners for far more reliable versions.
No - it makes browser-style GETs (the page, and in deep mode its own linked assets/favicon) and reads only the responses. It does not probe paths or send attack traffic.