User-Agent Parser
Breaks a user-agent string into browser, engine, OS and device, and shows your own for comparison.
Breaks a User-Agent string into the browser, engine, OS and device it claims to be, and shows the RFC 9110 product/comment structure underneath. It reads the string rather than consulting a device database, so nothing is presented as more certain than it is.
User-Agent string
How to use it
Leave it empty for your own
With no input the page parses your own User-Agent, which is the quickest way to check what a site is seeing from you.
Or paste one from a log
An access log line, a support ticket, an analytics export. Crawlers are identified too, and shown in red so a bot in your traffic is obvious.
Read the notes
Where the string is known to understate — a frozen OS version, a masked Android model — the parse says so rather than reporting the frozen value as fact.
Common questions
Why does my Windows 11 say NT 10.0?
Because that is what the browser sends. Microsoft never bumped the UA platform version for Windows 11, so 10 and 11 are indistinguishable from the User-Agent alone. Only the Client Hints API can tell them apart, and only with permission.
Why is the Android model just "K"?
Chrome froze it deliberately, for the same reason macOS is pinned at 10.15.7: the model token was a strong fingerprinting signal. If you need the real device, Client Hints is the supported route.
Why does every browser say "Mozilla/5.0"?
Thirty years of servers sniffing for capabilities by name. Each new browser claimed to be the previous popular one to get the good version of a page, and nobody could ever stop. The structural view below the summary shows the layers of that history.
Should I use the User-Agent for feature detection?
No. It is a claim, freely spoofable, deliberately frozen in places, and wrong for every browser that has not shipped yet. Test for the feature instead; use the UA only for statistics and for bug reports.
Feed it from
My Connection Info
Shows your public IP, its network and everything this tab reveals — browser, screen, language, time zone, connection — and names what a website genuinely cannot see, starting with your MAC address.
JSON Formatter & Validator
Pretty-prints, minifies and validates JSON, pointing at the exact line and column of a syntax error.
YAML Formatter & Validator
Re-indents YAML consistently, validates it, and flags the tab and anchor mistakes that break parsers.
TOML Formatter & Validator
Formats and validates TOML, normalising table ordering and inline-table style.
Next
These accept what this tool produces, so the result can go straight in.
HTTP Request Builder
Composes and sends a GET/POST/PUT/PATCH/DELETE/HEAD request with custom headers and a body, and shows the status, headers, body and timing — without ever forwarding cookies or Authorization.
HTTP Header Inspector
Fetches a URL and shows the full response headers, redirect chain, timings and compression used.
IP Address Info
Shows your public IP or any address with its reverse name, ASN, announcing network, prefix and registry country from Team Cymru’s DNS data — no city-level geolocation.
JSON ⇄ CSV
Flattens nested JSON into columns or rebuilds objects from a table, with a dot-path column naming rule.
JSON Diff
Compares two JSON documents structurally, ignoring key order and reporting added, removed and changed paths.
JSON Formatter & Validator
Pretty-prints, minifies and validates JSON, pointing at the exact line and column of a syntax error.