HTTP Status Code Reference
A searchable reference for every HTTP status code, with practical guidance.
Break a user agent string into browser, engine, OS and device.
Your own browser's string is loaded for you. Replace it with any other to parse that instead.
User Agent Parser takes the long, historically confused string a browser sends with every request and tells you what it actually describes: the browser and version, the rendering engine, the operating system, and whether the device is a desktop, a phone, a tablet or a bot.
User agent strings are famously misleading. Nearly every browser still claims to be Mozilla for compatibility reasons dating back to the 1990s, Chrome strings mention Safari, and Edge mentions both. The parser works through those layers in the right order so that a Chrome string is identified as Chrome rather than as the three other browsers it name-checks.
Your own browser's string is shown at the top, alongside the modern client hints your browser exposes where it supports them. Those hints are the replacement for user agent sniffing, and they are more reliable precisely because they are structured rather than being a sentence.
The user agent parser is used by writers, developers, students, marketers and anyone else who needs the job done once without installing software. Common cases include:
A historical accident. Early servers checked for Mozilla before sending modern pages, so every browser added it to avoid being downgraded. The claim has been meaningless for decades and is still there because removing it would break old sites.
No. It is freely editable by the client, and plenty of tools, privacy extensions and bots change it. Treat it as a hint for analytics and never as a security measure or an access control.
Only as a last resort. Feature detection, which tests whether the thing you need actually exists, is more reliable and does not break when a new browser appears. User agent sniffing is how sites end up broken in browsers released after they were written.
Structured headers that report browser, platform and device characteristics individually rather than as one sentence. They are the intended replacement for user agent sniffing and are shown here when your browser provides them.
Browsers have begun reducing the detail in user agent strings for privacy, reporting a frozen major version and a generic platform. That is deliberate, and client hints are the supported way to ask for more.
No. Parsing happens in your browser, and nothing is logged.
If the user agent parser is not quite what you need, these other free tools solve closely related problems.
A searchable reference for every HTTP status code, with practical guidance.
Look up MIME types by extension, or find which extensions use a type.
Build security header configuration for Apache, nginx, Netlify or Vercel.
Generate cryptographic hashes of text, computed in your browser.
Convert times across time zones, with daylight saving handled correctly.