Website security checkfor the whole site, not just malware.

A website security check tests how well a site is defended, not only whether it is infected: whether HTTPS is enforced with HSTS, which security headers the server sends, whether software versions are on show, how much WordPress exposes to strangers, and whether the domain sits on a blocklist. Run the free check below for the outside view, then use the self-audit for what no remote scanner can see.

Free, no signupRead-only, never logs inReport in about ten seconds

Security report
Ready
  • Transport: HTTPS and HSTSNot run
  • Security headersNot run
  • Version disclosureNot run
  • WordPress exposureNot run
  • Blocklist reputationNot run

What the report checks, section by section

Five areas, all visible from the public internet. Each one has a plain reason it matters and a fix your host or developer can apply.

01

Transport: HTTPS and HSTS

Every page should load over HTTPS, and plain-HTTP requests should be redirected to it. HSTS goes a step further: it tells browsers to refuse plain HTTP for your domain for months at a time, so a visitor on a hostile network cannot be quietly downgraded.

What good looks like
GET / over plain HTTP
301 to HTTPS
strict-transport-security
max-age=31536000

Fix: Redirect HTTP to HTTPS at the server and send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains only once every subdomain has a certificate.

02

Security headers

Five response headers limit what a browser lets an attacker do with your pages: load foreign scripts, frame your site, guess file types, leak full URLs, or ask for the camera. Each one is explained in the table below.

A typical first result
content-security-policy
missing
x-content-type-options
nosniff
x-frame-options
missing

Fix: Set them at the web server or CDN so they cover every response, including uploads and error pages, not only the pages WordPress renders.

03

Version disclosure

The Server and X-Powered-By headers, and the generator tag WordPress adds to every page, can announce exact versions. That turns finding a vulnerable site into a lookup: anyone can match your version against a list of known flaws.

What gets flagged
server
Apache/2.4.41 (Ubuntu)
x-powered-by
PHP/7.4.3

Fix: Hide versions in the server config (server_tokens off on Nginx, ServerTokens Prod on Apache, expose_php Off for PHP) and drop the generator tag. Then update anyway; a hidden version is still unpatched.

04

WordPress exposure

Three well-known paths tell an attacker a lot. xmlrpc.php accepts hundreds of password guesses in one request, the REST API users endpoint can list the exact usernames to guess against, and readme.html confirms WordPress and often its version.

What gets flagged
/xmlrpc.php
open
/wp-json/wp/v2/users
lists usernames
/readme.html
shows version

Fix: Block xmlrpc.php if nothing uses it, limit the users endpoint to logged-in requests, delete readme.html after each update, and turn on two-factor login so a leaked username is worth nothing.

05

Blocklist reputation

Google Safe Browsing decides whether browsers put a red warning in front of your site. The Spamhaus DBL and SURBL decide whether mail providers trust links to your domain. A listing usually means compromise, and costs traffic and email delivery until it is lifted.

Example output
Google Safe Browsing
not listed
Spamhaus DBL
not listed
SURBL
not listed

Fix: Find and remove the cause first, then request a review in Search Console or through each list’s removal form. Requests filed before the cleanup are refused.

Security headers, explained

Headers are instructions your server sends with every response. Browsers follow them, which makes them one of the cheapest protections a site can have.

Two cautions. A strict Content-Security-Policy can break page builders, chat widgets and analytics, so roll it out in report-only mode first. And on WordPress, prefer setting headers at the web server or CDN over a plugin, so they also cover files WordPress never touches.

This site sends every header in the table. Open your browser’s developer tools, select the page in the Network tab and look under Response Headers to see them.

