MockFoxAdvertise

User agent parser

Updated Free mock REST & WebSocket APIs

Your browser's user agent is parsed below. Paste any other User-Agent string — from server logs, analytics or a bug report — to see the browser, rendering engine, operating system and device it describes.

Reading your browser…

Browser
—
Engine
—
Operating system
—
Device type
—
Device
—
Your browser's User-Agent Client Hints

Checking…

🔒 Parsed in your browser — the user agent isn't sent anywhere or stored.

How to parse a user agent string

  1. The tool loads your own user agent automatically; paste another one to replace it, or pick a sample.
  2. Read the summary line, then the browser, engine, OS and device details. Bots and HTTP libraries are flagged.
  3. Check the notes: they tell you when a value is frozen (macOS 10.15.7, Windows NT 10.0, Android "K") and can't be trusted.

Reading a user agent string

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36 Edg/141.0.0.0
  • Mozilla/5.0 — a historical token every browser sends for compatibility. It means nothing today.
  • (Windows NT 10.0; Win64; x64) — platform: OS, version and CPU architecture.
  • AppleWebKit/537.36 (KHTML, like Gecko) — engine tokens. Blink still claims WebKit 537.36 for compatibility.
  • Chrome/141.0.0.0 Safari/537.36 — Chromium-based browsers include both; real Safari has Version/x Safari/y instead.
  • Edg/141.0.0.0 — the actual browser. Edge, Opera (OPR/) and Samsung Internet add their own token at the end, which is why parsers check them before Chrome.

User-Agent Client Hints

Chromium browsers now send only low-entropy hints by default: Sec-CH-UA (brands), Sec-CH-UA-Mobile and Sec-CH-UA-Platform. A server can request more — model, platform version, full version list, architecture — by replying with Accept-CH, and pages can read them with navigator.userAgentData.getHighEntropyValues(). Safari and Firefox don't implement Client Hints, so keep a user-agent fallback.

Gotchas when detecting devices

  • Since iPadOS 13, iPads send a desktop Mac user agent. Check navigator.maxTouchPoints > 1 to tell them apart.
  • All iOS browsers use WebKit, so Chrome on iOS (CriOS) behaves like Safari for rendering bugs.
  • Android phones include Mobile in the UA; Android tablets usually don't.
  • For features, use feature detection ('share' in navigator, CSS.supports()) instead of the UA.

Related tools

Frequently asked questions

What is my user agent?

It's shown at the top of the tool: the exact User-Agent string your browser sends with every request, parsed into browser, version, operating system and device type.

Why does my user agent say Windows NT 10.0 on Windows 11?

Browsers froze the Windows version in the UA string. Only User-Agent Client Hints (Sec-CH-UA-Platform-Version 13.0 or higher) reveal Windows 11.

Why does Chrome's version end in .0.0.0?

Chrome's User-Agent Reduction (2022–2023) replaced the minor, build and patch numbers with zeros, and on Android the device model with "K". Full details are available through Client Hints.

Can a user agent be faked?

Yes, trivially — any client can send any User-Agent. Never rely on it for security; use it for analytics and progressive fallbacks only, and prefer feature detection in the browser.

Your business here? Sponsor this tool from $16/week. See placements