Test whether the first HTML response changes under GPC
We fetch the URL twice: once normally, once with Sec-GPC: 1. If known tracker hosts disappear from that first HTML, we say the header had an effect. JavaScript-fired pixels after load are not compared.
What the probe actually does
This is a real HTTP header probe, not a policy-text search. The public scan attaches the result to your findings report.
A site can still ignore GPC in the browser after hydration. Treat “likely respected” as a first-byte signal only.
FAQ
Is this the same as Chrome’s GPC setting?
We send the Sec-GPC request header from our scanner. We do not control the visitor’s browser. Use both if you need end-user proof.
Related
PrivBeacon provides automated privacy scans and document templates for informational purposes only. This is not legal advice. Consult qualified legal counsel before relying on generated policies or compliance scores for regulatory decisions.