Find out what any website is built with
Enter a website address
Identifies the CMS, frameworks, server, CDN, analytics, ads, payment and marketing tools visible in the page's HTML and HTTP headers.
Fetching the page…
—
0
Technologies
0
Categories
0
Response (ms)
0%
Security headers
Detected Technologies 0
Detection reads only what the site makes public: HTML, script and stylesheet URLs, cookies and HTTP headers. Confidence reflects how many independent signals matched; items marked "implied" are inferred from another technology (for example WooCommerce implies WordPress).
Server & Connection
Security Headers
Want the full picture?
Knowing the stack is the first step — run a complete audit to check speed, SSL, mobile-friendliness, and broken links too.
Run Free Website AuditAbout Website Technology Detector
A website technology detector, sometimes called a tech stack checker or website profiler, reveals the software a site is running on. Every website leaves fingerprints: a CMS adds a generator meta tag and predictable folder names such as /wp-content/, frameworks ship distinctive markup and script bundles, servers announce themselves in HTTP response headers, and third-party services load scripts from well-known domains. This tool fetches the page you enter from our server, follows redirects safely, and compares what it finds against a library of more than 140 technology signatures covering content management systems, e-commerce platforms, JavaScript frameworks and libraries, UI toolkits, web servers, programming languages, hosting providers, CDNs, caching layers, analytics and tag managers, advertising pixels, payment gateways, live chat widgets, fonts, maps, SEO plugins and consent tools.
Where a version number is exposed, such as a WordPress generator tag or a versioned jQuery filename, it is shown beside the technology. The report also lists the response time, server IP address, HTTP version and the presence of six important security headers, so you get a quick technical snapshot in a single scan. Typical uses include competitor research before you build or redesign a site, checking whether a lead's website is running an outdated CMS, confirming that your own analytics and tag manager are actually loading, auditing a client's stack before migration, and spotting which payment or marketing tools a successful store depends on.
Keep in mind what a detector cannot see. Back-end languages, databases and frameworks that never reveal themselves in headers or markup stay hidden, sites that render everything with client-side JavaScript expose fewer signals in the raw HTML, and some security plugins deliberately strip version information. A technology that is not listed is therefore not proof that it is absent, while a detection backed by several independent signals is very reliable. Use the evidence line shown under each result to judge for yourself.