TOOL · 09 / 09
Website Security
Headers · CSP · CookiesFREE
Your data is safe
No storage
Domains are only used for the check and discarded immediately.
Public sources
All checks use publicly accessible data: DNS, SSL certificates, HTTP headers.
No account needed
The tool works completely anonymously and without signup.
GDPR compliant
No personal data, no storage, no sharing.
WEBSITE SECURITY — THE GUIDE
What is HTTP-header website security?
ON THIS PAGE
- What is Website Security?
- Why do you need this?
- Step-by-step in 4 steps
- What gets checked?
- Glossary
- FAQ
What is HTTP-header website security?
Modern browsers evaluate dedicated security headers when loading a page — Content-Security-Policy, HSTS, X-Frame-Options. Missing or weak headers open the door to XSS, clickjacking and mixed content. We check them all in one go.
Why check headers regularly?
A large share of web attacks would be prevented by proper headers:
- XSS. Without CSP, cross-site scripting is trivial.
- Clickjacking. Without X-Frame-Options your page can be embedded.
- MITM. Without HSTS the first HTTP requests are attackable.
- Cookie theft. Without Secure/HttpOnly, scripts read the cookie.
Step-by-step: Website Security in 4 steps
- 1Enter a URLWe send a GET request with a standard browser UA.
- 2Parse headersEvery security header is inspected.
- 3Analyse CSPEach directive examined for weaknesses.
- 4Inspect cookiesFlags, domain, lifetime.
What gets checked?
We follow the OWASP Secure Headers Project:
Strict-Transport-Security
HSTS value + preload.
Content-Security-Policy
All directives.
X-Frame-Options
Clickjacking protection.
X-Content-Type-Options
MIME-sniffing off.
Referrer-Policy
Which referrers are sent.
Permissions-Policy
Browser-API permissions.
Cookie flags
Secure, HttpOnly, SameSite.
Server disclosure
Version leakage.
GLOSSARY
Web-security vocabulary
- CSP
- Content Security Policy — defines which sources the browser may load.
- HSTS
- HTTP Strict Transport Security.
- XSS
- Cross-Site Scripting.
- Clickjacking
- Embedded page used for invisible clicks.
- CORS
- Cross-Origin Resource Sharing.
- Mixed content
- HTTPS page with HTTP resources.
- SameSite
- Cookie attribute against CSRF.
- Subresource Integrity
- Hash validation for external JS.
WHO USES IT
Who checks website security?
Frontend devs
Before production deploy.
Security teams
Quarterly audit.
Compliance
ISO 27001, BSI baseline protection.
Penetration testers
Quick pre-check.
Agencies
Before client launch.
FAQ
FAQ for Website Security
What’s the most important directive?
CSP. Without CSP everything else is cosmetic.
Do I need HSTS preload?
For every production domain — yes.
How is it scored?
OWASP score 0–100. < 50 = insufficient, > 80 = good.
Does it work with SPAs?
Yes, we test the initial GET. Client routing is irrelevant since it’s headerless.
Does it cost?
Web: €0. Monitoring: Mandokit plan.
Do you store URLs?
Only the request ID, no content.
MORE FREE TOOLS
Pairs well with Website Security
Monitor security headers across every domain.
Mandokit finds, validates and contacts B2B leads for you — as a guided workflow or via API.
Try for free