Local browser tool

What Is My User Agent?

Check your User-Agent, Client Hints, platform, language, and browser fields that websites can read before you continue into fingerprint or leak testing.

This page runs locally in your browser. The User-Agent is not a privacy verdict by itself, but it can explain why websites classify your browser, device, or VPN session differently.

Browser signal

Current User-Agent

Local

Unavailable

Copy the full string for support tickets. For public sharing, use Safe Copy instead of posting raw User-Agent with account, IP, or location details.

Browser fingerprint Safe Copy Methodology

Short answer

Your User-Agent is one browser identity clue, not the whole fingerprint

A User-Agent can show browser family, engine, operating system, compatibility tokens, and sometimes device context. Modern browsers may reduce parts of it, but Client Hints, language, timezone, screen, WebRTC, IP route, and fingerprint signals can still add context.

Use this page when a website says your browser is unsupported or your device looks wrong.
Copy the User-Agent only when support needs it; avoid sharing it publicly with account or IP details.
Continue with Browser Fingerprint, WebRTC, and What Is My IP when you need the full visible-session picture.

Signal	What it can explain	Next MyIPScan check
User-Agent	Browser family, engine, OS tokens, compatibility mode, and app wrapper hints.	Copy this User-Agent
Client Hints	Reduced browser and platform context that some sites request instead of the full User-Agent.	Browser Fingerprint Test
IP route	Whether the visible network path matches your VPN, ISP, mobile carrier, or proxy expectation.	What Is My IP
WebRTC candidates	Browser network candidates that can differ from the normal page request.	WebRTC Leak Test
Safe summary	A share-safe diagnostic note without raw IP, exact city, full UA, or raw resolver/candidate data.	Safe Copy

User-Agent checker

What to check after asking "what is my user agent?"

Start with the full User-Agent string, then compare Client Hints, platform, language, and browser fingerprint signals. A support team may need the full string, but public sharing should use a safe summary instead.

Use the full User-Agent for private support tickets when a website detects the wrong browser or device.
Use Browser Fingerprint Test when a site still identifies the session after the User-Agent changes.
Use Safe Copy before sharing the result publicly.

What websites can see

A User-Agent can include browser family, rendering engine, operating system, and compatibility details. Modern browsers may reduce or freeze some values, but related client hints and browser APIs can still provide context.

Why it matters

On its own, a User-Agent is usually broad. Combined with language, screen, timezone, IP route, WebRTC, and other browser signals, it can become part of a larger fingerprinting profile.

Safe sharing note

User-Agent and Client Hints can help support teams, but raw values can add account or device context when shared publicly. Safe Copy keeps the summary category-focused.

See what Safe Copy includes before sharing a result.

Want the full picture? Run the Privacy Exposure Report.

Combine IP, WebRTC, IPv6, DNS leak, fingerprint, user-agent, and related privacy signals in one report.

Run report

Related tools

Continue the privacy check

Browser Fingerprint TestSee browser signals beyond the User-Agent. WebRTC Leak TestCheck whether browser networking exposes IP candidates. VPN Leak TestCompare browser and network privacy signals. What Is My IPCompare browser signals with your public IP route.

Before / after privacy flow

Compare one browser or VPN change at a time

This page is focused on User-Agent, Client Hints, platform, language, and browser identity clues. Use this page for support-ticket context, then use Public Exposure Report for a safer combined receipt. Results are visible browser/session signals, not a certification.

1. BaselineRun the focused check before changing VPN, DNS, browser, profile, or network settings.

2. Change one thingConnect or switch VPN, change Secure DNS, adjust WebRTC/fingerprint settings, or move networks.

3. RetestRun the same check again in the same browser/session when possible.

4. CompareReview changed and unchanged IP route, DNS, WebRTC, IPv6, fingerprint, and User-Agent signals.

5. Safe receiptUse Safe Copy or the Safe Privacy Receipt instead of sharing raw identifiers.

Status language

Use conservative result labels

These labels keep the result understandable without implying a VPN, browser, device, or account is safe.

Visible

A browser/session signal was visible and should be compared with what you expected.

Expected

The observed signal appears consistent with the stated route or browser behavior.

Review

The signal may need closer review before relying on this setup for the current session.

Limited

The check ran, but this page cannot cover every app, device route, server, or future connection.

Not detected

The tested signal was not observed in this browser/session.

Not checked

The signal has not run yet or the browser did not provide enough data.

Fix checklist

Where to review settings after a signal needs attention

Settings names change. Treat this as a route to verify, then rerun the focused check and the Public Exposure Report.

ChromeReview Secure DNS, WebRTC policy/extensions, profile state, and site permissions.

EdgeReview Chromium privacy settings, managed policies, Secure DNS, and VPN split tunneling.

FirefoxReview Enhanced Tracking Protection, DNS over HTTPS, and advanced WebRTC preferences when appropriate.

BraveReview Shields, fingerprinting protections, and WebRTC IP handling policy.

SafariReview website permissions, iCloud Private Relay context, and operating-system privacy settings.

iOSRetest after VPN profile, relay, mobile data, or Wi-Fi changes. Browser controls may be limited.

AndroidReview per-app VPN, Private DNS, browser permissions, and Wi-Fi versus mobile data behavior.

WindowsReview VPN adapter DNS, split tunneling, IPv6, browser Secure DNS, and firewall/proxy rules.

macOSReview VPN profile order, DNS settings, iCloud Private Relay context, and browser-specific privacy controls.

Public Exposure ReportDefault next step for a combined route map and Safe Privacy Receipt. Is My VPN Working?Before/after VPN workflow for visible browser/session signals. What Websites Can See About MePlain-language map of signals websites may read from this browser/session. Check My Browser PrivacyFocused path for fingerprint, WebRTC, IPv6, User-Agent, and browser settings.

Check my browser/privacy

What this checks

Visible browser/session signals such as public route, DNS/WebRTC/IPv6 behavior, fingerprint traits, user-agent, or public IP context.

Limits

What this cannot check

It cannot certify anonymity, inspect every app, or prove that a VPN, ISP, device, or account is safe.

Read results

How to use the output

Treat results as review signals for this browser/session or public target. Re-test after one change, then use Safe Copy or notes that avoid raw identifiers.