Website security checkup · 2026-11-21T19:29:14Z
F

Sample: local test server built to be weak

Score 21 out of 100. 10 to fix, 2 to improve, 3 fine. 10 requests made.

This is a sample report. It was made against a local test server on the author's machine, not against a real website.

Fix these first (10)

FixContent Security Policy limits what the page can load

No Content-Security-Policy header.

What it means: A Content Security Policy lists where scripts and images may come from. It is the main defence that stops injected scripts from stealing data.

How to fix it: Start with a report-only policy, then enforce one such as "default-src 'self'". Avoid 'unsafe-inline' and '*' where you can.

FixOther sites cannot put yours inside a hidden frame

Neither X-Frame-Options nor CSP frame-ancestors is set.

What it means: Without frame protection, another site can show your page invisibly under a fake button and trick visitors into clicking it (clickjacking).

How to fix it: Send 'X-Frame-Options: SAMEORIGIN' or a CSP rule 'frame-ancestors 'self''.

FixPrivate page addresses are not leaked to other sites

No Referrer-Policy header.

What it means: Without a Referrer-Policy, the full address of the page a visitor came from (which can include private details) may be passed to every site you link to.

How to fix it: Send 'Referrer-Policy: strict-origin-when-cross-origin'.

FixBrowser features such as camera and location are restricted

No Permissions-Policy header.

What it means: A Permissions-Policy switches off browser features your site does not use, so a compromised script cannot turn them on.

How to fix it: Send 'Permissions-Policy: camera=(), microphone=(), geolocation=()' and allow only what you need.

FixCookies carry the right protection flags

1 cookie(s) set. session lacks HttpOnly, SameSite

What it means: Secure keeps a cookie off insecure connections, HttpOnly hides it from page scripts, and SameSite limits cross-site use. Missing flags make login cookies easier to steal.

How to fix it: In your site or framework settings turn on Secure, HttpOnly and SameSite=Lax (or Strict) for session and login cookies.

FixServer does not announce its software version

Software details are visible: Server: Apache/2.4.29 (Ubuntu)

What it means: Headers such as 'Server: Apache/2.2.15' tell attackers exactly which known bugs to try.

How to fix it: Hide or shorten the banner (for example 'ServerTokens Prod' in Apache or 'server_tokens off' in nginx) and remove X-Powered-By.

FixSecure pages do not load insecure files

1 script/style/frame and 1 image/media link(s): http://cdn.example.test/a.js, http://cdn.example.test/p.png

What it means: A secure page that pulls in scripts, styles or images over plain http:// can be tampered with on the way, and browsers may block or warn about it.

How to fix it: Change those http:// links to https:// (or to relative links). Check your page builder, theme and any hard-coded addresses.

FixSite software is not announcing an old version

Generator tag says 'WordPress 5.2.4', older than 6.0.

What it means: Many sites say which CMS and version built them in a hidden tag. An old version usually has published security holes.

How to fix it: Update the CMS, themes and plugins to the latest release, then remove the generator tag (most CMSs have a setting or a one-line filter for this).

FixPrivate files are not downloadable

Reachable from the internet: /.env

What it means: Files such as .env, .git or backup copies of config files can hold passwords and source code. If a request for them succeeds, anyone can fetch them.

How to fix it: Remove the file from the public web folder, or block it in the server config, and then change any password or key that was inside it.

FixEmail: DMARC record tells receivers what to do with fakes

No DMARC record found at _dmarc.example.test.

What it means: DMARC tells other mail systems to reject or quarantine mail that fails SPF/DKIM checks, which stops most look-alike emails.

How to fix it: Add a TXT record at _dmarc.<your domain>, starting with 'v=DMARC1; p=none; rua=mailto:<you>' to watch, then move to p=quarantine and later p=reject.

Worth improving (2)

ImproveBrowsers are told to always use HTTPS (HSTS)

HSTS is set but max-age=300 is under 180 days.

What it means: The Strict-Transport-Security header tells browsers to refuse the insecure version of your site for a set time, which blocks downgrade tricks.

How to fix it: Add the header 'Strict-Transport-Security: max-age=31536000; includeSubDomains' once every page and subdomain works over HTTPS.

ImproveA security contact is published (security.txt)

No security.txt with a Contact line found.

What it means: A small file at /.well-known/security.txt tells researchers where to report a problem privately instead of posting it or ignoring it.

How to fix it: Create /.well-known/security.txt with a 'Contact:' line (an email or form) and an 'Expires:' date. securitytxt.org has a generator.

Looking good (3)

OKSecurity certificate is valid and not about to expire

Issued by Test CA, expires 2027-02-19 (89 days left), TLSv1.3.

OKBrowsers are told not to guess file types

X-Content-Type-Options: nosniff.

OKEmail: SPF record limits who can send as your domain

SPF found with soft fail (~all): v=spf1 include:mail.example.test ~all

Good to know (1)

NoteVisitors are sent to the secure (HTTPS) version

Nothing answers on plain http:// (port closed). That is fine unless customers type http:// addresses.