Is your website secure, or does it just look that way?

The padlock in the address bar only says the connection is encrypted. The check below looks at what visitors never see: the certificate, the route from http to https, the security headers and the version numbers the site gives away.

Last checked:

Check your website's security

Free. We read the front page and the domain's public DNS, the way a browser and a mail server would. Nothing is changed on the site and nothing is e-mailed.

“Not secure” in the address bar

The browser shows “Not secure” when a page arrives over plain http:// without encryption. What a customer types into your contact form could then be read on the way. A certificate the browser cannot accept gives a warning page before anyone gets in. The usual causes:

  • No certificate. Most hosts offer a free Let’s Encrypt certificate; switch it on.
  • Expired certificate. Certificates are valid for a limited period. Free ones normally renew themselves about 30 days before expiry, but the automation can stall, for example after a move of host or DNS.
  • Wrong name. The certificate covers example.dk but not www.example.dk, or the other way round.
  • No redirect. Someone typing the bare address still lands on http://. A permanent (301) redirect fixes that.

All fine, but the site behaves oddly? Look for mixed content: the page comes over https:// but loads a script or stylesheet over http://. Browsers block such files on an encrypted page, so a menu or form stops working. It often follows a move, when old addresses linger in the theme or database.

HSTS: always use https

The Strict-Transport-Security (HSTS) header tells browsers to go straight to https:// for a set period. OWASP suggests max-age=63072000; includeSubDomains; preload, with a warning to read up carefully first. includeSubDomains requires every subdomain to work on https, and preload is hard to undo, so start with max-age=31536000 alone. Our check accepts HSTS from six months.

Security headers

Headers are short messages the server sends with every page. Visitors never see them; browsers obey them. We follow the recommendations of OWASP, an open community for web security, and MDN’s reference pages.

Content-Security-Policy

Decides where scripts and other content may come from, so injected code does less harm. OWASP calls it complex; start with report-only.

frame-ancestors

Stops other sites showing yours in a frame to trick people into clicking (clickjacking). Preferred over the older X-Frame-Options.

X-Content-Type-Options

nosniff forbids the browser to guess file types, which some attacks rely on.

Referrer-Policy

strict-origin-when-cross-origin limits what other sites learn about where a visitor came from.

Permissions-Policy

Switches off features the site never uses, such as camera, microphone and location.

X-XSS-Protection is missing on purpose. OWASP advises not setting it, or switching it off explicitly. Guides saying otherwise are dated.

Version numbers and updates

Many servers state their exact version in Server or X-Powered-By, and WordPress does so in a generator tag in the HTML. Not a hole in itself, but an attacker can look up known flaws in that version in seconds. OWASP recommends removing Server and X-Powered-By.

The most important defence is still keeping WordPress, the theme and plugins up to date. It is one of nine pieces of advice that sikkerdigital.dk (Danish Agency for Civil Protection) gives businesses with fewer than 50 employees, next to secure login, backup and an incident plan.

sikkerpånettet.dk and our check

sikkerpånettet.dk is a free Danish check backed by partners such as the Danish Agency for Digital Government and Punktum.dk. It looks at HTTPS settings, IPv6 and DNSSEC for the website, and at SPF, DKIM, DMARC and encrypted mail. It is a good place to start, and it covers IPv6 and DNSSEC, which we do not. Our report puts cookies before consent, accessibility, e-mail protection and security in one place. Use both.

What we do not test: we see only what the server shows from outside. We do not try passwords, hunt for vulnerable plugins or attempt to break in. A green report means the basic setup is in order, not that the site cannot be hacked.

Questions about website security

What is a security certificate?

A digital ID that proves to the browser that the site belongs to the domain and makes encryption possible. Also called an SSL or TLS certificate. The encryption is the same whether the certificate is free or paid.

My website has been hacked. Can the check see it?

Rarely; a hack usually hides in files or the database. Change passwords, ask your host to scan, and restore a backup from before the attack.

Can a Content Security Policy break my site?

Yes, if it is too strict. So start with Content-Security-Policy-Report-Only, which only reports problems. Our check shows when a policy is only being tested.

Why is TLS 1.0 a problem?

TLS 1.0 and 1.1 are old encryption versions with known weaknesses; current browsers refuse them. Turn them off in the host’s control panel or on the server.

Fixed price, no commitment

Get it fixed

Tell us which website it is and what the check showed. A person answers with a fixed price before any work starts.

  • A fixed price before we start
  • An answer by e-mail, no calls
  • Your details are used only to answer you

Fields marked with * are required.

What should be fixed?