Skip to content

Website scanner

Guide to every check

For each check: what it is, why it matters and how to fix it. If in doubt, show this page to your web developer or IT supplier – it is written so you can talk from the same page.

The website: encryption, headers and cookies

Encryption, security headers and cookies on the front page – what every browser gets to see.

HTTPS (encryption)

What is it?

HTTPS encrypts the connection between the visitor and your site and proves with a certificate that it is your site.

Why does it matter?

Without HTTPS, anyone on the same Wi-Fi or at the provider can read and change what is sent – including passwords and forms. Browsers warn against sites without HTTPS.

How to do it

  1. Ask your web host for a free certificate (Let’s Encrypt) – most offer it with one click.
  2. If the site is behind Cloudflare: use the SSL/TLS mode “Full (strict)”.
  3. Check the certificate’s expiry date and TLS versions on SSL Labs (see Go further).

From http:// to https://

What is it?

When someone types the address without https://, the browser often starts on the unencrypted version.

Why does it matter?

If the unencrypted version does not redirect, some visitors stay on an unencrypted page.

How to do it

  1. Set up a permanent redirect (301) from http:// to https:// – most web hosts have a button for it.
  2. On Cloudflare: SSL/TLS → Edge Certificates → “Always Use HTTPS”.
  3. Then turn on HSTS (see the next item).

Redirect to another domain

What is it?

The front page sends visitors on to another domain.

Why does it matter?

Headers, cookies and content live on the other domain, so that is where they need checking.

How to do it

  1. Run the test again on the domain the site redirects to.

HSTS

What is it?

Strict-Transport-Security is a header that tells the browser: “always use HTTPS here”.

Why does it matter?

Without HSTS, an attacker on public Wi-Fi can keep a visitor on the unencrypted version (“SSL stripping”).

How to do it

  1. Add the header Strict-Transport-Security: max-age=31536000.
  2. Add ; includeSubDomains once you are sure all subdomains work over HTTPS.
  3. On Cloudflare: SSL/TLS → Edge Certificates → HSTS.

Content Security Policy (CSP)

What is it?

Content-Security-Policy tells the browser which scripts, images and frames the page may load – and from where.

Why does it matter?

If an attacker manages to inject a script into your page, CSP can stop it from running and sending data away.

How to do it

  1. Start with Content-Security-Policy-Report-Only so nothing breaks while you learn what the page uses.
  2. A good starting point: default-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'.
  3. Avoid 'unsafe-inline' in script-src; use a nonce or hash instead.
  4. If you use WordPress or another CMS, find a well-maintained plugin or ask your developer.

X-Content-Type-Options

What is it?

A header asking the browser to trust the file type the server states.

Why does it matter?

Without it, an uploaded file can in some cases be run as a script.

How to do it

  1. Add the header X-Content-Type-Options: nosniff to all responses.

Clickjacking protection

What is it?

States whether other sites may show your page inside a frame (iframe).

Why does it matter?

An attacker can lay your page invisibly over their own and trick people into clicking buttons on yours.

How to do it

  1. Add frame-ancestors 'self' to your CSP – or the header X-Frame-Options: SAMEORIGIN.

Referrer-Policy

What is it?

Controls how much of the address the browser tells the next site when a visitor clicks on.

Why does it matter?

Addresses can contain search terms, IDs or tokens that should not leave the house.

How to do it

  1. Add Referrer-Policy: strict-origin-when-cross-origin (or no-referrer).

Permissions-Policy

What is it?

Blocks browser features such as camera, microphone and location for the page and everything it embeds.

Why does it matter?

If a foreign script gets in (for example via an ad), it cannot ask for access to anything you have blocked.

How to do it

  1. Add for example Permissions-Policy: camera=(), microphone=(), geolocation=().

Version numbers

What is it?

Headers such as Server and X-Powered-By can reveal for example “Apache/2.4.41” or “PHP/7.4.3”.

Why does it matter?

Hiding it costs nothing, and an attacker has to work a little harder to find matching known holes. Updating is still what matters most.

How to do it

  1. Update whatever the version shows.
  2. Apache: ServerTokens Prod and ServerSignature Off.
  3. nginx: server_tokens off;
  4. PHP: expose_php = Off in php.ini.

Cookies

What is it?

Cookies remember, for example, that you are logged in. Three small flags decide how well they are protected: Secure (HTTPS only), HttpOnly (cannot be read by scripts) and SameSite (not sent along from other sites).

Why does it matter?

