Network · Made a little simpler

Framing Policy Checker

Check saved CSP and X-Frame-Options declarations against a supplied document origin and ancestor chain. Compare precedence and download a local report.

Free to useNo account neededProcessed on your device
Your workspaceProcessed on your device

Enter the nearest ancestor first and continue to the top-level ancestor. Use one serialized HTTP(S) origin per line. The check uses the saved headers on this device.

Add this tool to your website

Paste this code into your page to add the tool and a visible ToolMellow credit link.

HTML embed code
Preview embed

Framing Policy Checker: how to use it

  1. Paste saved response headers or a header capture with status lines.
  2. Enter the protected document origin and each declared ancestor origin. The last final block is selected unless you specify another.
  3. Review the recorded declarations and ancestor results. Copy or download the JSON report.

Limits and notes

Reads up to 50,000 characters, 20 CSP policies, and 20 declared HTTP(S) ancestor origins. Common origin-based expressions are supported. Path-specific source expressions and unsupported browser contexts may require review.

How your privacy works →

Framing Policy Checker: common questions

Which header controls when both are recorded?

In the current HTML processing model, enforcing CSP frame-ancestors controls the framing check when present. A report-only field does not replace X-Frame-Options.

Does default-src control which sites can embed this document?

The frame-ancestors directive has no default-src fallback. The report also checks recorded X-Frame-Options declarations.

Why enter every ancestor?

A nested frame can have more than one container document. The declared chain must satisfy each relevant enforcing policy.

Guides