Websites may obtain browser information through User-Agent headers, JavaScript, and Client Hints. Learn their differences, default and requested data, why changing UA does not change the whole device environment, and how to investigate your own website.
User-Agent is one way a browser describes itself to a website, not a device identity card. Modern sites may also read script interfaces, Client Hints, and other operating conditions. Changing a UA string does not change the operating system, capabilities, or every visible signal.
Developers should provide features according to actual capabilities. Users and operations teams should understand which information is exposed and what it can—and cannot—establish.
Why UA strings are easily misread
The User-Agent request header usually includes browser and platform markers; scripts can read navigator.userAgent. Historical compatibility means several product names may appear. They do not each identify a separate browser currently in use.
UA can also be reduced, modified, or rewritten by intermediaries. Checking one word in the string can incorrectly block a capable browser.
If a page requires file uploads, for example, test the relevant interfaces and behavior instead of assuming support from the browser name. UA provides limited compatibility clues, not a replacement for feature detection.
What Client Hints change
Chrome’s User-Agent Client Hints explanation describes requesting structured client information. Rather than parsing a long string, a site can ask for relevant fields, while the browser decides what to provide under its policies.
Distinguish the interfaces and transport methods.
| Information source | Where it appears | What to investigate |
|---|---|---|
User-Agent | HTTP request header | Value actually sent by that request |
navigator.userAgent | Page JavaScript | String observed by that page’s script |
Hints such as Sec-CH-UA | Request headers in supporting browsers | Whether sent, field meaning, and requesting conditions |
navigator.userAgentData | Supporting script environments | Interface availability and returned fields |
Headers and scripts are different observation points. CDNs, proxies, caches, and server logs can represent different processing layers. Establish where data was collected before comparing expectations.
Low and high entropy do not mean trustworthy and untrustworthy
Entropy describes how much distinguishing information a signal can provide. It does not guarantee accuracy or indicate an account’s risk level.
MDN’s NavigatorUAData documentation distinguishes basic properties from additional information requested asynchronously and advises checking compatibility. More fields do not mean every site receives a complete, precise, unmodifiable device inventory by default.
For your own site, ask why a field is needed. Prefer responsive design for layout and feature detection for capabilities. Do not collect every available field simply because an interface exists.
Inspect basic information in your browser
This example reads basic information visible locally and sends nothing to an external server. Run it on a test page you control or in developer tools.
const browserInfo = {
userAgent: navigator.userAgent,
hints: navigator.userAgentData?.toJSON() ?? null,
};
console.log(browserInfo);
If hints is null, consider support and execution conditions before concluding the browser is faulty. Browsers, versions, and contexts may return different results; pages need sensible fallbacks.
To inspect headers, select a particular request in the Network panel and read what was actually sent. Do not mix script output with a different request, another tab, or historical cache records.
Check the whole chain when requesting more hints
A server can request hints through mechanisms such as Accept-CH. Whether they arrive, on which request, and whether the browser permits them must be verified in real traffic. HTTPS, support, and policies can affect availability.
First record whether the response requested the expected hints, then inspect subsequent requests for corresponding fields. With CDNs or caches, check that response variants are separated according to actual rules so one browser does not receive a response prepared for another condition.
A missing field on the first request does not establish failed “disguise.” Absence may be a normal result of support or negotiation.
Why changing UA does not change the whole environment
UA is only one signal. Language, time zone, window conditions, graphics, fonts, extensions, and site data can affect pages through other mechanisms. Changing one setting does not automatically change other layers.
Putting a mobile device name in the string does not give a desktop its touch capabilities, layout, or hardware. A site displaying mobile controls solely from that string can create confusing compatibility issues.
Environment management should favor stable business configurations and traceable records over frequent random changes. Platform rules, login security, and authorized account operations still require separate management.
Investigate “same account, different page” as a team
Record the environment, browser version, URL, time, and affected feature, then gather only the relevant minimum information. Change one condition at a time when comparing working and failing environments.
In PurpleMark, review operating system, engine version, User-Agent, language, and time zone in environment settings, then open your test page inside that environment. Grouping by client or purpose makes reviews easier to connect to actual work.
Do not infer certain safety or restrictions from a testing website’s score. Such pages observe only the signals they test, not the target website’s complete behavior or internal platform decisions.
A checklist for website developers
- Use feature detection for critical functions; limit UA checks to necessary, bounded compatibility handling.
- Provide working fallbacks without Client Hints instead of unusable blank pages.
- Distinguish headers, script output, and intermediary-processed logs.
- Request only business-relevant information and handle it according to actual privacy notices.
- After browser updates, retest the same pages and inputs instead of attributing every difference to fingerprints.
Understanding UA and Client Hints reduces mistaken conclusions. Websites observe conditional signals with compatibility boundaries. Interpret them within real tasks to improve both compatibility and privacy management.


