Why it matters
It limits what powerful browser features your page, and anything embedded in it, can request. Switching off unused features reduces risk.
Example
Permissions-Policy: camera=(), microphone=(), geolocation=()Where you will see it
The free Security headers checker looks at this on a live page and explains what it finds in plain English: grade HSTS, CSP and the other protective headers, with copy-paste fixes for Nginx, Apache, Cloudflare and Netlify.
Related terms
- Content-Security-Policy: An HTTP response header that lists which sources a page may load scripts, styles, images and other resources from.
- Referrer-Policy: An HTTP response header that controls how much of the current page's address is sent to another site when a visitor follows a link or loads a resource from it.
- HTTP header: A name and value pair sent along with a request or a response.
Go deeper
- Security headers explained: What HSTS, Content-Security-Policy, X-Content-Type-Options, frame-ancestors, Referrer-Policy and Permissions-Policy do, with safe example values.