Web tool / 17
User Agent Parser
Identify common browser, version, operating system, device class, engine, and bot signals locally.
User Agent Parser: TOEA applies transparent browser-side rules for common Edge, Opera, Firefox, Chrome, Safari, Googlebot, Windows, Apple, Android, and Linux signatures. Runs 100% locally in your browser with zero server file uploads.
- Category
- Web tools
- Runs
- In your browser
- Cost
- Free · no sign-up
- Availability
- Ready to use
Runs entirely in your browser
Why modern user agents say less
Browsers now reduce the user-agent string to limit tracking. Chrome and Edge report only the major version, as in Chrome/126.0.0.0, Windows 11 appears as Windows NT 10.0, and macOS versions are frozen at 10_15_7. iPads show a Mac user agent by default, because Safari on iPad requests desktop sites. Chromium browsers offer the precise details through User-Agent Client Hints, Sec-CH-UA request headers that a site must ask for.
Verifying a bot
Anyone can send a user agent that says Googlebot. To confirm a request really came from Google, look up the IP address in reverse DNS: it should resolve to a name ending in googlebot.com or google.com, and that name should resolve back to the same IP. Bing documents the same check with search.msn.com. Google also publishes its crawlers' IP ranges. For a site's rules for each crawler, use the robots.txt checker.
How to use it
- Paste a user-agent string or use this browser.
- Choose Parse user agent.
- Review the detected client traits.
Privacy & limitations
Parsing is entirely local. User-agent strings can be spoofed and detection is a useful hint, not trusted identity.
Related tools
Frequently asked questions
Can a user agent prove the browser?
No. Any client can send an arbitrary string.
Why might a new browser be unknown?
Browser signatures evolve, and less common clients may not match the intentionally focused rules.
Free tool · runs in your browser · no account required