Parse your browser User-Agent string into readable components: browser, version, OS, device type, and rendering engine.
Your current User-Agent is automatically detected and parsed on load.
Review the parsed components: browser, version, OS, device, and engine.
Paste a custom User-Agent string to analyze it for anomalies or outdated versions.
Browser name and full version, operating system and version, device type (desktop, mobile, tablet), rendering engine (Blink, Gecko, WebKit), bot detection flags, and whether the UA string matches known automation patterns.
An inconsistent or outdated User-Agent is the fastest path to getting blocked. If your UA claims Chrome 120 but your TLS fingerprint says Chrome 90, anti-bot systems flag the mismatch. Understanding what your UA reveals helps you build consistent, undetectable browser profiles for proxy-based work.
The parser uses regex pattern matching against the navigator.userAgent string to extract browser tokens, version numbers, OS identifiers, and platform markers. It cross-references these against a database of known browser release versions to detect outdated or synthetic UAs. Mobile detection uses the combination of platform token and touch capability.
A User-Agent (UA) string is a header your browser sends with every HTTP request identifying itself. It includes the browser name, version, operating system, and rendering engine. Example: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36.
Yes. Most HTTP libraries let you set a custom User-Agent header directly in the request config. In browsers, extensions can override it too. For scraping, always set a current, realistic UA that matches your other fingerprint signals, like TLS, header order, and JavaScript properties.
Anti-bot systems check that the User-Agent string matches the browser it claims to be. A Chrome UA paired with Firefox-style header ordering, missing Chrome-specific JavaScript APIs, or an outdated TLS fingerprint triggers detection instantly. Consistency across every signal, not just the UA, is what matters.
Run this check again from a clean residential proxies exit and see what actually reaches the other side.