Contact Wenver Song, the operator of PHP2ShellChecker.io, at fanran10130@gmail.com. This is the contact point for questions about this website, incorrect content, unexpected checker behavior, privacy requests and security reports affecting this service.
Last updated: 2026-10-22
Choose a clear subject
- Checker issue: a request fails, a result looks inconsistent or a page does not work.
- Content correction: a PHP version, source link or explanation needs review.
- Privacy request: you want information about data processing or to exercise an applicable privacy right.
- Security report: you believe you found a security weakness in PHP2ShellChecker.io itself.
- General inquiry: a question about the project or permission to reuse material.
Adding one of these labels to the subject helps identify the nature of your message. No particular subject format is required for a privacy request.
What to include in a checker or content report
- The affected page URL and, where relevant, the public domain you checked.
- The approximate date and time, with your time zone.
- The result or error text, what you expected to happen and the steps needed to reproduce it.
- Your browser and device type if the problem concerns the interface.
- A link to an official PHP or package-vendor notice when suggesting a version or patch correction.
Share only what is needed. Please remove access tokens, cookies, personal details and customer data from screenshots or logs. Do not send passwords, private keys, Cloudflare API tokens, Turnstile secrets, database exports or private server configuration. The normal checker does not need those materials.
Privacy requests
Use the same email address and describe the request, the relevant interaction and an approximate date range. If you previously emailed us, writing from that same address can help locate the conversation. We may request proportionate information to confirm identity or authority before disclosing or changing personal data; do not send identity documents unless a specific need has been explained.
The Privacy Policy describes the types of information processed, retention criteria and rights that may apply. We will handle valid requests within the time required by applicable law. Some requests may be limited by legal obligations, security needs or the inability to identify a record reliably.
Responsible security reporting
For a weakness in this website, email a concise description, the affected URL and the minimum non-destructive steps needed to understand it. Avoid accessing another person's data, causing service disruption or testing against third-party sites. This contact address does not authorize intrusive testing and is not a paid bug-bounty program.
If the issue concerns PHP itself, a hosting provider or a website you do not operate, use that project's or provider's official security reporting channel. We cannot patch another organization's infrastructure.
Replies and support scope
This project is maintained independently. There is no guaranteed response time or round-the-clock support service; privacy requests remain subject to applicable statutory deadlines. If your production website may be exposed, contact your hosting provider or administrator immediately and use the patch guide rather than waiting for an email reply here.
Contacting us opens your own email application or provider. There is no website contact form, attachment-upload system or newsletter signup. Your message and address are handled as described in our Privacy Policy. Read About for the project's methodology and Terms of Use for service conditions.