About this tool
Inspect a User-Agent header as self-declared compatibility evidence, while keeping spoofing, browser reduction, and bot-verification limits visible.
- Uses the MIT-licensed Bowser 2.14.1 parser for browser, operating-system, platform, device, and rendering-engine interpretation.
- Separates named and generic bot-token matches from verified crawler identity, and exposes the exact matched token.
- Rejects multiline and oversized inputs, preserves a source snapshot, blocks stale export, and downloads a versioned JSON evidence report.
How to use UA Parser
Parse a bounded User-Agent string into browser, OS, platform, engine, product-token, and bot-signature evidence with explicit uncertainty.
When this tool is useful
- Uses the MIT-licensed Bowser 2.14.1 parser for browser, operating-system, platform, device, and rendering-engine interpretation.
- Separates named and generic bot-token matches from verified crawler identity, and exposes the exact matched token.
- Rejects multiline and oversized inputs, preserves a source snapshot, blocks stale export, and downloads a versioned JSON evidence report.
Examples you can test
Load an example, compare the result with the expected output, then replace it with your own input.
Inspect a browser user agent
Example input
Mozilla/5.0 ... Chrome/126.0 Safari/537.36
Expected output
Browser: Chrome, engine: Blink/WebKit-style token, platform details
Useful for debugging support reports, analytics anomalies, and browser-specific issues.
Identify crawler-like traffic
Example input
Mozilla/5.0 compatible; Googlebot/2.1; +http://www.google.com/bot.html
Expected output
Crawler-style user agent details
User-agent strings can be spoofed, so use them as a clue rather than proof of identity.
Validation checklist
- Do not rely on user-agent strings alone for security decisions.
- Expect spoofed, outdated, or incomplete user-agent values.
- Pair user-agent review with headers, IP ranges, logs, or feature detection when accuracy matters.