MyIPScan
Browser-only check

Client Hints Checker

See which User-Agent Client Hints and fallback browser values are visible in this browser session.

Client hints are browser-controlled. Some high-entropy values may require request headers or browser permission and may not be visible from client-side JavaScript alone.

Client hints

Current Result

Checking
Reading local client hints...Checking
Signals shown
Checking
Storage behavior
No server-side storage
Scope
Local navigator API check
Backend calls
None

Direct answer

Client Hints Checker: answer first

Check User-Agent Client Hints and related browser-visible values locally. Use the result as an observable public-signal check with stated limitations, not as an absolute guarantee.

Last updated

What this checks

The checker reads navigator.userAgentData when available, then shows low-entropy hints such as brands, platform, and mobile status. It also shows user-agent fallback values.

When the browser allows it, the script asks for a small set of high-entropy values and labels the result clearly.

Limitations

  • Browser policy decides which hints are exposed.
  • Server-requested hints may differ from client-side values.
  • Some browsers do not support navigator.userAgentData.
  • This page does not send hint values to a server.

Reduce exposure

What to do next

Client hints are mostly controlled by browser design and site request policy.

  1. Keep your browser updated to benefit from current user-agent reduction behavior.
  2. Review privacy settings that limit high-entropy hints when available.
  3. Compare with the User-Agent Checker to understand fallback values.

Related tools

User-Agent CheckerInspect the legacy user-agent string and related values. Browser Fingerprint TestReview the broader browser signal overview. GPC / DNT CheckerCheck exposed privacy preference signals. WebGL Fingerprint TestCompare browser hints with graphics signals.

Supporting evidence

Use this User-Agent Client Hints as one browser signal, not a full verdict

Run this subtest before and after one browser/privacy setting change when you need focused evidence. For a combined IP, DNS, WebRTC, IPv6, fingerprint, and User-Agent view, use the Public Exposure Report.

BaselineRun the subtest before changing browser, extension, GPU, font, or privacy settings.
RetestChange one setting, restart the browser if needed, and rerun the same subtest.
Safe sharingShare Safe Copy or categories instead of raw hashes, full User-Agent values, or raw browser details.
Browser Fingerprint TestReturn to the broader fingerprint overview. Public Exposure ReportCombine browser and network signals in one Safe Privacy Receipt. Check My Browser PrivacyFollow the browser-focused privacy path.

Check my browser/privacy

What this checks

Visible browser/session signals such as public route, DNS/WebRTC/IPv6 behavior, fingerprint traits, user-agent, or public IP context.

Limits

What this cannot check

It cannot certify anonymity, inspect every app, or prove that a VPN, ISP, device, or account is safe.

Read results

How to use the output

Treat results as review signals for this browser/session or public target. Re-test after one change, then use Safe Copy or notes that avoid raw identifiers.

Related tools

Continue with the closest checks

Public Exposure ReportFull browser-session report with Safe Copy, issues, fixes, and clear limits. VPN Leak TestCompare visible IP, DNS, WebRTC, IPv6, and browser signals. What Is My IPPublic IP, ISP, ASN, approximate location, and browser context. Browser Fingerprint TestBrowser-visible traits and focused fingerprint subtests. MethodologyReview how MyIPScan labels signals, limitations, and Safe Copy output.

SEO and AI citation summary

Client Hints Checker: what this tool does

Shows User-Agent Client Hints and fallback user-agent values available in the browser.

How to use

  1. Run the tool in the same browser and network context you want to review.
  2. Change only one VPN, DNS, browser, WebRTC, IPv6, or privacy setting at a time.
  3. Run the Public Exposure Report afterward if you need a combined receipt.

What the result means

Treat the output as visible browser-session or public network evidence. It helps compare current settings, but it does not certify anonymity, VPN safety, or every app route.

Limitations

  • This tool reports observable signals only; it is not a guarantee or certification.
  • Browser-local navigator APIs only.
  • Results can change after VPN reconnects, DNS propagation, browser updates, cache changes, or provider configuration changes.

Client Hints Checker — Common Questions

What are User-Agent Client Hints?

User-Agent Client Hints (UA-CH) are a newer API replacing the traditional user-agent string. Instead of sending all browser/OS details in every request, Client Hints let servers request only what they need. Basic hints (browser family, mobile/desktop) are sent by default; detailed hints (full version, OS version, device model) require an explicit Accept-CH response header. Chrome and Edge support them; Firefox and Safari do not fully implement them.

How should I use Client Hints Checker results?

Use the result to decide what to review next, make one change at a time, and retest in the same browser, network, domain, or provider context when possible.

What does Client Hints Checker not prove?

It does not prove anonymity, full security, complete deliverability, full reputation cleanliness, search ranking, or AI citation. It only reports the visible signals available to this tool.

Next checks and references

Privacy DiagnosticsParent hub for this tool category.Browser Fingerprint TestBrowser-visible fingerprint surface overview.User-Agent CheckerBrowser user-agent viewer.GPC / DNT CheckerLocal privacy preference signal check.Relevant guideBackground reading for interpreting this result.MethodologyHow MyIPScan labels confidence, limits, and safe-copy outputs.