Info

No Permissions-Policy

The short version

Send a Permissions-Policy that turns off features you don't use, such as camera=().

What it means

Your home page doesn't send a Permissions-Policy header. That header tells browsers which sensitive browser features your pages and the frames inside them may use: camera, microphone, location, payment, USB and others.

Why it matters

This is information, not a failure. A Permissions-Policy limits the damage if a script or an embedded frame is compromised: a third-party widget can't ask for the camera if your policy turns it off. It also documents what your site actually needs, which helps when you review third-party scripts later.

How to fix it

  1. List the features your site uses. Most sites use none of the sensitive ones.
  2. Send a header that turns the rest off, for example Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=().
  3. To allow a feature only for your own pages, use self, as in geolocation=(self).
  4. Test pages with maps, video calls or checkout after the change; a feature turned off fails quietly.

The header uses the newer structured syntax; the older Feature-Policy header is no longer needed.

Check it worked

Run the HTTP and security headers check again. The Permissions-Policy row should show your value, and the finding should be gone.