Trois-Rivières, serving all of Quebec 450 231-3836 info@oktosolutions.ca

Free tool

Free website security scanner

Is your website secure? Enter its address. In a few seconds you get a grade from A+ to F, what is missing, and the exact line to add in nginx, Apache or Cloudflare.

A website security scanner checks, from the outside, what your site shows any visitor: SSL certificate, HTTPS redirect, security headers, visible software versions, cookies, mixed content, and the domain’s SPF and DMARC records. It gives a grade from A+ to F, along with a copy-ready fix for every finding.

Scan your website’s security

An address is all it takes. No attack, a single page visit.

What the tool checks

  • SSL certificate, expiry date
  • HTTPS redirect, HSTS
  • Security headers
  • Visible software versions
  • Domain SPF and DMARC

Free, no account needed.

The short answer

What is a website security scanner?

A website security scanner looks at your site the way an ordinary visitor would, then flags anything that weakens its protection. It does not try to break in: it reads what the server sends to everyone. Is the SSL certificate valid, issued for the right name, far from expiry? Does the site force HTTPS? Are security headers such as Content-Security-Policy or HSTS in place? Does the page display the WordPress version, or the version of an old jQuery library? Are session cookies protected? Does the domain have SPF and DMARC records to stop people from sending fake emails in its name? The result is a grade from A+ to F, with a concrete fix for every finding. You may know it as a security headers check, an SSL checker or an SPF and DMARC checker: this tool does all of them at once. No access to your site is needed.

The checks

What does the scanner check on your website?

Five groups of checks, each with its own score. Nothing is guessed: only what the server shows a visitor is graded.

Encryption

  • Valid SSL certificate, its issuer, days left before expiry, with an alert under 30 days
  • TLS 1.2 or 1.3 protocol
  • Redirect from http:// to https://
  • HSTS: duration, includeSubDomains, preload
  • Mixed content: scripts or images still loaded over http://

Security headers

  • Content-Security-Policy, with unsafe-inline and unsafe-eval flagged
  • X-Content-Type-Options
  • X-Frame-Options or frame-ancestors
  • Referrer-Policy, Permissions-Policy
  • Cross-Origin-Opener-Policy

Information leaks

  • Server version in the Server header
  • X-Powered-By, X-AspNet-Version
  • Generator tag, for example WordPress 6.4
  • Visible versions of jQuery, Bootstrap, AngularJS, Lodash
  • A /.well-known/security.txt file

Cookies

  • Secure attribute: the cookie never travels in clear text
  • HttpOnly attribute: an injected script cannot read it
  • SameSite attribute: protection against forged requests
  • Session cookies checked separately, more strictly

Domain email

  • SPF present, single, with a final -all or ~all rule
  • Fewer than 10 DNS lookups in the SPF record
  • DMARC: none, quarantine or reject policy
  • DMARC report address (rua)

What the scanner never does

No intrusion attempt, no port scan, no password tried, no list of hidden paths to guess. One page visit, like anybody else. That is what makes it safe to offer to everyone, for every site tested.

How it works

How do I check my website security online?

A handful of requests, in a few seconds. The site being tested sees the equivalent of one visitor opening one page.

  1. You enter the address. The home page is enough. The tool switches to https:// on its own.
  2. The page is loaded once. Like an ordinary browser: headers, cookies and HTML are read exactly as the server sends them.
  3. The http:// version is requested. Without following the redirect, to see whether the site sends visitors to https://, and with which status code.
  4. The certificate is read. During the TLS handshake: issuer, expiry date, negotiated protocol.
  5. Public DNS is queried. The domain’s SPF and DMARC records, and whether it has a mail server.
  6. Each finding gets a status. Passed, watch or problem. The A+ to F grade comes from the scale described below.
Why passive? A public tool that attacked the sites it was given would serve attackers too. This one only reads public information: useful to the site owner, useless to someone looking for a way in.

The grade

How is the A+ to F grade calculated?

Each check is worth one point when it passes, half a point when it needs watching, zero when it is a problem. Encryption weighs 30% of the grade, headers 25%, domain email 20%, information leaks 15% and cookies 10%. A group with nothing to measure, such as a page that sets no cookies, simply drops out of the calculation.

