Network · Made a little simpler

Permissions-Policy Checker

Inspect a saved Permissions-Policy dictionary. See empty, same-origin, wildcard and listed allowlists, and review conflicts across repeated field lines.

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

Paste a raw value, named field lines, or a saved response with its HTTP status line. For captures, the report uses the last non-informational block when one exists.

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

Permissions-Policy Checker: how to use it

  1. Paste a Permissions-Policy value, field lines or saved response headers.
  2. Check Permissions-Policy and read the latest declaration for each supplied feature.
  3. Check reporting parameters and compare the declared policy with the iframe and browser separately.

Limits and notes

Up to 50,000 input characters and 300 dictionary members. Checks modern Permissions-Policy response header syntax and declared values. The report does not execute APIs or infer feature defaults, actual browser support, iframe inheritance or user permissions.

How your privacy works →

Permissions-Policy Checker: common questions

What does camera=() mean?

It declares an empty allowlist for camera. For a browser that implements camera policy, no origin is included by that declaration.

What happens to repeated declarations?

A Permissions-Policy field is a Structured Fields dictionary. When a key repeats, the final member defines that entry.

Does fullscreen=* guarantee fullscreen access?

The wildcard includes any origin in that declared allowlist. Browser support, ancestor frame policies and API requirements still affect actual access.

Guides