Check if your browser sends Do Not Track (DNT) and Global Privacy Control (GPC) signals and whether sites respect them.
The page inspects the two privacy signals your browser exposes to every site it visits and reports their exact state: the legacy Do Not Track header and the newer Global Privacy Control signal. It shows whether either one is sent, what the value means, and why the two are not equal in practice. The surprise most people hit: DNT can be switched on and still be ignored, because honoring it is voluntary, while GPC, which far fewer browsers send, is the signal that California's CCPA regulations recognize as an opt-out and that a growing list of sites actually act on.
A concrete input and expected output from the current implementation.
Input
Safari on macOS with default privacy settings ('Ask websites not to track me' is on). Expected output
Do Not Track: sent (header value DNT: 1). Global Privacy Control: not supported - this browser has no GPC implementation, so it sends no Sec-GPC header and sites will not see one from it.
Safari ships with 'Ask websites not to track me' enabled, which makes it send DNT: 1 on every request. Apple has not implemented GPC, so the page finds no globalPrivacyControl property and reports the signal as unsupported rather than merely disabled.
The checker runs entirely in your browser and reads the same properties any site can read. navigator.doNotTrack returns '1' (opt out), '0' (opt in), or 'unspecified' (header not sent). navigator.globalPrivacyControl returns a boolean, present only in browsers that support GPC; true means the browser attaches a Sec-GPC: 1 header to every request. Nothing is uploaded or stored.
An 'unspecified' DNT result is not a failure: the header is simply absent, which is the default in most browsers today. GPC 'not supported' differs from 'disabled': the first means the browser has no GPC implementation at all (Chrome and Safari), the second that the property exists but is off. The page labels each outcome so the two are not confused, and flags that DNT is rarely honored while GPC carries legal weight under California's CCPA regulations.
Because the 'Do Not Track' mechanism was never adopted as a standard. The W3C published its Tracking Preference Expression proposal, but the advertising industry chose not to honor the header, and most browsers now leave it off by default. Sites that respect it do so voluntarily. For a signal with actual legal recognition, GPC is the meaningful one to have.
In browsers that support it: Brave and the DuckDuckGo browser send GPC by default, and Firefox enables it for users in the United States with a preference others can switch on. Chrome and Safari have no GPC implementation, so there is no option to enable it there - if you need the signal in those browsers, a privacy extension or a different browser is the route.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.