Find out what a website is built with. Enter a URL and we read its HTML, response headers and cookies for the fingerprints of about 70 technologies: frameworks, site builders, hosting, CDNs, analytics, payments, chat and auth.
How to use the Tech stack checker
- Enter the website's URL.
- Press Detect stack.
- Read the technologies grouped by category, plus anything the site reports about itself.
How detection works
Every technology leaves traces. Next.js serves files from /_next/static, WordPress from /wp-content, Vercel adds an x-vercel-id header, Stripe loads js.stripe.com. We fetch the page once from our server and match those traces. Nothing runs in a browser, so tools injected later by JavaScript (some analytics and chat widgets) can be missed.
Why founders check a stack
To see how a competitor built their product, pick tools that similar startups trust, check which analytics or payments a site uses before a partnership, or confirm your own site doesn't leak more than it should through headers like X-Powered-By.
Hiding your own stack
Remove the X-Powered-By header and generator meta tags, and keep your server header generic. It won't stop a determined look at your asset paths, but it removes the easy tells and the version numbers attackers look for.