Security grade scale
GradeScore out of 100What it means
A+95 to 100, no problemsEvery recommended protection is in place.
A85 to 94Very good. A few details are left, often a secondary header.
B70 to 84The basics are there. One or two important protections are missing, often the CSP.
C55 to 69Several common protections are missing. Usually an evening of work.
D40 to 54Weak. Important fixes are needed, starting at the top of the list.
Funder 40No HTTPS, a rejected certificate or almost nothing in place. Fix it this week.

Two caps apply: a site without HTTPS or with a rejected certificate gets an F whatever else it does well; a server that still accepts TLS 1.0 or 1.1 cannot go above C.

The fixes

How do you fix a website’s security problems?

In this order. The first steps protect every visitor, the last ones fine-tune. Most of it fits in an evening and never touches the site’s content.

  1. Fix the certificate. An expired certificate, or one issued for another name, shows your visitors a warning page. Let’s Encrypt is free and renews itself; Cloudflare provides one too.
  2. Force HTTPS. A permanent (301) redirect from all http:// to https://. On Cloudflare, that is the Always Use HTTPS setting.
  3. Add HSTS. A max-age of at least one year. Only add preload once every subdomain is on HTTPS.
  4. Set the simple headers. X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy: four lines, no effect on how the site looks.
  5. Roll out a CSP gently. Start in Report-Only mode for a week, add the domains the site needs, then switch to blocking mode.
  6. Hide versions, then update. server_tokens off, remove X-Powered-By and the generator tag. Above all: keep WordPress, its plugins and jQuery up to date.
  7. Protect cookies. Secure on all of them, HttpOnly on session cookies, SameSite=Lax by default.
  8. Lock down your domain email. A single SPF record, then a DMARC record at p=none that you raise to quarantine, then reject once the reports are clean. Publish a security.txt file.
nginx: the recommended headers
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
add_header X-Content-Type-Options "nosniff" always;
add_header X-Frame-Options "SAMEORIGIN" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
add_header Permissions-Policy "camera=(), microphone=(), geolocation=(), payment=()" always;
add_header Cross-Origin-Opener-Policy "same-origin" always;
add_header Content-Security-Policy-Report-Only "default-src 'self'; img-src 'self' data: https:; object-src 'none'; base-uri 'self'; frame-ancestors 'self'" always;
server_tokens off;
Apache: the same block
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"
Header always set X-Content-Type-Options "nosniff"
Header always set X-Frame-Options "SAMEORIGIN"
Header always set Referrer-Policy "strict-origin-when-cross-origin"
Header always set Permissions-Policy "camera=(), microphone=(), geolocation=(), payment=()"
Header always set Cross-Origin-Opener-Policy "same-origin"
Header always set Content-Security-Policy-Report-Only "default-src 'self'; img-src 'self' data: https:; object-src 'none'; base-uri 'self'; frame-ancestors 'self'"
Header always unset X-Powered-By
ServerTokens Prod
ServerSignature Off

On Cloudflare: Rules, then Transform Rules, then Modify Response Header, one “Set static” rule per header. The CSP starts in Report-Only mode: after a week with no warnings in the browser console, rename it Content-Security-Policy.

Compare

Online scanner, cybersecurity audit or penetration test?

Three tools, three depths. The scanner is the first reflex; it does not replace the other two.

CriterionSecurity scannerCybersecurity auditPenetration test
What it looks atWhat the site shows any visitor: certificate, headers, cookies, versions, email DNSThe whole environment: accounts, computers, servers, network, backups, Microsoft 365One specific target, actually attacked to prove someone can get in
Access neededNoneRead-only access, granted by youWritten authorization, signed scope
Risk to the siteNone: a single page visitVery low: read-only collectionReal, which is why it is scheduled
ResultA+ to F grade, copy-ready fixes, in a few secondsFindings ranked by risk, with a remediation planReport of the flaws exploited, with evidence
Who it is forAny business with a website, before or after a redesignA small business that wants to know where it standsAn already mature organization, or one required by a contract

