My Browser, IP & User-Agent Info Online Free
See exactly what your browser tells websites about you: the full User-Agent string, parsed browser name and version, rendering engine (Blink, Gecko, WebKit), operating system, architecture and device class (desktop, mobile, tablet or crawler). You can also paste any User-Agent string from logs or analytics to reverse-parse it offline — handy for debugging feature flags, bot detection and device targeting. Nothing is transmitted; parsing is pure client-side pattern matching.
My Browser, IP & User-Agent Info In-Browser Workspace
Input data or select files to begin. 100% private, client-side execution with zero server transmission.
How to Use My Browser, IP & User-Agent Info
- Step 1: Open the tool — your live navigator.userAgent loads and parses automatically.
- Step 2: Review the table: browser, engine, OS, architecture, device type and bot likelihood.
- Step 3: Optionally paste a different User-Agent string into the custom field and hit Analyze.
- Step 4: Compare the custom parse against your own to debug UA-switching issues.
- Step 5: Copy the raw User-Agent with one button for bug reports or QA test cases.
About My Browser, IP & User-Agent Info
The User-Agent string is a compact history of browser sniffing: tokens like Mozilla/5.0 (compatible) remain for legacy reasons, while real detection hinges on product versions — Chrome/, Firefox/, Edg/, Safari/Version/, OPR/. Detection order matters because almost every Chromium browser also contains “Safari” and “Mozilla/5.0”; Edge and Opera must be checked before Chrome or they would be mislabeled. Engine families map as: Chromium derivatives → Blink; Firefox → Gecko (Gecko/ token plus “like Gecko” pitfalls); Safari → WebKit. OS detection reads Windows NT (map 10.0 → Windows 10/11, 6.1 → 7), iPhone/iPad OS x_y underscores, Mac OS X, Android version, CrOS and generic Linux, with architecture hints from WOW64/x64/aarch64 tokens. Device class heuristics flag mobile via “Mobile” or iPhone, tablet via iPad/Android-without-Mobile, and bots via bot/crawler/spider/headless patterns — useful when debugging why a crawler sees a different UI. Client hints (Sec-CH-UA headers) are gradually replacing UA parsing on the open web; high-entropy values still expose brands and full version lists to permissioned requests, so treat UA as one signal among several. The parser here intentionally favors readable, explainable regex branches over enormous device databases — it will label flagship phones and desktops correctly without shipping a multi-megabyte WURFL file. Because everything runs in-page, you can debug offline or inside locked-down corporate networks, and pasted strings never leave the tab.
Frequently Asked Questions
Is my User-Agent sent to your servers?
No — parsing happens entirely in the browser; neither live nor pasted strings are transmitted.
Why do all browsers claim to be Mozilla?
Historical compatibility: early servers only served content to Mozilla-tagged clients, so others copied the token.
How accurate is UA parsing?
It is heuristic — spoofed or brand-new strings can be mislabeled; Client Hints are the modern precise source.
Can I analyze a UA from my server logs?
Yes — paste it into the custom field; no network request is made to fetch or validate it.
Does this detect my IP address or location?
No — the tool only reads browser-exposed strings and APIs, never network addresses.