Free technology detector
See which web server, CDN, framework and content management system your home page discloses, with any version it gives away.
Example report
example.comAlso 4 informational.
What the home page discloses
| Host | Technology | Version | Seen in |
|---|---|---|---|
| example.com | nginxWeb server | 1.18.0 | Server header: nginx/1.18.0 |
| example.com | PHPProgramming language | 8.0.30 | X-Powered-By header: PHP/8.0.30 |
| example.com | WordPressContent management system | 6.4 | generator meta tag: WordPress 6.4 |
| www.example.com | cloudflareHosting or CDN | Not disclosed | Server header: cloudflare |
What the technology check looks at
Headers
Server, X-Powered-By and the headers a CDN or host adds.
Cookie names
Names that belong to a platform, such as PHPSESSID.
Markup
A generator tag or another trace a content system leaves.
Versions
Any version number disclosed, and where it was seen.
Detection is observation and inference: a CDN can hide the server behind it, and an advertised version may not be what is installed.
Keep watch after you've fixed it
Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.
Free during the preview. Domain verification required.
- NewIssue detected
- FixedConfirmed by recheck
- ReopenedDetected again
How the check works
- One request for the home page of the domain and, for a registrable domain, its
www.name: HTTPS first, plain HTTP if HTTPS does not answer, following up to 2 redirects. - Response headers that name software, such as
ServerandX-Powered-By, and headers that identify a CDN or hosting platform. - Cookie names that belong to a platform, such as
PHPSESSIDorJSESSIONID. - Markup in the page, such as a
generatormeta tag left by a content management system. - For each technology: its type, the version where one is disclosed, and where it was seen.
Reading a result
The result lists what the home page reveals, not everything the site runs. A CDN in front of the site often hides the server behind it, and a well-configured server names no version. A technology with no version shown was named without one.
Every item is informational; nothing here is a finding on its own. A disclosed version is worth attention for two reasons: it tells anyone scanning the internet which known vulnerabilities to try, and if it is old, it may no longer receive security fixes. The end-of-life software checker compares disclosed versions with a list of releases that no longer do.
Detection is observation and inference. A header can be set by a proxy rather than the server behind it, and markup can be left over from an old build, so treat each item as something to confirm, not as an inventory.
What it does not do
- It reads the home page of each host and nothing else. Software used on other pages, behind a login or on other subdomains is not seen.
- A CDN or reverse proxy in front of the site usually hides the server and software behind it.
- It recognises software from a fixed set of headers, cookie names and markup patterns. It does not run scripts, request other paths or fingerprint the server by its behaviour.
- Versions are what the site advertises. Vendors and Linux distributions often backport security fixes without changing the advertised version.
What happens to the domain you enter
The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.
Guides
A few things worth knowing
- Should I hide my server version?
- Yes, where you can. A version number helps attackers choose which known vulnerabilities to try, and visitors have no use for it. Most web servers and frameworks can be configured not to send it. Hiding it does not replace patching.
- Why does it show only my CDN?
- Because the CDN answers the request and sets its own headers, so the server behind it is rarely visible. That is normal.
- Does it run JavaScript or crawl the site?
- No. It requests the home page of each host, follows redirects, and reads the response's headers, cookie names and HTML. Nothing else is requested.

