Read ordinary public responses.
Inspect response headers, a PHP-style cookie name and a bounded sample of homepage markup. No hidden-path enumeration or form submissions.
Start with the signals.
Know what needs a closer look.
Paste a website address. We’ll inspect its public response for PHP clues and any disclosed version.
Validating the address and checking the homepage…
Servers can hide PHP. Proxies can obscure the origin. A banner can be stale. This tool keeps those limits visible.
Inspect response headers, a PHP-style cookie name and a bounded sample of homepage markup. No hidden-path enumeration or form submissions.
PHP advertised in a header is stronger evidence than a .php link. WordPress markup can also come from a static export.
Confirm the PHP-FPM, web server or container version actually serving requests. A CLI version or WAF alone cannot establish patch status.
No. PHP can be hidden, limited to another path or subdomain, or run behind an edge service. This tool does not prove PHP is absent and does not establish vulnerability status.
No. It makes an ordinary HTTPS homepage request, with up to three validated homepage redirects. It sends no file uploads, memory-exhaustion requests or remote-code-execution probes.
The address is sent to this Cloudflare Worker to perform the check. The service does not save scan history, response bodies or cookie values. Cloudflare may process operational and security metadata. Turnstile is used to limit automated abuse. Downloaded reports are saved by your browser.
The report will describe limited visibility, or show an error. Challenge pages, unsupported redirects, timeouts and network restrictions are not treated as evidence that PHP is absent.