A server-side fingerprinting pipeline — your browser only sends a URL; all detection logic stays on the server.
Server-side fetch
The target page is retrieved by the server (not your browser), which sidesteps the cross-origin restrictions that prevent in-browser tools from reading third-party sites. Private, loopback and reserved addresses are blocked to prevent SSRF.
Multi-signal fingerprinting
Each technology is matched on response headers, Set-Cookie names, raw HTML, <script src> URLs, <meta> tags, and CSS-selector (dom) rules evaluated against the parsed page — the server-side signal classes Wappalyzer uses, with version extraction where the signature allows. Signals that only exist after JavaScript runs (in-page js globals) require the optional render service.
Implied technologies
Detections cascade: spotting WooCommerce implies WordPress and PHP; Next.js implies React and Node.js. Implied entries are flagged so you can tell direct matches from inferred ones.
Security-header scorecard
The same response TechDetect fingerprints also carries the site's security headers. Each scan grades Content-Security-Policy, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and cross-origin policies into an A–F score, and flags software-version disclosure — no extra requests to the target.
Cookie & third-party audit
Every Set-Cookie is checked for the Secure, HttpOnly and SameSite flags, and the page's external hosts are inventoried and labelled (analytics, advertising, CDN, payments, chat) so you can see who a site talks to and what it may be leaking.
Hidden ruleset
The fingerprint database and matching engine never reach the browser — there is no detection logic in the page source to copy. The page only renders results returned as JSON.
JS-render aware
Single-page apps that render via JavaScript expose little in raw HTML. TechDetect flags likely JS-heavy pages, and can optionally route them through a headless renderer for deeper detection when that service is enabled.
Export
Every result set is exportable as JSON for reporting, asset inventories, or feeding into other tooling.