Website Technology Checker
Enter a website to see the technologies behind it — CMS, JavaScript frameworks, web server, CDN, analytics and payment tools — together with the hosting provider, server location and response details.
How the detection works
The tool downloads the page the way a browser would and matches its headers, cookies, meta tags, script and stylesheet URLs and telltale HTML fragments against a list of more than a hundred technology signatures. Versions are read where the site exposes them, for example in a generator tag or a library file name.
Hosting and location
The address the site answers from is looked up in geolocation and ASN databases to show the hosting provider, country and city, and how far the server is from you. When a CDN such as Cloudflare sits in front, the address belongs to the CDN, and the tool tells you so.
Response and security details
Alongside the technology list you get the HTTP status, protocol version, time to first byte, page size, compression, the redirect chain, the TLS certificate and a quick grade of the security response headers.
Limits of static detection
Only what is visible in a plain HTTP response can be detected. Technologies that run entirely in the browser without leaving a trace in the delivered page — or that are hidden on purpose — will not appear.
Frequently asked questions
How do I find out which CMS a website uses?
Enter the address above. WordPress, Joomla, Drupal, Shopify, Wix, Tilda, Bitrix and many other systems leave recognisable traces in the page source, headers or cookies, and appear in the CMS group.
Why does the IP belong to Cloudflare instead of the site's host?
Sites behind a CDN or reverse proxy answer from the CDN's network. The real origin server stays hidden by design, which is why the tool shows a CDN note next to the address.
Is the version number reliable?
It is read from what the site exposes, such as a meta generator tag or a file name like jquery-3.6.0.min.js. Sites often hide or leave outdated version strings, so treat it as a hint.
Can the tool detect back-end languages?
Only when they show up in headers (X-Powered-By, Server), cookies (PHPSESSID, ASP.NET_SessionId) or file extensions. A modern site may reveal nothing about its back end.
Is scanning a site allowed?
The tool makes one normal page request, like a browser visit, with a clear user agent. It does not probe hidden paths, and it never reaches private or internal addresses.