X-Frame-Options / frame-ancestors check
Confirms clickjacking protection is enabled via X-Frame-Options or the modern CSP frame-ancestors directive.
Quick answer#
Lemwatch passes the check if the response sets X-Frame-Options: DENY|SAMEORIGIN OR a CSP with frame-ancestors.
What it checks#
Where to find it in Lemwatch#
Site details → Security → Headers.
How to fix#
X-Frame-Options: SAMEORIGIN at your web server.frame-ancestors 'self' to your CSP and drop X-Frame-Options.FAQ#
Which is better, XFO or frame-ancestors?#
frame-ancestors — it supports multiple origins and modern browsers ignore XFO when both are set.
Does this protect against all clickjacking?#
It covers iframe overlay attacks. UI-redress via popups needs additional mitigations.
Related#
Related Articles
Security Headers Explained
What security headers are, why they matter, and how to fix them.
Content-Security-Policy header check
Parses your CSP and flags unsafe-inline, unsafe-eval, wildcard sources, and missing directives — the hardest security header to get right.
Cookie security check
Inspects Set-Cookie headers for Secure, HttpOnly, and SameSite flags — the three attributes that stop session hijacking in modern browsers.
How does Lemwatch validate canonical URLs?
Lemwatch checks every crawled page for a rel=canonical tag, verifies it resolves to a 200, and flags self-referencing errors or canonical loops.