Free developer tool
User-Agent Parser
Break a User-Agent string into browser, engine, OS and device, and spot Googlebot, Bingbot and AI crawlers.
Try:
- Browser
- —
- Rendering engine
- —
- Operating system
- —
- Device type
- —
- Device model
- —
- CPU architecture
- —
Read any User-Agent string
Every browser and crawler sends a User-Agent header. This tool breaks it into browser and version, rendering engine, operating system, device type and model, using the open-source ua-parser-js library. It opens with your own browser's string.
For SEO work it also recognizes the crawlers that matter: Googlebot and its variants, Bingbot, Applebot, the major AI crawlers (GPTBot, ClaudeBot, PerplexityBot and others) and SEO tools like AhrefsBot and SemrushBot. Paste lines from your server logs to see who's visiting.
Limits of User-Agent strings
- Anyone can fake a User-Agent. Confirm real Googlebot visits with a reverse DNS lookup of the IP address.
- Browsers are freezing parts of the string, so Windows 11 still reports Windows 10 and macOS versions are capped.
- For precise data, modern Chromium browsers offer User-Agent Client Hints instead.
Frequently asked questions
- How do I verify that a visit was really from Googlebot?
- Run a reverse DNS lookup on the IP address. It should resolve to a host ending in googlebot.com or google.com, and a forward lookup of that host should return the same IP. Google also publishes its crawler IP ranges.
- Why does my Windows 11 PC show as Windows 10?
- Browsers stopped updating the Windows version in the User-Agent string, so both report "Windows NT 10.0". Only User-Agent Client Hints can tell them apart.
- Is the User-Agent I paste sent anywhere?
- No. Parsing happens in your browser.