Skip to main content

User Agent Parser

Paste a user-agent string to identify the browser, engine, operating system and device, and to spot search, AI and SEO crawlers.

What sent this

Browser
—
Engine
—
Operating system
—
Device
—

Notes

  • Paste a string to analyse it.

Related tools

All Network tools →
New
What Is My IP See the public IP address your connection is using right now, along with your provider, con…
New
IP Address Lookup Look up any public IP address: country, region, city, coordinates, time zone, currency, and…
New
HTTP Headers Checker See every response header a URL sends, follow the redirect chain hop by hop, and check the…
New
IPv4 Calculator Convert an IPv4 address between dotted, decimal, binary and hex, convert CIDR to a subnet m…
New
URL Parser Break a URL into its parts, list its query parameters, strip tracking codes to get the cano…
New
DNS Lookup Look up live DNS records for any domain — A, AAAA, MX, NS, TXT, SPF, CNAME and SOA. Queried…

This tool runs entirely in your browser. Nothing you enter is sent to our servers, so there is nothing for us to store or see.

This tool reads public records — DNS, WHOIS and certificate data that registries and servers publish openly. It sends nothing to the host you enter and changes nothing there. Use it on infrastructure you own or are authorised to look into.

About the User Agent Parser

Paste a user-agent string from a log file, an analytics report or your own browser, and find out what actually sent it: browser and version, rendering engine, operating system, device class, and whether it is a crawler.

Every browser lies in its user agent, for compatibility reasons that are now thirty years old. Chrome claims to be Safari, which claims to be Gecko, which claims to be Mozilla. Edge claims to be Chrome. Opera claims to be both. So a string containing "Chrome" is only Chrome if it contains none of Edg, OPR, Vivaldi, Brave, YaBrowser or SamsungBrowser — which is why the checks here run most-specific-first, and why a parser that simply searches for a name reports Edge users as Chrome users.

Crawlers are identified by their claim, and labelled as such. A user agent proves nothing — anything can say it is Googlebot, and plenty does. Verifying it means a reverse DNS lookup on the source address, which is a different job. Search engines, AI crawlers, SEO tools, link-preview fetchers and command-line clients are all recognised.

Modern Chromium browsers freeze their reported version — you will see 131.0.0.0 rather than a real build number — as an anti-fingerprinting measure. That is flagged, so nobody spends an afternoon wondering why every visitor appears to be on the same patch level.

How to use the User Agent Parser

  1. Paste a user-agent string

    From a server log, an analytics export, or use the button to fill in your own browser's.

  2. Read the breakdown

    Browser, engine, operating system and device appear separately, each with the version where the string carries one.

  3. Check for a crawler

    If the string claims to be a bot, the tool names it and says what kind — search engine, AI crawler, SEO tool, link preview or script.

  4. Watch for a frozen version

    A Chromium version ending in .0.0.0 is deliberately reduced. Treat it as "recent Chromium", not as a real build number.

Frequently asked questions

Why does my browser claim to be several browsers at once?

Historical compatibility. In the 1990s servers checked for "Mozilla" before serving frames, so every browser added it. The same thing happened with "like Gecko", "Safari" and later "Chrome". Nobody can remove those tokens now without some sites breaking, so the strings keep growing.

Can I trust a user agent that says it is Googlebot?

No. The user agent is just a text field the client chooses, and impersonating a crawler to get past a paywall or a rate limit is common. Google publishes the method for verifying it: do a reverse DNS lookup on the source address, check the name ends in googlebot.com or google.com, then resolve that name forward and confirm it matches.

Why does Chrome report version 131.0.0.0 instead of a real build?

Chromium reduced the user agent deliberately to limit fingerprinting. The minor, build and patch numbers are frozen at zero and the platform detail is coarser. Sites that genuinely need more are expected to ask for it through the User-Agent Client Hints API, which requires the visitor's browser to grant it.

Why can an iPad look like a Mac?

Since iPadOS 13, Safari on an iPad requests desktop sites by default and its user agent says Macintosh. There is nothing reliable left in the string to distinguish them, which is why device detection here is described as a guess rather than a fact.

Is the string I paste sent anywhere?

No. Parsing happens entirely in your browser and nothing is transmitted or stored. That matters because a user agent from a log file is linked to a visitor, and in several jurisdictions counts as personal data.