A stolen login cookie is as good as the password.

How to do it

  1. Set Secure on all cookies.
  2. Set HttpOnly on all cookies scripts do not need to read – especially login and session.
  3. Set SameSite=Lax (or Strict).
  4. We only see cookies from the front page; login pages may set others.

Tracking before consent

What is it?

We open the front page in a real browser – as a visitor who has not yet clicked the cookie banner – and see which cookies are set and which known tracking services the page contacts.

Why does it matter?

Under EU cookie rules and the GDPR, cookies for analytics and marketing may only be set once the visitor has said yes. Tracking before consent is one of the most common mistakes on websites – and anyone can see it.

How to do it

  1. Log in to your consent tool (such as Cookiebot, Cookie Information or CookieYes) and check that analytics and marketing scripts only run after consent.
  2. If you use Google Tag Manager: make tags wait for consent (Consent Mode), and remove scripts added directly to the theme outside the consent tool.
  3. Test it yourself: open the site in a private window, do not click the banner, and look under developer tools → Application (or Storage) → Cookies.
  4. We only see the front page and only known services. Other pages and unknown scripts may behave differently, and some sites show different content depending on the country.

Mixed content

What is it?

An encrypted page that loads something over unencrypted http://.

Why does it matter?

The unencrypted part can be changed on the way. Scripts over http:// can take over the whole page; that is why browsers block them.

How to do it

  1. Change the addresses from http:// to https:// in the theme or content.
  2. As a safety net: add upgrade-insecure-requests to your CSP.

Scripts from other domains

What is it?

Scripts for analytics, chat, ads and fonts loaded from other companies’ servers.

Why does it matter?

A foreign script runs with the same rights as your own. If the supplier is hacked, so is your site – and many of them pass on data about your visitors.

How to do it

  1. Go through the list: do you still use them all?
  2. Self-host what you can (fonts, for example).
  3. Use Subresource Integrity (integrity=…) on fixed files from CDNs.
  4. Remember that scripts setting cookies or sending personal data need consent.

CMS and version

What is it?

Many systems such as WordPress write their name and version in the page code.

Why does it matter?

It is not a hole in itself, but it tells attackers exactly which known holes to try if the version is old.

How to do it

  1. Make sure the system and all plugins and themes are updated – turn on automatic updates.
  2. Remove the generator tag (in WordPress via a security plugin or the theme’s settings).

Old jQuery

What is it?

jQuery is a very widely used JavaScript library.

Why does it matter?

Versions before 3.5.0 have known holes that can lead to XSS if the site uses them in a certain way.

How to do it

  1. Update to the latest jQuery 3.x (or 4.x) and test the site afterwards.
  2. If you use WordPress: update WordPress, the theme and plugins – old jQuery often comes from an outdated theme.

security.txt

What is it?

A small text file at /.well-known/security.txt (RFC 9116) with contact details for security issues.

Why does it matter?

If someone finds a hole, they need to know where to report it – otherwise it may end up on social media or not be reported at all.

How to do it

  1. Put a file at https://yourdomain.com/.well-known/security.txt with, for example:
    Contact: mailto:security@yourdomain.com
    Expires: 2027-11-19T00:00:00Z
    Preferred-Languages: en
  2. Remember to renew Expires before the date runs out.

Email: can others send in your name?

Fake emails that appear to come from your domain are the most common route to fraud against businesses – fake invoices and “the CEO asks you to transfer money”.

Domain without mail? Lock it down

If you do not use a domain for mail (for example an extra domain for a campaign), it can still be abused as a fake sender. Three DNS records lock it down:

Mail server (MX)

What is it?

MX records tell which servers receive mail for the domain.

Why does it matter?

Domains without mail can also be abused as a fake sender. They need locking down with SPF and DMARC.

How to do it

  1. Domain without mail? Add three records: MX 0 . (null MX), SPF v=spf1 -all and DMARC v=DMARC1; p=reject;

SPF

What is it?

SPF is a list in DNS of the servers allowed to send mail from the domain.

Why does it matter?

Without SPF, recipients cannot tell your mail from fake mail sent from any server.

How to do it

  1. Find everyone sending mail in your name: the mail system (such as Microsoft 365 or Google Workspace), the newsletter, the web shop, the accounting system.
  2. Combine them in one TXT record, for example v=spf1 include:_spf.google.com -all.
  3. There may only be one SPF record, and it may need at most 10 lookups.
  4. End with -all (or ~all together with DMARC).

