Free Website Security Checker
Check what any visitor, crawler or attacker can already see about your website. Enter your address and ContentMas checks encryption, security headers, cookies, exposed files and email protection, then ranks what to fix first.
What the website security checker looks at
- Encryption, certificates and how the connection is negotiated
- Security headers and cookie settings on every page
- DNS and email protection for your domain
- Exposed files, paths and secrets in the frontend
- Forms, software versions and known vulnerabilities
These checks are the Security part of a full ContentMas audit, which runs 700+ checks in six pillars. Why this pillar matters.
What you get
- A security score for your site and for each page scanned
- Critical issues first: exposed secrets, open files, missing HTTPS or an expiring certificate
- A plain fix for each issue, written so you can hand it to a developer
How the check works
Enter your address
Type your website address. ContentMas counts your pages before anything is scanned.
Choose what to scan
Pick the pages or sections that matter most. The scan opens each one in a real browser.
Read your report
See your scores straight away. Sign in with Google (free) for every issue, ranked from critical to low, with its fix.
Questions
- Is the security checker really free?
- Yes. The Free plan needs no card and scans up to 10 pages per scan, 3 scans every 24 hours.
- Is it safe to scan my website?
- Yes. ContentMas only reads public pages, identifies itself as ContentMasBot and respects robots.txt. It never logs in, submits forms or tries to break in.
- My site has HTTPS. Is that enough?
- HTTPS is the first step, not the last. Headers, cookies, exposed files, outdated libraries and email protection are checked too, and each one can lower trust on its own.
- Does ContentMas test my site like an attacker would?
- No, ContentMas reads what any visitor or crawler can see and never tries to break in. It reports what is exposed and how to close it.
- What makes a site "at risk"?
- Only an open critical security issue: an exposed secret, files open to anyone, no HTTPS, hacked content, a vulnerable library or a certificate about to expire. A low score alone never does.
