Do I need to spoof a different browser to access a site?

Use spoofing only for testing. Keeping a real, up-to-date browser and user agent is safer and more compatible.

Why does a site say I'm on an old Chrome version after updating?

Stale service workers, cached assets, or user-agent spoofing extensions often cause this. Clear site data and retest.

Can VPNs change the user agent?

VPNs change your IP, not your user-agent string. If the UA looks wrong, focus on extensions, enterprise policy, or compatibility mode.

Fix 'Your Browser Is Not Supported' and Wrong User-Agent (Run the Browser Test)

Confirm what the site sees

Open the Full Browser Test to see your real engine, version, and feature support. Then open the User-Agent Check. If the user-agent string looks wrong (for example, shows an old Chrome 90 build or a different OS), you likely have compatibility mode or a spoofing extension turned on. Keep both tabs open and re-run them after each fix.

Fix 1: Update to a supported version

Most apps require current builds of Chrome, Edge, Firefox, or Safari.

Update via Menu > Help > About (Chrome/Edge/Firefox) or System Settings > General > Software Update on macOS for Safari.
After updating, rerun the Browser Test. If the site still complains, continue below.

Fix 2: Turn off compatibility or IE Mode in Edge

Edge can render sites in Internet Explorer mode, which many apps block.

Go to edge://settings/defaultBrowser.
Set Allow sites to be reloaded in Internet Explorer mode to Disabled.
Remove the site from the Internet Explorer mode pages list if present.
Reload the app and check User-Agent Check to confirm it now shows a modern Edge/Chrome string.

Fix 3: Disable user-agent spoofing extensions

Extensions that fake your browser can trigger "unsupported" warnings.

Disable extensions named User-Agent Switcher, Privacy spoofers, or anything that rewrites headers.
Open the site in Incognito/InPrivate (extensions off). If it works there, keep the spoofing extension disabled or set it to "Default" for the site.

Fix 4: Reset custom command-line flags

Flags passed to browser shortcuts can alter the user-agent or disable modern features.

Remove flags like --user-agent=..., --disable-features=SameSiteByDefaultCookies, or other overrides from your shortcut or policy.
Launch the browser normally and retest.

Fix 5: Enable required features blocked by privacy settings

Some sites fail when JavaScript, cookies, or storage are blocked.

Ensure Cookies and JavaScript are allowed for the site in Settings > Privacy and security > Site settings.
If you previously disabled third-party cookies and the site relies on SSO, allow the identity domain as an exception (see our third-party cookies guide).

Fix 6: Clear old service workers and cache for the app

Stale cached files can convince the app you are on an old build.

Open DevTools > Application > Service Workers and click Unregister for the site, or clear site data from Settings > Privacy and security > Clear browsing data > Cached images and files (choose the site via Cookies and other site data > See all site data and permissions for a precise wipe).
Reload and rerun the Browser Test.

Fix 7: Check enterprise policies forcing legacy modes

Managed devices might force older engines or block required APIs.

Visit chrome://policy or edge://policy and look for policies that set IE mode or override the user-agent.
If present, share the User-Agent Check output with IT and request a policy update.

Verify the fix

Run the User-Agent Check again. It should show your current browser and OS accurately. The Full Browser Test should be green on core HTML5 and CSS checks. Reload the problem site; the unsupported banner should disappear. If it remains, try another browser profile to rule out profile corruption.