Check if your browser sends Do Not Track (DNT) and Global Privacy Control (GPC) signals correctly.
Do Not Track Tester reports whether the current page visit carries the browser's Do Not Track preference and Global Privacy Control signal. DNT is normally conveyed in the DNT request header, while an affirmative GPC preference is conveyed as Sec-GPC: 1 and may also be exposed to page scripts as navigator.globalPrivacyControl. The result describes this browser context for this visit. It does not show whether the destination will honor either preference. The common surprise is that DNT and GPC are separate signals, so one can be present while the other is absent.
When the page is loaded, the DNT portion evaluates the preference conveyed with that visit. DNT: 1 expresses a preference not to be tracked; DNT: 0 expresses the opposite preference, and an absent DNT value communicates neither. The displayed status therefore concerns the request made by this browser profile, not a browser-wide promise about every future request.
An affirmative GPC signal is represented by Sec-GPC: 1. The GPC specification also defines navigator.globalPrivacyControl so page code can read the user's preference. The tester's GPC result reflects the signal available in this page context. GPC does not define a Sec-GPC: 0 request value, so absence should not be relabeled as an explicit opt-in.
They are independent preference mechanisms with different browser and extension support. A browser or extension can send Sec-GPC: 1 without sending DNT: 1, or vice versa. The mismatch is not a validation error. Check the specific privacy setting or extension responsible for each signal, then reload the tester in the same browser context.
No. DNT and GPC communicate preferences; they are not content blockers, cookie scanners, or proof of a recipient's behavior. This tester cannot establish whether a particular site honored the signal, avoided fingerprinting, or changed server-side processing. It only answers whether the relevant signal is visible during the test visit.
The 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.