Free tool

Free website security checker

Enter your website’s address and this tool checks what anyone on the internet can already see: whether HTTPS and the certificate are set up properly, the security headers that protect visitors’ browsers, cookie flags, exposed files like .env or .git, mixed content, and the SPF and DMARC records that stop scammers sending email as you. You get a grade and a plain-English fix for every problem. It never tries to break in, and nothing is stored.

Last updated

Checks only what anyone on the internet can already see, the way a browser and a mail server would. Nothing is attacked, and the address and results aren't stored. A few checks per hour per visitor.

What the check looks at

Encryption

Whether HTTPS works, the certificate is valid, trusted, strong and not about to expire, plain HTTP sends visitors to HTTPS, and HSTS makes browsers remember it.

Browser protection

The security headers that tell browsers to block injected scripts (CSP), refuse to show the site in hidden frames, and stop guessing file types.

Cookies

Whether the cookies the home page sets are marked Secure, HttpOnly and SameSite, so they can't be read by scripts or sent over plain HTTP.

Exposed files

Whether a .git folder or .env file is publicly readable, and whether the site announces exact software versions. Nothing is downloaded or kept.

Page content

Files loaded over plain http:// on a secure page (mixed content), and scripts from other sites that run without an integrity check.

Email spoofing

The SPF and DMARC records that stop scammers sending email as your domain, plus DKIM keys under common names and a CAA record.

What it doesn't do: it never tries to break in (no password guessing, SQL injection or port scans), and it only sees the home page from the outside. A clean result means the basics are right, not that the site can't be hacked. For that, you need a security review by someone you've given permission to test it.

Want the background? How to check your website's security for free walks through each check and the one-line fixes for the most common problems.

Made by AI Web Center

Rather have it fixed for you?

Most of these fixes take an hour or two for whoever runs your site. Send me your report and I'll tell you what matters most, or move the site to a modern, secure setup like this one.

Frequently asked questions

Is this website security checker really free?

Yes. It's free, needs no account or email address, and has no paid version. It checks one site at a time from your browser; a few checks per hour per visitor keep it from being used to scan the internet.

How do I check if my website is secure?

Enter its address above. The check takes 10 to 20 seconds and looks at the things attackers check first: HTTPS and the certificate, security headers, cookie flags, exposed private files, mixed content and email-spoofing records. Each problem comes with a plain-English fix you can pass to whoever runs your site.

Is it safe to run on my site?

Yes. It makes a handful of ordinary requests, the same ones a browser or search engine makes: the home page, the http:// version, /.well-known/security.txt, and two well-known private file addresses (/.git/HEAD and /.env), plus public DNS lookups. It never logs in, submits forms, guesses passwords or scans ports.

What does the grade mean?

The score is the share of points earned across the graded checks: a warning earns half, a problem none, and notes don't count. A is 90 or more, B 80, C 65 and D 50. Broken HTTPS or a publicly readable .git or .env file means an F whatever the rest says, because either can undo everything else.

My site works fine. Why is the grade low?

Most problems here don't break anything you can see. Missing security headers, for example, only matter when someone attacks the site, which is exactly when you want them. Many are one-line changes in the web server or hosting settings; each finding says what to add.

Does a good grade mean my site can't be hacked?

No. A good grade means the basics are in place: the things automated attack tools look for first. It can't see outdated plugins, weak passwords, or bugs in your own code. For that you need a security review or penetration test by someone you've given permission to test the site.

Why do email records count toward website security?

Because scammers who can't break into your site can still send email that looks like it's from your domain, to your customers. SPF says which servers may send your email, and DMARC tells providers like Gmail and Outlook to reject or junk mail that fails. A domain that never sends email should still publish them.

Is the address I check stored?

No. The address and the results are not stored or logged. The result is kept in memory for half an hour, so you can still email it to yourself, and checking the same site again within five minutes shows the same report without contacting it again. Like every page on this site, the server log records your visit.

Can I get the report by email?

Yes. After a check, enter your email address under the grade and the full report, with every fix, is sent to you once. Your address isn't kept. If you'd also like the free AI Coding Starter Kit and occasional updates, tick the box: you'll get a link to confirm first, and you can unsubscribe at any time.

How often can I use it?

A few checks per hour and about thirty a day from one network, so it can't be used to scan the internet for weak sites. If you need to check many sites, for example for clients, get in touch.

Sources

  1. OWASP HTTP Security Response Headers Cheat Sheet. Recommended values for HSTS, X-Frame-Options, nosniff, Referrer-Policy, Permissions-Policy; remove X-Powered-By and version banners
  2. Strict-Transport-Security (MDN). max-age, and the one-year minimum for preloading
  3. RFC 9116: A File Format to Aid in Security Vulnerability Disclosure. security.txt: Contact and Expires are required
  4. RFC 7208: Sender Policy Framework (SPF)
  5. RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC)