What Is My User Agent?

Every time your browser loads a page, it usually sends a User-Agent header — a short text string that describes the client software. Historically it named the browser engine, version, and operating system so servers could send compatible HTML, warn about unsupported features, or collect rough analytics. Today the string is still useful for debugging “works on my phone but not my laptop” reports, even though browsers deliberately reduce how unique and detailed that string is.

Routerpedia’s “What Is My User Agent?” tool shows the UA our server received on this request and the value JavaScript reads from navigator.userAgent. They normally match, but extensions, corporate proxies, or developer overrides can change one side. If you are testing a router admin UI, captive portal, or ISP app that behaves differently by device, copying the exact UA into a bug report saves time.

Consumer websites may switch between mobile and desktop templates, load lighter assets on small screens, or block ancient browsers that lack security features. Download sites sometimes suggest Windows vs macOS installers based on UA hints. Analytics suites group traffic by browser family. None of this identifies you as uniquely as a logged-in account, but it is still metadata tied to the session along with your public IP.

Home routers and ISP gateways sometimes present different captive-portal pages to phones versus desktops. Mesh apps may reject unsupported WebViews. When a manufacturer says “open this URL on a device connected to the LAN,” knowing whether the portal sees you as mobile helps explain missing menus. Pair UA checks with local IP and DNS tools when onboarding new access points.

Chrome, Edge, and other Chromium browsers have frozen or reduced parts of the classic UA string to limit passive fingerprinting. You might see a generic OS token or an older fixed version number even though your browser is current. Apple has long limited how much Safari reveals. As a result, “detect browser version from UA alone” is less reliable than it was a decade ago. Modern sites increasingly use feature detection and optional Client Hints headers instead of brittle UA parsing.

For SEO and AdSense publishers, that shift matters when you write device-specific content: do not assume the UA proves a precise Chrome minor version. For troubleshooting, the full string you see on this page is still what many server logs record, so it remains the right artifact to paste into support tickets.

Developers spoof user agents to emulate mobile Safari inside desktop Chrome, to scrape pages, or to bypass naive blocks. Because spoofing is easy, sites should never treat UA as strong authentication. Privacy-focused browsers may send deliberately bland strings. If you use a VPN or proxy, your proxy check and ISP lookup may change while your UA stays the same — they answer different questions about the connection versus the client software.

Routerpedia does not store your user agent as a personal profile when you view this tool; it is displayed for the current response the way any web server can already see the header. Our privacy policy explains broader logging practices for forms and analytics.

Classic user agents read like a nested list of product tokens. You might see Mozilla/5.0 first — a historical compatibility token — followed by platform details such as Windows NT 10.0 or Macintosh; Intel Mac OS X, then engine and browser clauses like AppleWebKit/537.36 and Chrome/120.0.0.0. Mobile strings often include Mobile or device model fragments. Server-side parsers on this page simplify that into browser, version, and platform cards for quick copy-paste into support tickets.

Do not treat the rightmost version number as gospel on Chromium browsers undergoing UA reduction — the real feature set may be newer than the frozen token suggests. When a router vendor publishes a “supported browsers” list, compare your full string against their examples rather than assuming Safari-on-iPhone behaves like desktop Safari. If you file a bug with Routerpedia or another site, include both the server UA and the JavaScript navigator.userAgent value when they differ.

Televisions, streaming sticks, and game consoles ship with WebKit or Chromium variants that report unfamiliar user agents. Router admin pages designed for desktop Chrome may render poorly on a ten-foot UI with an older engine. If you must manage Wi‑Fi from the TV browser, note the UA here on a laptop first to see whether the vendor even targets that client. Some mesh apps embed WebViews with their own UA independent of the system browser you normally use.

Captive portals on hotel or ISP networks sometimes branch on mobile UAs to show simplified login forms. At home, parental-control apps may inject filtering proxies that alter headers. Pair UA inspection with What is my proxy? when a portal behaves differently across devices on the same SSID. For LAN-side management, confirm you are on the expected subnet using local IP detection before blaming the user agent alone.

Developers change UAs through browser devtools device emulation to preview responsive layouts without owning every phone model. That override affects only the local tab and helps reproduce customer reports. Avoid spoofing to bypass paywalls or security controls — sites may block inconsistent combinations of UA, Client Hints, and TLS fingerprints.

After toggling emulation, reload this page to confirm the string your test environment sends. Clear overrides before normal browsing so banking and router admin sessions use your real client identity. When testing remote access to a home server, also verify your public IP and ISP from the same network path users will take. Wi‑Fi setup flows benefit from strong credentials via the WiFi Password Generator regardless of which browser completes the wizard.

When a router page looks broken, try another browser before factory-resetting hardware. Copy the UA from this tool, note whether you are on Wi‑Fi or Ethernet, and confirm you are hitting the intended gateway IP from our IP addresses guides. Some admin skins fail in embedded smart-TV browsers with unusual UAs. If an ISP support chat asks “what device are you using?”, the platform and browser fields above give a clearer answer than “my phone.”

For developers hosting local tools on a home server, log UAs alongside request paths when diagnosing mobile layout bugs. Combine with DNS Lookup if a hostname resolves differently than expected. Exploring all free utilities from our tools directory covers IP identity, Wi‑Fi sharing, and subnet planning in one place.