Free website check
Check your website's security in seconds.
Type your domain. We read the same public settings anyone on the internet can see, then explain each one in plain English.
Results
Waiting for a domain
Encrypted connection (HTTPS)Ready
Why it matters: visitors' data travels encrypted, and anyone who types http:// gets sent to the secure version.
How to fix: install a TLS certificate and forward every http:// request straight to https://.
Forces HTTPS on every visit (HSTS)Ready
Why it matters: browsers remember to use the secure version, even if someone on the network tries to downgrade the connection.
How to fix: send Strict-Transport-Security with a max-age of at least 6 months (15768000 seconds) on every HTTPS address your visitors pass through.
Blocks injected scripts (CSP)Ready
Why it matters: a Content Security Policy tells browsers which scripts may run, so code an attacker slips into the page gets blocked.
How to fix: send a Content-Security-Policy header (a <meta> tag counts too), and keep 'unsafe-inline' out of your script rules.
Can't be framed by another siteReady
Why it matters: it stops another site from loading your page invisibly and tricking your visitors into clicks.
How to fix: add frame-ancestors 'none' (or 'self') to your CSP header, or send X-Frame-Options: DENY.
Stops file-type tricks (nosniff)Ready
Why it matters: browsers treat each file as the type your server says, so a disguised upload can't run as a script.
How to fix: send X-Content-Type-Options: nosniff.
Limits what it shares on linksReady
Why it matters: it controls how much of your page address other sites see when a visitor clicks away.
How to fix: send Referrer-Policy: strict-origin-when-cross-origin or stricter.
Locks camera, mic, and locationReady
Why it matters: it turns off browser features your site doesn't use, so injected code can't switch them on.
How to fix: send a Permissions-Policy header that disables the features you don't use.
Hides server software versionsReady
Why it matters: a version number tells attackers exactly which known bugs to try first.
How to fix: remove version numbers from the Server and X-Powered-By headers.
Says who may send its email (SPF)Ready
Why it matters: an SPF record lists the servers allowed to send email for your domain, so inboxes can spot forgeries.
How to fix: publish 1 SPF record that ends in -all or ~all and stays within 10 DNS lookups.
Rejects forged email (DMARC)Ready
Why it matters: DMARC tells inboxes to quarantine or reject email that fakes your domain.
How to fix: publish a DMARC record at _dmarc with p=quarantine or p=reject.
Worth knowing
The path we followed
A quick outside look at 10 public settings, not a full security audit.
Get help fixing theseHow the grade works
Each check passes, fails, or could improve. Where Mozilla's HTTP Observatory scores the same setting, a Fail here matches one of its big penalties and Improve matches a small one.
- Points
- Pass counts 1, Improve counts half, and Fail counts 0. A check that couldn't run doesn't count either way.
- Score
- Your points as a share of the checks that ran, out of 100.
- Grade
- A+ means all 10 checks ran and passed. A is 90 or more, B is 75, C is 60, and D is 40. Below 40 is an F. A grade needs at least 6 checks that ran.
What this check doesn't cover
It reads what anyone on the internet can see from outside. These need a closer look.
- TLS versions and cipher suites. Which encryption settings your server offers.
- DNSSEC. Whether your DNS answers are signed.
- DKIM. Email signing keys, which live under selector names the check can't guess.
- Cookies. Whether your site's cookies are marked Secure, HttpOnly, and SameSite.
- The software behind your site. Plugins, updates, passwords, and backups.
Questions about the website check
What does the Syntro website check look at?
It reads the security headers on your home page, checks that plain HTTP forwards to HTTPS, and looks up your SPF and DMARC email records. That makes 10 checks in all.
Is the check safe to run on my site?
Yes. It requests your home page over HTTPS and over plain HTTP, the same way a visitor's browser would, follows up to 5 redirects, makes a few DNS lookups, and asks the public HSTS preload list about your domain. It refuses private and internal addresses.
Does a good grade mean my site is secure?
It means these 10 public settings are right. The check can't see the software behind your site, your passwords, or your backups.
Do you keep my results?
Each result is kept for 10 minutes so a repeat check loads instantly, then it expires. The tool also counts checks per visitor for 10 minutes to stop abuse.
Want help with your results?
Tell us what the check found. Our Web Hosting & Security service includes SSL/TLS, DNSSEC, and a monthly security report. We'll get back to you within 24 hours.