My User Agent

Parse and diagnose HTTP headers and routing signals in your browser. No input is sent to a server. Use it for first-pass observation-gap troubleshooting.

Result

User-Agent

Languages

Platform

Timezone

Locale

Screen

Viewport

Device Pixel Ratio

Device Memory

CPU Cores

Touch

Runs in your browser. No input is sent to a server. Use this as a first-pass diagnostic step.

How to use

Check User-Agent, language, and platform values to isolate environment differences. Share only required fields in support cases.

Notes (this tool)

  • Some values may be unavailable due to browser privacy settings.
  • UA strings can be spoofed. Use multiple signals when strict detection is required.

About this page

What does this tool do?

Shows User-Agent, language settings, screen size, timezone, and other environment info.

Useful for support and bug reproduction checks.

User-Agent basics

  • User-Agent is a string describing browser/OS.
  • Some browsers reduce or freeze UA details.
  • Do not rely solely on UA; use feature detection too.

What is UA-CH (Client Hints)?

UA-CH (User-Agent Client Hints) provides browser info without relying on the legacy UA string. As some browsers freeze UA strings, UA-CH becomes more important.

This page shows what is available (e.g., platform) and will be empty when unsupported.

Typical use cases

  • Quickly capture environment info for support
  • Clarify reproduction conditions for UI bugs
  • Compare against access logs for mismatches

Fields displayed

  • User-Agent / UA-CH (when supported)
  • Accept-Language / Languages
  • Platform / Device memory / Cores
  • Screen / Viewport / DPR
  • Timezone / Locale

Tips for sharing in support tickets

For debugging, details beyond UA (language, timezone, screen size, DPR) can be critical.

  • Layout issues: share Viewport / DPR / Screen
  • Time issues: share Timezone / Locale
  • Localization issues: share Languages / Accept-Language

Privacy considerations

Combining environment signals can contribute to fingerprinting. Share only the minimum needed.

  • This tool displays locally and does not send data.
  • Review the content before pasting into external forms

Common pitfalls

  • User-Agent information may be reduced or frozen
  • Device info can be hidden by privacy settings
  • Misclassifying based on UA string appearance
  • What is my IP: check network-side visibility
  • HTTP Header Parser: inspect request/response headers

What this tool does

  • List browser environment info
  • Check UA/language/screen size
  • Organize shareable info for support

Debugging workflow (recommended)

  • Paste actual headers or observed values
  • Compare expected and observed values
  • Trace proxy, CDN, and redirect paths

Operational notes

  • Intermediaries may rewrite headers. Compare captures from equivalent points.
  • Confirm final decisions with server logs and configuration such as trusted proxy and routing.

Referenced specs

  • UA-CH (User-Agent Client Hints)
  • MDN: Navigator / Screen / Intl

FAQ

What is UA-CH?

User-Agent Client Hints allow staged UA info; shown only in supported browsers.

Is UA-only detection OK?

Not recommended. Use feature detection or real measurements.

Why are some fields (none)?

It can be unavailable due to browser support or privacy settings.

References

  1. MDN: Navigator
  2. MDN: Screen
  3. MDN: Intl
  4. MDN: Sec-CH-UA (UA-CH)

These links are generated from site_map rules in recommended diagnostic order.

  1. What is my IP — Show your current client IP and related info