Domain email

Why check SPF and DMARC for my domain?

Your website’s domain also carries your email. Without SPF and DMARC, anyone can send a message that appears to come from your address: a fake invoice to a client, a changed bank account number sent to your accountant. It is the most profitable fraud for scammers, because it rides on the trust people have in you.

SPF says which servers may send mail in your name. DMARC says what to do with a message that fails: monitor it (p=none), quarantine it or reject it. The scanner reads both records in public DNS. To go further, our DMARC and SPF checker counts SPF DNS lookups, looks for DKIM keys under the common Microsoft 365 and Google Workspace selectors, then gives you the records to copy.

For a complete setup, phishing filtering included, see our page on email protection for small businesses.

Good habits

8 habits that keep a website secure

A good grade slips quickly. These habits keep it from one update to the next.

  • Run the scanner again after every site update. A theme or plugin can drop a header without telling you.
  • Set an alert 30 days before the certificate expires. Automatic renewal fails more often than people think.
  • Keep WordPress and its plugins up to date. Hiding the version patches nothing.
  • Remove plugins you no longer use. A deactivated plugin is still code sitting on the server.
  • Test a CSP before it blocks anything. Report-Only mode keeps you from breaking a form on a Friday night.
  • One SPF record per domain. Two SPF records means an invalid SPF.
  • Read your DMARC reports before moving to reject. They show which services send mail in your name.
  • Write down who has access to hosting and DNS. The day you need to fix something fast, nobody hunts for the password.

Questions and answers

Website security questions

How do I know if my website is secure?
Enter its address in the scanner at the top of this page. In a few seconds it checks the SSL certificate, the HTTPS redirect, security headers, visible software versions, cookies and the domain’s SPF and DMARC records, then gives a grade from A+ to F. It is a free website security scanner, with no sign-up.
How do I check my website’s SSL certificate?
The scanner reads the certificate during the connection: it tells you whether it is valid, who issued it, when it expires and which TLS protocol is used. It raises an alert under 30 days before expiry. In a browser, click the padlock to the left of the address to see the same details page by page.
What are security headers?
They are lines the server adds to every page to tell the browser how to protect itself: force HTTPS (HSTS), limit which scripts may run (Content-Security-Policy), refuse to be shown in a frame (X-Frame-Options), and not guess file types (X-Content-Type-Options). They are added in nginx, Apache or Cloudflare without touching the site’s content.
Can the scanner break or slow down my site?
No. It does what a visitor does: it opens the home page once, requests the http:// version to see the redirect, reads the security.txt file if there is one, and queries public DNS. No attack, no port scan, no password attempts.
How do I check my DMARC record?
This scanner reads your SPF and DMARC records in public DNS and tells you whether DMARC only monitors (p=none), quarantines or rejects fake emails. For a deeper look, our free DMARC and SPF checker counts SPF DNS lookups, tries the common DKIM selectors and gives you records to copy.
Does the scanner find malware?
No. It looks at the site from the outside, like a visitor. Malicious code hidden in the files can only be found with access to the server. If you think your site has been hacked, contact us.
Does an A grade mean my site cannot be hacked?
No. The grade measures the protections visible from outside. It cannot see a weak admin password, a vulnerable plugin that does not display its version, or poorly maintained hosting. It is a good thermometer, not a guarantee. For the rest, you need an audit.
What is the difference between a security scanner and a penetration test?
The scanner looks at what the site shows everyone, without trying anything. A penetration test actually attacks a specific target, with written authorization, to prove someone can get in. In between, a cybersecurity audit reviews the whole environment in read-only mode, with no attack.
My WordPress site got a bad grade. Where do I start?
In this order: the certificate, the HTTPS redirect, HSTS, then the simple headers. Next, update WordPress, the theme and every plugin, and remove the generator tag. Email problems such as SPF or DMARC are fixed in DNS, not in WordPress.

Get your whole site checked

The scanner sees the outside. A specialist looks at the rest: hosting, plugins, access and the site’s backups. Tell us what you want fixed and we send you a quote.

Reviewed by , president of OKTO Solutions · updated