Security headers, what each one does, and a sensible starting value
HeaderWhat it doesA sensible starting value
Strict-Transport-SecurityTells browsers to use HTTPS only for your domain, for a set period, so nobody on the same network can downgrade a visit to plain HTTP.max-age=31536000; includeSubDomains
Content-Security-PolicyLists where scripts, styles, frames and connections may come from. A script injected from an unknown domain is blocked instead of run.Start in Report-Only mode, tighten, then enforce
X-Content-Type-OptionsStops the browser guessing file types, so a file uploaded as an image cannot be run as a script.nosniff
X-Frame-OptionsStops other sites loading yours inside a hidden frame to trick visitors into clicking (clickjacking). The CSP frame-ancestors directive does the same job.SAMEORIGIN, or frame-ancestors 'self'
Referrer-PolicyLimits how much of the page address is passed on when visitors follow a link away. Full URLs can carry search terms, reset tokens or order numbers.strict-origin-when-cross-origin
Permissions-PolicySwitches off browser features the site never uses, such as camera, microphone and location, so injected code cannot ask for them.camera=(), microphone=(), geolocation=()

What a remote check can’t see: the self-audit

Most breaches start somewhere no scanner can look: an old plugin, a reused password, a backup nobody tested, a neighbour on the same server. Tick off the 14 items below. The boxes are only for you; nothing is saved or sent.

Updates

Updates

3 checks

Outdated plugins are the most common way into a WordPress site.

Passwords and two-factor login

Passwords and two-factor login

4 checks

A stolen password walks past every header and firewall rule.

Backups

Backups

3 checks

The only undo button after a breach, if it works.

Hosting isolation

Hosting isolation

4 checks

On shared hosting, one hacked site can reach its neighbours.

Harden it yourself, or hand it off

Most of the report can be fixed in an afternoon by whoever runs your server. If that is you and you would rather it were not, Delvok takes it on in one of two ways.

Security-first managed hosting

from$150/month

For sites that are healthy and should stay that way. Instead of patching a shared server one setting at a time, the site moves somewhere built for this.

  • Each site in its own isolated environment, not a shared account
  • Monitoring around the clock, with file-integrity scans every 5 minutes
  • If malware reappears while the site is under Delvok management, it is investigated and addressed at no extra charge

Already compromised? Malware rescue

$1,250flat. Launch pricing, normally $2,500.

If the check found signs of compromise, hardening comes second. Get the site cleaned, then closed up.

  • Most rescues start the same day; the site is clean within 24–48 hours
  • Files, database, users and scheduled tasks inspected and cleaned
  • Hardening, Google blacklist review requests and a move to managed hosting included

Questions, answered

What is a website security check?

An outside review of how well a site is defended: HTTPS and HSTS, security headers, software version disclosure, exposed WordPress endpoints and blocklist reputation. A malware scan asks whether the site is already infected. A security check asks how easy it would be to infect, and what would limit the damage if someone tried.

Is it safe to run the check on a live site?

Yes. It makes a handful of ordinary requests, the same kind a browser or search engine makes: your homepage and a few well-known public paths. It does not log in, submit forms, guess passwords or change anything.

Why do missing security headers matter if my site is not hacked?

Headers decide how much harm a single mistake can do. A Content-Security-Policy can stop an injected script from loading at all, HSTS stops a downgrade to plain HTTP on hostile Wi-Fi, and nosniff and frame protection close smaller tricks. They are set once at the server and cost nothing in speed.

Should I block xmlrpc.php?

If nothing you use needs it, yes. XML-RPC is used by some plugins, mobile apps and remote publishing tools, and most sites use none of them. Blocking it at the web server removes a favourite brute-force target and the pingback abuse that comes with it. If you do need it, rate-limit it and turn on two-factor login.

Can every check pass and the site still be at risk?

Yes. A remote check only sees the public surface. A reused password, an outdated plugin with a known flaw, missing backups or a compromised neighbour on shared hosting are all invisible from outside. That is what the self-audit on this page is for.

How often should I run a website security check?

After any change to hosting, a CDN or server configuration, after adding or removing plugins, and otherwise about once a month. Security headers in particular disappear quietly when a site moves host or a CDN setting changes. Continuous monitoring is better still.

Who runs websitesecuritycheck.co?

Delvok, a WordPress malware removal and security-first managed hosting service. The check and the self-audit are free to use. If you would rather have the fixes done for you, or the site is already compromised, that is the work Delvok does.