What Is a User Agent String?

BinVerify · · 5 min read

What the User-Agent header is

Browsers, apps and bots send a User-Agent header with their HTTP requests to identify the software, its version and the operating system. RFC 9110, which defines HTTP semantics, says servers often use it to identify the scope of reported interoperability problems, to work around limitations of particular user agents and for analytics on browser and operating system use.

The value is one or more product identifiers, each a name with an optional version after a slash, followed by optional comments in parentheses. RFC 9110 also asks user agents not to send needlessly fine-grained detail: long and detailed values increase the risk of a user being identified against their wishes, known as fingerprinting.

How to read a user agent string

The example on the User Agent Parser page is a string that names Chrome 120 on a Google Pixel 7: “Mozilla/5.0 (Linux; Android 13; Pixel 7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.6099.144 Mobile Safari/537.36”. Its parts:

  • Mozilla/5.0: a general token saying the browser is Mozilla-compatible; for historical reasons, almost every browser sends it.
  • (Linux; Android 13; Pixel 7): a comment with the platform, here the Android version and the device model.
  • AppleWebKit/537.36 (KHTML, like Gecko): engine names kept for compatibility. Chrome's own engine is Blink, which MDN's detection table identifies by the Chrome/ token.
  • Chrome/120.0.6099.144: the browser name and its full version; 120 is the major version.
  • Mobile Safari/537.36: “Mobile” marks a mobile device and “Safari” is another compatibility token, which is why Chrome reports both Chrome and Safari.

User-agent reduction and client hints

Because the string can be used for fingerprinting, supporting browsers now send less detail. Under Chromium's User-Agent Reduction plan, Chrome 101 replaced the minor version numbers with “0.0.0”, the reduced desktop string rolled out from Chrome 107 and the reduced Android string from Chrome 110, where the device model became “K” and the Android version a fixed “10”.

So Chrome 120 on an Android phone normally sends “Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Mobile Safari/537.36”, and the example above is in the older, full format. Chromium's page, whose latest dated update is from May 2023, says there are no plans for the reduction on iOS or in Android WebView.

The removed details are available through User-Agent Client Hints, a draft from the Web Platform Incubator Community Group (WICG), not a W3C standard. Over HTTPS, Chromium-based browsers send three of these hints by default: Sec-CH-UA with the brands and major version, Sec-CH-UA-Mobile and Sec-CH-UA-Platform. A server that needs more, such as the device model in Sec-CH-UA-Model, asks for it in an Accept-CH response header, and the browser decides whether to send it.

Bots and crawlers

Crawlers name themselves in the header too; MDN's Googlebot example contains “Googlebot/2.1”. But a client can send any string, and Google warns that Googlebot's user agent is often spoofed by other crawlers. To check a visitor that claims to be Google, Google documents these steps:

  • Run a reverse DNS lookup on the IP address from your logs.
  • Check that the domain name is googlebot.com, google.com or googleusercontent.com.
  • Run a forward DNS lookup on that host name.
  • Check that it returns the original IP address.

For large numbers of requests, Google suggests matching the IP address against its published lists of crawler IP ranges instead.

How fraud and security teams use it

A user agent is a claim, not a verified fact. MDN notes that browsers routinely pretend to be other browsers and that client hints are not as commonly spoofed. Visa asks merchants to report the User-Agent header of attack transactions along with their IP and email addresses. Fraud and security teams compare the string with other signals to spot bots and unusual devices, for example:

  • The client hints, which Chromium-based browsers send alongside the string.
  • The IP address: VPN & Proxy Detection shows whether it belongs to a hosting company, a VPN service or a known proxy.
  • For a visitor that claims to be Googlebot, the DNS check above.

Treat a mismatch as a reason to look closer, not as proof of fraud on its own.

What User Agent Parser returns

User Agent Parser compares a string with a database of known browsers, operating systems, devices and bots and turns it into readable fields. For the example string it returns:

  • Type Phone, Browser / Agent Chrome, Version 120.0.6099.144 (Major: 120), Engine Blink, Release Date 2023, Current Version No and Frozen UA No.
  • Operating System Android 13, OS Family Android, OS Version 13 (Major: 13), Mobile Yes and WebView No.
  • Device Brand Google, Device Model Pixel 7 5G, Model Code Pixel 7, Device Release 2022 and Device Price 500 USD, an estimated retail price.
  • Resolution 1080x2400, PPI 416, Pixel Ratio 3, Screen Size (px) 360 × 800 px and Screen Size (mm) 65 × 146 mm.

Rows the parser cannot fill are left off. For a reduced string, the result marks Frozen UA, and the exact version can be missing. The result shows what the string claims; it does not verify the device.

Terms in this guide: User agent, VPN (virtual private network), Proxy

Sources

  1. User-Agent header (MDN Web Docs, October 2025)
  2. HTTP Semantics, RFC 9110, Section 10.1.5 User-Agent (IETF, June 2022)
  3. Browser detection using the user agent string (UA sniffing) (MDN Web Docs, January 2026)
  4. User-Agent Reduction (The Chromium Projects)
  5. User-Agent Client Hints, Draft Community Group Report (Web Platform Incubator Community Group, October 2026)
  6. HTTP Client hints (MDN Web Docs, December 2025)
  7. Sec-CH-UA header (MDN Web Docs, July 2025)
  8. What Is Googlebot (Google Search Central, February 2026)
  9. Verify requests from Google crawlers and fetchers (Google Crawling Infrastructure, March 2026)
  10. Enumeration Mitigation and Considerations for Merchants, V1.3 (Visa, June 2026)