DMARC

What is it?

DMARC tells recipients what to do with mail that claims to come from your domain but fails SPF or DKIM – and where to send reports.

Why does it matter?

Without DMARC (or with p=none), fraudsters can send mail with your exact sender address. It is the basis of fake invoices and CEO fraud.

How to do it

  1. Start by monitoring: a TXT record on _dmarc.yourdomain.com with v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com.
  2. Read the reports for a couple of weeks and make sure all your real senders pass SPF or DKIM.
  3. Move up to p=quarantine and then p=reject.
  4. The reports are XML and hard to read; ask your IT supplier or use a free analysis tool.

DKIM

What is it?

DKIM digitally signs outgoing mail so the recipient can see that it really comes from you and has not been changed.

Why does it matter?

DKIM is what makes DMARC work, also when mail is forwarded.

How to do it

  1. Turn on DKIM in your mail system (Microsoft 365: Defender → Email authentication → DKIM; Google Workspace: Admin → Gmail → Authenticate email).
  2. Add the DNS records the system gives you.
  3. Check a mail from the domain: in the DKIM-Signature header, the selector follows s=.

MTA-STS

What is it?

MTA-STS asks other mail servers to always encrypt mail to your domain.

Why does it matter?

Without MTA-STS, an attacker between two mail servers can strip the encryption and read the mail on the way. It is rare, but easy to prevent.

How to do it

  1. Put a policy file at https://mta-sts.yourdomain.com/.well-known/mta-sts.txt with version: STSv1, mode: testing, your MX names and max_age.
  2. Add a TXT record on _mta-sts.yourdomain.com: v=STSv1; id=20261119.
  3. Set up TLS-RPT and switch to mode: enforce once the reports are clean.

TLS-RPT

What is it?

TLS-RPT asks other mail servers to send you a report when they cannot deliver mail to you encrypted.

Why does it matter?

Then you notice problems with encryption before they become a problem.

How to do it

  1. Add a TXT record on _smtp._tls.yourdomain.com: v=TLSRPTv1; rua=mailto:tls-reports@yourdomain.com.

The domain and DNS

The foundation of the domain: can answers be forged, who may issue certificates, do names point at something that no longer exists – and are there registered domains that look like yours?

DNSSEC

What is it?

DNSSEC signs the domain’s DNS answers so a resolver can tell whether they are genuine.

Why does it matter?

Without DNSSEC, an attacker can in rare cases trick a resolver into sending visitors or mail to the wrong place.

How to do it

  1. Turn on DNSSEC with whoever runs your DNS (for example Cloudflare: DNS → Settings → DNSSEC).
  2. Add the DS record at your registrar.
  3. If DNSSEC is broken: fix it at once – wrong signatures make the domain unreachable for many.

CAA

What is it?

CAA records in DNS state which certificate authorities (such as Let’s Encrypt) may issue certificates for your domain.

Why does it matter?

It makes it harder for an attacker to trick another authority into issuing a fake certificate for your domain.

How to do it

  1. Find out who issues your certificates (look at the certificate in the browser or ask your host).
  2. Add for example 0 issue "letsencrypt.org" as a CAA record – and one for each authority you use.
  3. If the site is behind Cloudflare, also add the authorities Cloudflare uses, or renewal can fail.

Dangling CNAME

What is it?

A CNAME record sends a name on to another service, such as a shop or blog at a provider.

Why does it matter?

If the service is gone but the record remains, a stranger can create a new service with the same name and show their own content on your domain (“subdomain takeover”).

How to do it

  1. Delete the CNAME record if the service is no longer used.
  2. Or recreate the service at the provider.
  3. We only check the name you entered and www. Go through your other subdomains too.

Domains that look like yours

What is it?

We make up to 60 variants of your domain – other endings (.com, .net, .eu …), letters that look alike (l and 1, rn and m) and typical typos – and look up in DNS whether they are registered. We do not visit them.

Why does it matter?

Fraudsters register domains that look like a real company’s and send fake invoices or ask to change an account number. It is hard to spot in a busy inbox.

How to do it

  1. Go through the list: do you recognise the domains? The ones that “can receive mail” are the ones that can be used for fake mail.
  2. Consider registering the most important variants yourself (such as .com if you have .dk) and redirecting them to your real site.
  3. Tell staff and accounts to look for typos in the sender – and never change an account number based on an email alone. Call and confirm.
  4. If a domain is used for fraud in your name, contact the registrar and report it to the police.