Website Technology Detector
Use this free website technology detector to find out what a site is built with — WordPress, Shopify, React and more — from its public code.
Enter a website address above, or paste a page’s HTML source below.
This check reads only the site’s public HTML — the same code anyone can see with View Source. Nothing you enter is stored. Some sites block outside checks; if a site cannot be fetched, paste its HTML source above instead.
How to use the website technology detector
Ever wondered what a website is built with — WordPress or Shopify, React or plain HTML? This website technology detector finds out from the site's public code. It does not guess: it fetches the page's HTML and looks for the distinctive fingerprints that platforms, themes and tools leave behind.
Step 1: Type in the website address. You can include the https:// or not — reviewkarts.com works just as well as https://reviewkarts.com.
Step 2: Press Check website and wait a moment while the tool fetches the site's public code through a public proxy. You will see a message while it is working.
Step 3: Read the results. Every technology found is listed with the sign it was found by — for example, WordPress, found, sign: wp-content. The results also list what was not found among the technologies checked, so you can see the full picture. If nothing is found, the tool says so plainly instead of guessing.
Worked example: reviewkarts.com (example)
As an example, checking reviewkarts.com finds WordPress — the page's public code contains wp-content — and the Astra theme — the code contains astra. It does not find Shopify, Wix or Squarespace, and the results list those as not found. Your own checks will show the signs the tool actually found for the site you entered, which may be different from this example.
How detection works
Websites are built with platforms and tools that leave traces in their public HTML. WordPress pages link to files under wp-content and wp-includes. Shopify stores link to cdn.shopify.com. A site built with Next.js loads files from _next/. The detector keeps a list of these fingerprints and searches the fetched HTML for each one, ignoring upper and lower case. When a fingerprint is found, the technology is reported with the exact sign that matched, so you can check the reasoning yourself.
Why some sites can't be fetched
Some sites block outside checks. A site can refuse to serve its pages to the proxy the detector uses, or it can return an empty page to anything that is not a normal browser visit. That is the site's choice, and the detector respects it by saying plainly that the site could not be fetched. There is a workaround: open the site in your own browser, view the page source, copy it, and paste it into the box on this page. The same fingerprint checks then run on the HTML you pasted, in your own browser, and give the same kind of result.
How reliable is it?
Fingerprints are clues, not proof. A site can hide its platform, customise its code or strip out the usual signs, and then the detector will find nothing — even though the technology is there. The other way round, a sign can appear for an innocent reason, such as a page that mentions a technology by name. Treat the results as a strong hint, and check the sign shown for each finding before you rely on it. If the tool finds nothing, it says so rather than inventing an answer.
Frequently asked questions
How does the detector work?
The detector fetches the public HTML of the website you enter, through a free public proxy, and searches it for fingerprints — short, distinctive strings left in the code by platforms, themes and tools. Each technology it finds is reported with the exact sign that matched, and the technologies it did not find are listed too.
Why can't it always fetch a site?
Some sites block outside checks or refuse to serve their pages to the proxy. When that happens the detector says the site could not be fetched, and suggests pasting the page's HTML source instead. To do that, open the site in your browser, view the page source, copy it and paste it into the box on this page.
Is the result always right?
No. Fingerprints are clues, not proof. A site can hide or customise its code, so a technology can be present without leaving a sign, and a sign can occasionally appear for another reason. Check the sign shown for each finding, and treat the result as a strong hint rather than a guarantee.
Can it detect sites behind a login?
No. The detector can only read public code. Pages behind a login do not show their HTML to the public, so the fetch will fail. If you can open the page yourself while logged in, you can view its source, copy it and paste it into the box — the same checks will then run on the HTML you pasted.
Is it free and legal?
Yes. It is free, and it reads only public code — the same code anyone can see by choosing View Source in their browser. Nothing you enter is stored.