What is a user agent string?
Every time a browser requests a page, it sends along a short line of text describing itself — the browser, its version, the rendering engine, and the operating system. That line is the user agent string. Servers read it to decide what to send back: a mobile layout for a phone, a desktop layout for Windows, or nothing at all for a browser too old to support the page.
What "cover strength" actually checks
Two things: whether the platform and browser you picked are commonly seen together in real traffic, and whether the version looks current. Safari doesn't ship for Windows anymore, so a Safari-on-Windows string will always read as unusual no matter how well-formed it is — that's a real signal a lot of basic testing tools skip. Read more in common mistakes that make a fake user agent obvious.
What this is useful for
Testing how a responsive layout behaves across browsers and devices without owning every device, checking that a site degrades sensibly for older browser versions, and debugging user-agent-based content branching during development. See our practical testing workflow for a fuller process.
What this won't do
Changing your user agent changes one signal, not your whole fingerprint — sites can still infer a lot from screen size, fonts, timezone, and dozens of other characteristics. If you're trying to understand fingerprinting more broadly, this breakdown covers what else is in play.