All checks

How well is your website secured?

The test takes a quick look at your website from the outside and checks HTTPS, the certificate, security headers, cookie settings and how up to date the detectable software is: WordPress with plugins, Next.js (for example on Vercel), Astro, jQuery, Bootstrap and Drupal. Nothing gets attacked, and we don’t try any logins.

What gets checked

  • Redirect from HTTP to HTTPS and certificate validity
  • Security headers such as HSTS, Content-Security-Policy and X-Content-Type-Options
  • Secure cookie settings
  • Insecure content loaded over HTTP
  • Visible server and CMS versions, compared with the latest release for WordPress
  • Update backlog of WordPress plugins: installed version against the latest on wordpress.org
  • Next.js, Astro, jQuery and Bootstrap: detected version against known vulnerabilities in the open OSV database
  • Whether a security.txt exists

Limits of this check

  • Malicious code in files or the database isn’t visible from the outside, so this test won’t find it.
  • We only check plugins that are visible in the page source, at most twelve and only those listed on wordpress.org. Premium plugins and themes aren’t compared, and individual vulnerabilities aren’t named.

Every check explained

What each point in the report means, why it matters and how to fix it.

HTTPS redirect

The site is also reachable unencrypted over HTTP.

How to fix it: Set up a permanent (301) redirect to HTTPS at your host or in .htaccess.

SSL certificate

The certificate is expired or invalid.

How to fix it: Check automatic renewal, for example Let’s Encrypt in your hosting panel.

HSTS

HSTS is missing or set too short. Browsers might still connect unencrypted on the first visit.

How to fix it: Set the header “Strict-Transport-Security: max-age=31536000; includeSubDomains”.

Content-Security-Policy

There’s no Content-Security-Policy. It limits the damage if someone else’s script gets into the page.

How to fix it: Start with a policy in report-only mode and tighten it step by step.

X-Content-Type-Options

The header X-Content-Type-Options: nosniff is missing.

How to fix it: Add the header “X-Content-Type-Options: nosniff”.

Framing protection

The page can be embedded in other sites. This enables clickjacking.

How to fix it: Set “X-Frame-Options: SAMEORIGIN” or “frame-ancestors 'self'” in the CSP.

Referrer-Policy

No Referrer-Policy set. Browsers then use their own default.

How to fix it: Set the header “Referrer-Policy: strict-origin-when-cross-origin”.

Permissions-Policy

No Permissions-Policy found. It lets you decide whether the page may use browser features such as the camera or location.

How to fix it: For example “Permissions-Policy: camera=(), microphone=(), geolocation=()”.

Visible versions

The server reveals software and versions. Attackers look specifically for known vulnerabilities in these versions.

How to fix it: Shorten the Server header and remove X-Powered-By, for example with “expose_php = Off”.

Mixed content

These resources load unencrypted over HTTP.

How to fix it: Switch all addresses to https://, on WordPress for example with search and replace in the database.

PHP version

This PHP version has vulnerabilities that CISA lists as actively exploited (PHP2Shell, no login needed). Updating to a patched release or later closes them.

How to fix it: In your hosting panel, pick the latest patch release of your PHP branch, ideally PHP 8.4. Then set “expose_php = Off” so the version is no longer visible.

PHP support

This PHP version no longer gets security updates. New vulnerabilities won’t be fixed.

How to fix it: Switch to PHP 8.4 and test on a copy of the website first to make sure the theme and plugins still work.

Actively exploited WordPress vulnerability

This WordPress version has a vulnerability that CISA lists as actively exploited (CVE-2026-119977). Updating to a patched release or later closes it.

How to fix it: Update WordPress right away, after making a backup. Turn on automatic security updates.

CMS version

WordPress is outdated.

How to fix it: Update WordPress, themes and plugins and enable automatic security updates.

Visible plugins

These several plugins are visible in the source. Keep them updated and remove what you don’t need.

Software components

At least one component has known severe vulnerabilities or no longer receives updates. Such flaws are now attacked automatically, often shortly after an update is released.

How to fix it: Update the affected components and republish the website. For Next.js on Vercel this means updating the dependencies and redeploying. Vercel keeps the platform up to date, not the framework inside your app.

Plugin updates

Several plugins are outdated although updates have been available for more than a week. Attackers now search for exactly these gaps automatically: AI agents compare security updates and turn them into attacks within a short time.

How to fix it: Install the updates in the WordPress dashboard under “Plugins” and switch on “Enable auto-updates” for every plugin. Delete plugins you don’t need instead of just deactivating them.

security.txt

There’s no security.txt, which security researchers would use to report vulnerabilities to you.

How to fix it: Provide at least “Contact:” and “Expires:” at /.well-known/security.txt.

Matching package

from€390

wwwery safe

Clean up a hacked website and secure it so it doesn’t happen again.

Questions

My website was hacked. Does this test help?

It shows configuration weaknesses but won’t find hidden malicious code. If you’ve been hacked, get in touch directly. That’s exactly what the wwwery safe package is for.

More checks