User-Agent Parser

The parser uses pattern matching against known browser, OS, and engine signatures in the UA string to identify components. Results are best-effort since UA strings can be spoofed.

Yes. The parser identifies common bots, crawlers, and spiders by matching known patterns like Googlebot, Bingbot, and others.

The tool automatically detects and displays your current browser's user-agent string when the page loads.

For compatibility. Chrome descends from WebKit, whose UA string copied Safari's, which itself copied earlier browsers - so today's Chrome UA reads Mozilla/5.0 ... AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36. Every token is a historical handshake with old server-side detection scripts, which is also why the last matching browser token is usually the real one.

A privacy-friendlier replacement shipped alongside Chrome's user-agent reduction. The server requests high-entropy hints with the Accept-CH response header and receives structured fields like Sec-CH-UA-Platform and Sec-CH-UA-Full-Version on subsequent requests. New code should prefer feature detection or UA-CH over parsing raw UA strings.

Reasonable for analytics and coarse routing, fragile for anything security-relevant. UA strings are trivially spoofed, third-party browsers often copy Chrome's token wholesale, and reduced UAs freeze the minor version. The best practice recommended by MDN: detect features (CSS @supports, if ('IntersectionObserver' in window)) rather than browsers, and treat UA parsing as a fallback.

Yes. Desktop Chrome, Edge, and Firefox DevTools offer device emulation with a UA override; Safari has Develop > User Agent; and curl sets it with -A. Sites that gate content on UA strings are bypassable by design - another reason servers should never treat a UA as proof of identity.

Chrome's freeze plan (rolling out since 2020) gradually strips version detail from the default UA: the minor version pinned to 0 and most device information removed, giving something like Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36. The goal is limiting passive fingerprinting; precise data moved to opt-in Client Hints.