Outil gratuit, aucun compte requis

Free WordPress Security Configuration Checker

Check eight externally observable WordPress configuration areas: XML-RPC, wp-login.php, debug leakage, directory listing, version disclosure, security headers, REST user enumeration, and sensitive public paths.

Aussi connu sous le nom de: WordPress hardening checker, XML-RPC and REST API test

Preuve montrée avec sourceAucun compte requisAucune métrique inventée

Exécutez un contrôle réel ci-dessus

Soumettez une URL publique, un domaine ou un mot-clé. Novaverb ne montrera que les preuves que cet outil peut réellement récupérer ou mesurer.

Modèle de preuve

Savoir ce que le résultat prouve

This check captures public HTTP evidence for eight WordPress configuration areas: XML-RPC, the standard login path, debug leakage, directory listing, version disclosure, six response headers, REST API user enumeration and selected sensitive paths. It keeps each observation separate and publishes no general security score.

1. Source

Bounded live HTTP observations from the submitted public WordPress origin. Le résultat identifie d'où proviennent ses preuves.

2. Limite

This is a non-intrusive configuration review of selected public HTTP responses. It does not test passwords, exploit vulnerabilities, enumerate plugins, or prove that a WordPress site is secure.

3. Prochaine action

Utilisez la découverte pour vérifier un problème, puis connectez un espace de travail lorsque vous avez besoin d'historique, de surveillance ou d'analyse à l'échelle du site.

How to read this WordPress configuration result

Observation, not exploitation

The checker recognizes selected public response signatures. It sends no attack payload, login attempt, password test or component enumeration request.

No composite security score

Each of the eight areas stands on its own evidence. A clean header result cannot cancel an exposed debug log, and an unavailable response never becomes a pass.

Fix, deploy, re-check

Prioritize exposed logs and sensitive files, then public user enumeration and unnecessary endpoints. Re-run the exact check after deploying each configuration change.

Obtenez la bonne réponse

Ce qu'il faut soumettre - et ce qu'il faut éviter

Submit a public WordPress domain or any URL on that site. The checker normalises the address to the final public origin before requesting WordPress paths. Private and reserved targets are refused, and the result may say WordPress was not confirmed when the site hides or changes all recognizable public signals.

Utilisez-le comme ceci

your-wordpress-site.comA public WordPress domain works, and the checker normalizes the address before the bounded requests.

https://www.your-wordpress-site.com/blogA full page URL works too; WordPress configuration paths are checked at the final public origin.

Évitez cela

localhost / 10.0.0.8Private and internal targets are refused by the public-IP safety boundary.

Expecting a vulnerability scanThis tool checks selected public configuration evidence only; it does not exploit, authenticate, or enumerate installed components.

Méthodologie publique

Exactement comment ce résultat est produit

Every request passes through the public-IP safety boundary and every redirect target is checked again. The checker recognizes specific response signatures rather than treating every HTTP 200 as exposure, runs a bounded set of paths, and discards raw response bodies before the result is stored or displayed.

Nous récupérons l'adresse publique soumise via un contrôle de sécurité IP fixe et vérifions chaque destination de redirection.
We request a bounded WordPress path set and recognize exact login, XML-RPC, REST, directory-index, debug and sensitive-file signatures.
We read the homepage for WordPress version signals and six selected browser security headers.
We discard raw response bodies and report eight named configuration observations without creating a composite security score.

Construit sur des normes publiques

Les normes internationales auxquelles cette vérification s'applique.

WordPress documentation defines XML-RPC and REST API behavior, while RFC 9110 defines the HTTP responses observed. The response-header section applies the selected OWASP Secure Headers set. These references describe configuration surfaces; none turns a public response into proof of a vulnerability.

WordPressXML-RPC

WordPress XML-RPC support

Recognises whether the standard public XML-RPC endpoint answers with a WordPress XML-RPC signature.

Lisez la spécification

WordPressREST API

WordPress REST API

Checks REST discovery separately from whether the public users endpoint returns account identifiers.

Lisez la spécification

IETFRFC 9110

HTTP Semantics

Reads each bounded path's response status while preserving unavailable and restricted outcomes.

Lisez la spécification

OWASPSecure Headers

OWASP Secure Headers Project

Reports presence of the six selected response-header controls without claiming their policy values are complete.

Lisez la spécification

Nous listons un standard uniquement lorsque cet outil le lit ou le mesure réellement. Lorsqu'un signal est en dehors d'une vérification en direct, le résultat le dit plutôt que d'impliquer une couverture.

Questions courantes

WordPress Security Configuration Checker FAQ

What does the WordPress Security Configuration Checker inspect?

It observes eight public configuration areas: XML-RPC, wp-login.php, debug output, directory listing, WordPress version disclosure, six security headers, the REST API user endpoint, and selected sensitive WordPress paths.

Is this a WordPress vulnerability scanner?

No. The checker sends bounded public HTTP requests only. It does not exploit vulnerabilities, test passwords, enumerate plugins or themes, inspect source code, or look up known software vulnerabilities.

Should XML-RPC always be disabled?

Not always. XML-RPC can support publishing clients, integrations and pingbacks. If nothing you use needs it, restrict or disable it; if it must stay public, protect it with rate limiting and monitoring.

Is a public wp-login.php page automatically insecure?

No. The standard login page is normally public, so reachability is a review item rather than proof of a defect. Use strong passwords, multi-factor authentication, rate limiting and monitoring instead of relying on a hidden URL.

How does the checker detect exposed WP_DEBUG output?

It looks for recognizable PHP and WordPress error signatures in the captured homepage and public debug.log response. It never displays or stores the raw log or configuration-file contents.

What counts as WordPress directory listing?

The checker requests selected wp-content directories and looks for an actual generated index page, such as an Index of page with a parent-directory listing. A normal application response is not labeled as directory listing.

How can WordPress disclose its version?

A page can disclose a WordPress version through its generator metadata. Removing that metadata reduces easy fingerprinting, but installing security updates remains the important control.

Is the WordPress REST API unsafe?

No. The REST API is a normal WordPress feature. The relevant observation is whether the public users endpoint returns account identifiers; the checker reports REST availability and user enumeration separately.

Which sensitive WordPress paths are checked?

The bounded path set covers the public readme and license files, the install and setup screens, debug.log, and one common wp-config.php backup name. Only recognized content is labeled exposed, and raw sensitive content is discarded.

Does a clean configuration result prove the site is secure?

No. It only means the selected public observations did not show those configuration exposures at that moment. Plugin vulnerabilities, authorization flaws, malware, weak accounts and server-side issues require separate authorized testing.

Plus de vérifications gratuites