Parse and analyze user agent strings to extract browser, OS, device type, and rendering engine information
Paste any user-agent string and instantly see the browser name and version, operating system, device type, and rendering engine. Useful for debugging request headers, analyzing access logs, and understanding what clients are hitting your servers.
Initializing in your browser…
Analyze password security with 10 criteria checks, entropy calculation, crack time estimation, character breakdown, warnings, and improvement suggestions
Analyze any URL for phishing, suspicious patterns, and security risks. Detects login keywords, suspicious TLDs, encoded characters, brand impersonation, and more
Decode and analyze PEM-encoded X.509 SSL/TLS certificates. View subject, issuer, validity, extensions, and fingerprints
A bug only reproduces for one customer. Their support ticket includes a raw User-Agent string and you need to know exactly what browser and OS to test.
Raw User-Agent header
Mozilla/5.0 (iPhone; CPU iPhone OS 17_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.2 Mobile/15E148 Safari/604.1
Parsed components
Browser: Safari 17.2 Engine: WebKit 605.1.15 OS: iOS 17.2 Device: Apple iPhone (mobile) Form factor: Mobile Bot: No
The User-Agent is a single dense string that crams browser, engine, OS, and device into legacy "Mozilla/5.0 … like Gecko" tokens kept only for compatibility. The parser maps those tokens to structured fields so you can reproduce the exact environment, here, mobile Safari 17.2 on iOS, which has very different CSS and JS behaviour from Chrome on Android.
Paste any user-agent string and instantly see the browser name and version, operating system, device type, and rendering engine. Useful for debugging request headers, analyzing access logs, and understanding what clients are hitting your servers.
Parse the User-Agent header from failing requests to identify client-specific issues.
Decode user-agent strings from server logs to understand your traffic mix across browsers and devices.
Identify crawlers, scrapers, and automated agents by examining their user-agent signatures.
Decades of browser history led to each new browser appending compatibility tokens. Chrome's UA includes "Mozilla""AppleWebKit"and "Safari" for legacy reasons.
No. Prefer feature detection (e.g., checking if an API exists in the browser) over user-agent sniffing, which is fragile and easily spoofed.
This runs as client-side JavaScript. Keys, tokens, payloads, and other inputs never leave your device.