Parse your browser’s User-Agent into readable parts and see whether it’s consistent with your other browser signals. Honest, runs in your browser, nothing stored.
Your browser sends a User-Agent string with every request, describing your browser, version, and operating system. This tool parses yours into readable parts and checks whether it’s consistent with your browser’s other signals. Everything runs in your browser; nothing is stored.
The User-Agent is a line of text your browser sends to every website, identifying what you’re browsing with — for example Mozilla/5.0 (Windows NT 10.0; Win64; x64) … Chrome/120.0. Servers read it to tailor responses (mobile vs desktop layouts, feature support). It reveals your browser family and version, operating system family, and rough device type — but not your name, exact device model, or precise OS build.
Parsing a User-Agent is best-effort pattern matching, not an exact science — the format is messy by history, and new or uncommon browsers are sometimes misread. We show the parsed result alongside the raw string so you can always see the source. Browsers are also deliberately reducing the detail in User-Agents over time for privacy, so modern strings are less specific than older ones, and increasingly point to client hints instead.
A website can’t truly know whether your User-Agent is “spoofed.” What it can do is compare your UA against other signals your browser reports — its client hints and the platform JavaScript sees. When they all agree, your UA is consistent. When they don’t — say your UA claims macOS but your browser reports Windows — that mismatch is exactly what anti-fraud systems notice. It’s common and harmless if you’re deliberately overriding your UA (via an extension or dev tools); worth knowing if you didn’t expect it.
Scraper and automation engineers verify their custom client sends a believable, consistent User-Agent — a default library UA or a UA that contradicts its other signals is a fast way to get blocked. Privacy-conscious users check whether a UA-spoofing extension is doing what they expect without creating tell-tale inconsistencies. In both cases, the honest signal is consistency, not a scary “exposed” verdict.
Related: Request header viewer · What is canvas fingerprinting? · Why proxies leak your true ASN