About PHP Version Checker
About PHP Version Checker: this independent utility helps developers and website owners interpret public PHP signals without mistaking a guess for a version. It provides one bounded check and practical ways to verify the answer with your own access. The project uses PV as its short name. It is not a PHP Group product, an official security audit, or a substitute for a server inventory.
Who makes this tool, and why?
This independent project is maintained by the operator of this website under the PV project name. It was built for developers and site owners who need a useful answer when public headers hide a version. No individual author biography or company identity is claimed without operator-supplied details.
What we check
The tool validates a public HTTP or HTTPS URL, starts with HEAD, and uses a GET of the same page when needed. A WordPress generator declaration in the body may permit one same-origin /wp-json/ GET. It looks for an explicit PHP version in identifying headers, a PHP session cookie name, and selected HTML generator tags. It distinguishes confirmed public disclosures from possible technology signals. It does not scan a host, test vulnerabilities, request hidden diagnostic paths, or use privileged credentials.
How the documentation is maintained
The byline “PV documentation” identifies this project’s documentation, not an independently verified individual expert. Technical explanations link to primary documentation, and the displayed update date changes only when the content is reviewed. Support deadlines are checked against php.net and its official website source. We do not invent ratings, testimonials or usage statistics.
Public headers can be spoofed, cached, or removed. A confirmed result means a version was reported in this response, not that every server behind the domain runs it. Read the detection method before acting on the result.
Access and limits
No account or payment is required. Checks share a five-second total deadline, allow at most one redirect and four HTTP requests, and cache all outcomes for ten minutes. Redirect destinations undergo full safety checks; 403 and 429 responses stop the check without retries. Requests to private networks and reserved addresses are rejected. The application uses a temporary result cache and host-level limits to reduce repeated traffic. If disk storage is unavailable, an in-memory cache uses the same ten-minute expiry within the current server process.
For a concrete next step, use the PHP version checker or the six owner-side verification paths. Our privacy notice explains URL handling and optional analytics.