Inputs
Enter a public WordPress URL. The checker requests the common XML-RPC endpoint in a bounded way.
Free public URL tool
Check public XML-RPC endpoint reachability and POST-only response behavior without treating visibility as an automatic vulnerability.
Problem, cause, fix, verify
Problem
XML-RPC can be expected for some workflows and unwanted for others, so teams need public evidence before changing access rules.
Audience
WordPress owners, agencies, and security reviewers deciding whether XML-RPC deserves follow-up.
First check
Enter a public WordPress URL. The checker requests the common XML-RPC endpoint in a bounded way.
Verify
If it is not needed, plan a reversible access-control change and monitor login, publishing, and integration behavior afterward.
Editorial trust
On this page
Decision Support
For: WordPress owners, agencies, and security reviewers deciding whether XML-RPC deserves follow-up.
Use The Tool
Enter a public WordPress URL. The checker requests the common XML-RPC endpoint in a bounded way.
Review endpoint status, reachability, and whether the common POST-only message appears.
If XML-RPC is reachable, confirm whether Jetpack, mobile apps, legacy integrations, or publishing workflows need it.
If it is not needed, plan a reversible access-control change and monitor login, publishing, and integration behavior afterward.
Reachable XML-RPC is not automatically a vulnerability. Use the result to decide whether the endpoint is expected for this site.
Limitations