TXT · Text & Data tools

User Agent Parser & Bot Detector

OR
Test:
Awaiting User-Agent string...

Parse and detect

Paste a raw User-Agent string or HTTP header to instantly extract the browser, operating system, device type, hardware model, and rendering engine.

Click Use my browser’s UA to parse your own device. When supported, the tool will also request high-entropy Client Hints to expose deeper details like architecture, bitness, and platform version that the standard User-Agent string hides.

Bot and crawler identification

The built-in bot detector highlights common automated agents. It flags search engine crawlers (Googlebot, Bingbot), SEO tools (AhrefsBot), AI crawlers (GPTBot, ClaudeBot), social preview bots, and automation tools (Headless Chrome, Lighthouse).

When an automated pattern is matched, the tool displays an alert badge and the bot category to help you investigate server logs or verify robots.txt access rules. Remember that User-Agent strings are self-reported and can be spoofed; always verify crawler IPs for critical decisions.

Token breakdown and export

User-Agent strings are full of legacy baggage. The Token Breakdown table isolates confusing compatibility fragments—like Mozilla/5.0, AppleWebKit, or KHTML, like Gecko—and explains why they appear in modern browser strings.

Once parsed, you can click Copy Link to share a URL that preserves the exact User-Agent string in the page hash. Click Copy JSON to export the structured browser data and any available Client Hints for bug tickets or development workflows.

Frequently Asked Questions

It reads a User-Agent string and extracts recognizable details such as browser, browser version, operating system, device type, device model, rendering engine, and CPU information when those values are available. It also flags common bots, crawlers, social preview agents, SEO tools, AI crawlers, automation tools, and audit tools.

Yes. Use the browser-detection button to load your current browser's User-Agent string. When supported by your browser, the tool can also request high-entropy Client Hints such as platform version, architecture, bitness, model, and full version details.

Yes. It recognizes common patterns such as Googlebot, Bingbot, Facebook External Hit, Twitterbot, AhrefsBot, SemrushBot, GPTBot, ClaudeBot, Headless Chrome, and Lighthouse. Bot detection is pattern-based, so it should be treated as a helpful signal rather than absolute proof of identity.

Yes. User-Agent strings are self-reported by the client and can be changed or faked. For security decisions, combine User-Agent analysis with server logs, IP verification, reverse DNS checks, request behavior, rate limiting, and official crawler verification guidance.

Client Hints are browser-provided values that can expose more structured information than the classic User-Agent string, such as platform, architecture, bitness, model, and version lists. Availability depends on the browser and privacy settings.

Many browser User-Agent strings contain historical compatibility tokens. Chrome and Chromium-based browsers often include strings such as AppleWebKit and Safari even though the browser is not Safari. The token breakdown explains these legacy pieces.

No.

Yes. The tool stores the current User-Agent in the page hash, so you can copy a shareable link without sending the string to a backend. You can also copy the parsed result as JSON.

Explore Our Tools

Browse all tools