Nos bénévoles n'ont pas encore traduit cet article en Français. Inscrivez-vous et aidez-nous à réaliser cette tâche !
Vous pouvez également lire cet article en English (US).

The HTTP Public-Key-Pins-Report-Only response header sends reports of pinning violation to the report-uri specified in the header but, unlike Public-Key-Pins still allows browsers to connect to the server if the pinning is violated.

For more information, see the Public-Key-Pins header reference page and the HTTP Public Key Pinning article.

Header type Response header
Forbidden header name no


Public-Key-Pins-Report-Only: pin-sha256="<pin-value>"; 


The quoted string is the Base64 encoded Subject Public Key Information (SPKI) fingerprint. It is possible to specify multiple pins for different public keys. Some browsers might allow other hashing algorithms than SHA-256 in the future.
This directive is meaningless for the Public-Key-Pins-Report-Only header, it will be ignored by user agents and the header will not be cached.
includeSubDomains Optional
If this optional parameter is specified, this rule applies to all of the site's subdomains as well.
Pin validation failures are reported to the given URL. This directive should be used with this header, otherwise this header will be a no-op.



In this example, pin-sha256="cUPcTAZWKaASuYWhhneDttWpY3oBAkE3h2+soZS7sWs=" pins the server's public key used in production. The second pin declaration pin-sha256="M8HztCzM3elUxkcjR2S5P4hhyBNf6lHkmjAHKhpGPWE=" also pins the backup key. This key pinning is also valid for all subdomains, which is told by the includeSubDomains declaration. Finally, report-uri="" explains where to report pin validation failures.


Specification Title
RFC 7469, section 2.1: Public-Key-Pins-Report-Only Public Key Pinning Extension for HTTP

Browser compatibility

FeatureChromeEdgeFirefoxInternet ExplorerOperaSafari
Basic support46 No1 No2 ?33 ?
FeatureAndroid webviewChrome for AndroidEdge mobileFirefox for AndroidOpera AndroidiOS SafariSamsung Internet
Basic support Yes Yes ? No33 ? Yes

1. Under consideration for future release.

2. See bug 1091177.

See also

Étiquettes et contributeurs liés au document

Étiquettes : 
Contributeurs à cette page : fscholz, raulsiles, arlenyan, teoli
Dernière mise à jour par : fscholz,