User-Agent
What is User-Agent?
The User-Agent header is an HTTP request field, defined in RFC 9110, that lets a client identify its software -- conventionally a string naming the browser, its engine and the operating system. It's client-supplied and unverified, so AdminKit's User-Agent tool treats what it parses as a self-reported hint, not a verified fact.
By AdminKit team, Netbase JSC · Updated
The User-Agent header is an HTTP request field, defined in RFC 9110 section 10.1.5 (current document status at its IETF Datatracker entry), that lets a client identify the software making the request — conventionally a string of product names and versions, such as a browser name, its rendering engine, and the operating system it runs on. Servers and clients both use it informally: RFC 9110 notes that servers often scan the User-Agent value, and clients often scan a server’s own Server field, to work around known bugs or poorly chosen defaults in a specific version, rather than as part of any formal negotiation. MDN’s User-Agent header reference describes the value as a characteristic string identifying the application, operating system, vendor and/or version of the requesting user agent, and warns that serving different content to different browsers based on it is usually a bad idea.
Because the field is client-supplied, with no fixed schema beyond a list of product tokens and comments, it can be spoofed, omitted, or trimmed — like Referrer-Policy, another header a server can only read and not verify, User-Agent is reported by the client in good faith rather than enforced by the protocol. That’s part of why some browsers now send a shorter, less detailed User-Agent string by default for privacy — steering sites instead toward the User-Agent Client Hints model, an opt-in mechanism where a site must explicitly request specific details rather than receiving them with every request by default.
User-Agent is part of AdminKit’s IP and network cluster, next to the other checks on what your connection and device reveal; what a User-Agent string reveals explains what each token in the string means, and the full AdminKit glossary lists other related terms.
Frequently asked questions
What does the User-Agent header identify?
The software making the request -- conventionally a string naming the browser, its rendering engine and the operating system.
Is the User-Agent value verified by the server?
No -- it is client-supplied and unverified, so AdminKit's own User-Agent tool treats what it parses as a self-reported hint, not a verified fact.
How do servers and clients informally use the User-Agent and Server fields?
To work around known bugs or poorly chosen defaults in a specific version, rather than as part of any formal content negotiation, per RFC 9110.
What is replacing detailed User-Agent strings for privacy?
User-Agent Client Hints, an opt-in model where a site must explicitly request specific details instead of receiving them with every request by default.