Skip to content

Free clickjacking protection checker

See whether other websites can load your pages in a frame, from the frame-ancestors and X-Frame-Options headers.

Reads the home page as a browser would. No login access needed. What happens to the domain you enter

Example report

example.com
  • 1 Low
  • 1 passed
  • Pages can be framed by other siteswww.example.comLow

    https://www.example.com/ sets neither CSP frame-ancestors nor X-Frame-Options.

    Next step

    Add Content-Security-Policy: frame-ancestors 'self' (or X-Frame-Options: SAMEORIGIN for older browsers).

    View fix guide

What the clickjacking check looks at

  • frame-ancestors

    Read the directive in the enforced Content-Security-Policy.

  • X-Frame-Options

    Accept DENY or SAMEORIGIN; other values do not count.

  • Either control

    Pass a page that sets either one.

  • Each name

    Check the domain and its www name separately.

Only the home page is read; pages where a signed-in visitor acts with one click matter most.

Understand the issue and your next step

Each finding explains what we found, why it matters and what you can change. Start with the issues that need attention, then open the evidence when you want the detail.

  1. Enter your domain
  2. Review the findings
  3. Follow the fix guides
Example finding

Pages can be framed by other sitesLow

Neither X-Frame-Options nor a CSP frame-ancestors directive is set.

Content-Security-Policy: not present
X-Frame-Options: not present

Common framing issues you can put right

  • Pages can be framed by other sitesLow

    Without a framing control any site can load your page in a hidden frame. Set frame-ancestors to 'self', or list the sites that embed you.

    Read the fix guide

Keep watch after you've fixed it

Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.

Free during the preview. Domain verification required.

  1. NewIssue detected
  2. FixedConfirmed by recheck
  3. ReopenedDetected again

How the check works

  • The final HTTPS response for the home page of the domain and its www. name, or the subdomain entered.
  • A frame-ancestors directive in the enforced Content-Security-Policy header. One in a report-only policy does not count.
  • X-Frame-Options set to DENY or SAMEORIGIN. Other values, including the obsolete ALLOW-FROM, do not count.
  • Either control on its own is a pass. Both values are shown, or Not set where a header is absent.

Reading a result

Clickjacking loads a real page from your site in a transparent frame on another site, placed over something the visitor wants to click. The click lands on your page instead, on a button the visitor never saw.

frame-ancestors names who may frame a page: 'none' for nobody, 'self' for your own site, or a list of origins that embed it legitimately. X-Frame-Options is the older header, with two useful values, DENY and SAMEORIGIN. Browsers that understand frame-ancestors ignore X-Frame-Options when both are set, so the CSP directive is the one to get right.

A finding means neither control is set, so any site can frame the page. It is low severity, and matters most on pages where a signed-in visitor can take an action with one click.

What it does not do

  • It reads the home page only. Pages behind a login, where clickjacking matters most, can send different headers; check them in your browser's developer tools.
  • It checks that frame-ancestors is present, not what it allows. A directive that permits every origin still passes.
  • It does not try to frame the page or test whether a particular action could be hijacked.

What happens to the domain you enter

The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.

Guides

A few things worth knowing

Should I use X-Frame-Options or frame-ancestors?
frame-ancestors, in your Content-Security-Policy header. It is the current standard and can list several allowed origins. Sending X-Frame-Options: DENY or SAMEORIGIN as well does no harm and covers very old browsers.
Can frame-ancestors be set in a meta tag?
No. Browsers ignore frame-ancestors in a meta tag. It only works when sent as an HTTP response header.
A partner embeds our pages. What should we set?
List the partner's origin in frame-ancestors, for example frame-ancestors 'self' https://partner.example. Current browsers give X-Frame-Options no way to allow one specific other site.