No signup · No email · Completely free forever
Paste a domain to see what the website is built with. This free website technology checker groups public components by category — CMS, frameworks, analytics, CDN, hosting clues, JavaScript libraries, widgets, payments, and more. We match technology fingerprints in publicly accessible markup, headers, and generator tags. Custom, headless, or heavily stripped sites can be missed.
Paste a hostname or a full URL. We fetch the homepage and match technology fingerprints to show what the site is built with. Results are not a guarantee — hidden, custom, or headless stacks may not appear.
1 target per run · 10 domains per day.
Use this free Website Built With Checker when you want a public-source view of a website’s technology stack — a website technology checker for one target at a time.
example.com). One target per run.Chrome extension
Install the free Karma Domains add-on to see domain age and Karma Metric on SERPs — and run Checks from the popup.
The Website Built With Checker covers a public-source question: what visible components appear to power the website. It is not a full-stack audit, not a lead list, and not a vulnerability scan. You see what the homepage exposes — not a complete inventory of the origin.
We fetch the homepage and compare it with a library of technology fingerprints in site elements: markup patterns, HTTP headers, a generator tag, and sometimes a favicon or a light DOM pass. Matches are grouped by category so you can see what the site is built with in one place. A locked-down, headless, or bot-protected front end can look empty even when a large stack sits behind it.
Typical groups include CMS platforms and website builders (content management systems such as Shopify or Wix), ecommerce, JavaScript frameworks, analytics and marketing tags, a CDN or other content delivery clue, the web server, a programming language banner, widgets, and payment tools. You may also see CSS, JS, Bootstrap, or a font file when those paths are public. The page only renders categories that actually matched. A visible library is a clue, not proof of the whole architecture, the database, or the infrastructure behind the page.
Custom builds, headless setups, sites that strip default paths and generator tags, or pages that reply to our request with a bot check often leave too few traces. A miss is not proof that no platform is used — only that we did not see a public fingerprint.
We do not log into the admin, run the page in a full rendered session as a separate product, inventory every plugin, look for vulnerabilities, keep a history of past stacks, or export a bulk list of thousands of sites. For the CMS name as the main result, use CMS Detector. A dedicated theme report is on the theme detector. For the hosting provider and network, use Hosting Checker.
A Website Built With Checker is a free website technology checker: a practical way to check the public stack used to build a site, grouped by category. It looks at technology fingerprints in the page’s HTML, headers, and meta tags. It cannot see a private backend, and custom or headless sites can be missed. It is a useful first lookup for a developer doing web development research, and it works on a homepage or a landing page.
Start with this form to check website technology. We fetch the homepage and match public fingerprints — generator tags, response headers such as X-Powered-By, and other visible traces. Read the categories in the result, then confirm anything important with the site owner or your own records. You can inspect the source code in a web browser for context, but that is not required to run the check. Treat what you see as a starting point to analyze public clues, not as a certified audit. To get detailed hosting or theme data, use the sibling online tools.
The public components we can detect from technology fingerprints, grouped by category — for example CMS, frameworks, CDN, hosting clues, widgets, and payments. If a version, a generator tag, or a public response header is visible, we show that too. Fingerprints can also reveal a front-end clue, or help you discover a widget, when those traces are public.
We fetch the homepage and match technology fingerprints in HTML, headers, scripts, and meta tags. We do not claim a complete inventory of hidden or custom software, and we do not run a separate headless product in this version.
The site may be custom or headless, the usual traces may have been removed, the homepage may have failed to load, or a bot check may have blocked the fetch. A miss is not proof that the site has no stack.
Yes. Fingerprints can miss hardened or heavily customized sites, and they only see what the homepage exposes. Treat the result as a public-source clue, not a certified audit. Response headers may describe a proxy or CDN rather than the origin server.
This page shows the public platform and technologies across categories. CMS Detector puts the content-management system first. The theme detector is a dedicated theme report. Hosting Checker covers the hosting provider. These checks help you identify public clues in one place.
Only when a fingerprint exposes one, for example in a public generator string. We do not guess versions.
No signup for the free tier. Limits match other Karma landing-tools: 1 target per run and the shared free daily domain limit of 10 per day.
Yes — the free Karma Domains add-on on the Chrome Web Store shows domain age and Karma Metric on SERPs and runs Checks from the popup.
Alongside this free check, the full list of expired domains from 49 lists across 32 platforms (auctions, drops and buy-now listings) is on the Karma.Domains homepage, updated hourly.
See domain age and Karma Metric on SERPs — and run WHOIS, name lookups, and other Checks from the popup. Free on the Chrome Web Store.