What is any SaaS actually built with?
Paste a URL to detect the tech stack behind any website: framework, hosting, analytics, payments, auth, email and more, with the evidence for every single detection.
How we detect
Every detection in the report is backed by the signal it was matched from. If a method can't prove a technology is there, we don't list it.
Response headers
Server, CDN and framework fingerprints straight from the HTTP response, e.g. x-vercel-id, x-powered-by. The cleanest signals in a scan.
Scripts & markup
Third-party script sources and HTML markers that reveal analytics, payments and CMS choices embedded in the page itself.
Cookies & DNS
Set-cookie names plus CNAME and TXT records that expose hosting, auth and email providers the page never mentions.
Evidence-first, always
We only list a technology when a signature genuinely matches. We show you exactly what matched, so you can judge each detection yourself.
Server-side tech: honestly invisible
Some tools leave no public trace from the outside. “None detected” means no public signal, not proof of absence. We never pad the list with guesses.
You've seen the stack. Now go deeper.
Frequently asked questions
How does the tech stack detector work?
You paste a website URL. Our server fetches the page (through an SSRF-safe request), then matches response headers, cookies, script sources, HTML markers and DNS records against an open signature set. Each detection lists the exact evidence we matched, grouped by category: framework, hosting, analytics, payments, auth, email, CMS and AI providers.
What technologies can it detect?
Anything with a public fingerprint: frontend frameworks, hosting and CDN providers, analytics, payment processors, auth providers, email services, CMS platforms and AI providers. Detections are grouped by category, and every one shows the header, script, cookie or DNS record it was matched from.
Is it accurate?
It is honest rather than exhaustive. We only report a technology when a signature genuinely matches, and we show you the evidence so you can judge it yourself. Some tools are invisible from the outside (server-side only), so “none detected” in a category means we found no public signal, not necessarily that nothing is there.
Is this a Wappalyzer alternative?
It covers the same core need of identifying what a website is built with, using a self-hosted, open signature approach, free and with no account. Our angle is honesty: every detection is evidence-backed and we never pad the list with guesses.
Is it free?
Yes, with no account. Live scans are rate-limited for fair use, and any domain scanned recently returns instantly from cache at no cost.
Does it work on any website?
Any publicly reachable website — SaaS products, marketing sites, blogs. Sites behind logins, aggressive bot walls or heavy client-side rendering may expose fewer signals, in which case you'll simply see fewer detections rather than padded guesses.
Can I use this to research competitors?
Yes. Founders, marketers and investors use it to see the framework, hosting, payments and analytics choices behind products they admire or compete with. Because we cache results, you can also share a permalink to a specific report.