User Agent & Device Inspector

Parse browser User-Agent strings to extract browser version, operating system, rendering engine, and device type.

Category: URL & Internet

How to Use User Agent & Device Inspector

Paste any client User-Agent string into the input box or leave it blank to analyze your current device.
Click Parse User Agent or Execute to break down the string into structured client metadata.
Inspect extracted browser family, version number, OS platform, CPU architecture, and rendering engine.
Copy single parameters or download the full device inspection report in 1 click.

Related URL & Internet Tools

URL Encoder & Decoder
Percent-encode query parameters or decode percent-encoded URLs with UTF-8 support and RFC 3986 compliance.
URL Parser & Query Extractor
Parse complex URLs into protocol, hostname, path, port, hash, and individual query parameters with instant decoding.
URL Cleaner & Tracking Stripper
Remove UTM parameters, fbclid, gclid, and analytics trackers to create clean, shareable canonical URLs.
IPv4 Subnet & CIDR Calculator
Calculate network address, broadcast address, netmask, wildcard mask, and usable host IP ranges with accurate /31 and /32 support.
HTTP Status Code & Security Headers Inspector
Look up definitions, causes, and troubleshooting fixes for HTTP 1xx, 2xx, 3xx, 4xx, and 5xx status codes with security header guides.

Frequently Asked Questions

What is a User-Agent string and what information does it typically contain?

A User-Agent (UA) is an HTTP request header string (defined in RFC 9110) that client software sends to web servers to identify itself. It typically contains tokens specifying the browser application name and version, the host operating system and CPU architecture, the rendering engine (e.g., AppleWebKit, Gecko), and compatibility tokens indicating browser lineage.

Can User-Agent strings be spoofed or modified by clients?

Yes. User-Agent strings are entirely client-controlled and can be modified or spoofed easily using browser Developer Tools, custom HTTP request headers, command-line tools like curl or Postman, proxy extensions, or automated web scraping frameworks (Puppeteer, Playwright). Because UA strings can be forged, web applications should never rely exclusively on User-Agent headers for critical authentication, security authorization, or billing decisions.

Why do almost all modern browsers include 'Mozilla/5.0' and 'like Gecko' in their User-Agent strings?

This historical legacy dates back to the early web browser wars. When Netscape (internally codenamed Mozilla) was the dominant browser, web servers filtered out other browsers. Internet Explorer added 'Mozilla/2.0 compatible' so servers would send full modern content. When Apple developed Safari with WebKit, they included 'AppleWebKit' and 'like Gecko' so servers treating Mozilla/Gecko browsers specially wouldn't degrade pages. When Google built Chrome, they included 'Safari' and 'AppleWebKit'. Today, nearly all major browsers maintain these tokens to avoid breaking legacy web server sniffers.

What are User-Agent Client Hints (Sec-CH-UA) and how do they improve privacy?

User-Agent Client Hints (defined by W3C and IETF) are a modern, privacy-preserving alternative to traditional monolithic UA strings. Rather than transmitting a detailed User-Agent string on every HTTP request that enables cross-site device fingerprinting, browsers send minimal low-entropy headers (e.g., Sec-CH-UA, Sec-CH-UA-Mobile, Sec-CH-UA-Platform). Web servers must explicitly request higher-entropy details (like exact OS versions or device models via the Accept-CH header) only when genuinely required.

Does this inspector detect search engine crawlers, bots, and command-line tools?

Yes. The inspector identifies search engine crawlers (Googlebot, Bingbot, DuckDuckBot), AI web scrapers (GPTBot, ClaudeBot, CCBot), social media link preview bots (Twitterbot, facebookexternalhit), and developer command-line utilities (curl, Wget, PostmanRuntime).