Whoer IP: How to Check Your IP, WebRTC, and Browser Fingerprint

Whoer displays the IP address, network leaks, and browser signals that websites use to assess whether a digital profile is consistent. People use it to test a proxy or VPN and spot conflicts between geolocation, DNS, WebRTC, language, and timezone. A high percentage score alone proves very little. What matters is whether the reported values form a plausible configuration.

For a quick second opinion, open the Afina fingerprint check inside the same profile you plan to use. Do not switch proxies between the test and the first login. If you do, the checker no longer describes the working session.

What Is Whoer and Why Should You Check Your IP and Anonymity?

Whoer is a web-based checker that reports your public IP address, approximate location, provider, ASN, and a set of browser signals. It does not make the connection more private. Its job is diagnostic: it shows what an ordinary website can observe during the current session.

An IP check answers one narrow question about the network exit point. The extended report goes further by comparing network data with browser settings, including the browser User-Agent. Suppose the IP belongs to an ISP in Canada while JavaScript returns a European timezone and a locale that is unusual for that region. This may not expose the original IP, but the profile looks manually assembled.

That is why a checker is useful before the first login, after replacing a proxy, and after changing the browser core. For repeat tests, open the same page in the same profile and note which value changed. Otherwise, you can spend an hour fixing a random symptom.

Our guide to how browser fingerprint checkers work explains the wider context. Treat Whoer as one diagnostic view, not a universal verdict for every website.

What Data Does a Whoer IP Report Show?

A Whoer report combines network and browser signals. Check the IP, country, ISP, and ASN first. Then inspect DNS and WebRTC before moving to User-Agent, language, time, and device parameters. This order separates routing leaks from fingerprint configuration errors.

Start with two basic comparisons. The visible address should belong to the proxy you connected, and its country should match the profile's purpose. Then compare the HTTP User-Agent header with navigator.userAgent; the two values should not contradict each other.

Do not try to make every value rare. Rarity is not the same as realism. A common Chrome and operating system combination with a plausible screen often attracts less attention than an exotic setup barely represented among real devices.

How Is an IP Check Different From a Browser Fingerprint Check?

An IP check describes the session's network address, while a browser fingerprint describes the browser and device. Changing an IP does not change Canvas, WebGL, fonts, screen size, processor count, memory, or stored cookies.

A fingerprint is not one magical hash. A website reads dozens of available values and compares them. Two sessions may use different IPs yet expose the same Canvas output, screen, WebGL renderer, and font set. That creates a strong link. The reverse can also be suspicious: a fingerprint that changes at every launch does not behave like an ordinary laptop.

A stable profile has two useful properties: internal consistency and repeatability. If a browser claims to be Windows 11 with Chrome today, then shows another OS, graphics card, and CPU count tomorrow, cookies will not explain the jump. Changes should have a normal cause, such as a planned browser update.

Why Does Whoer Show Your Real IP or a Low Score?

A real IP in Whoer usually means some traffic bypassed the intended route. A low score can also appear without a direct leak when the service finds conflicts among IP, DNS, WebRTC, or system settings.

Check the common causes in a fixed order:

1. Stop other VPNs and proxy extensions. Multiple network layers can intercept different requests and create a mixed report
2. Test the proxy separately. Confirm the address, port, protocol, credentials, and sticky-session lifetime
3. Open the WebRTC test. If its public address differs from the proxy, check UDP routing or disable WebRTC when the target site does not need it
4. Run a DNS leak test. A home ISP resolver behind a foreign IP suggests that DNS bypassed the intended route
5. Compare time and locale. Timezone, system time, and language should make sense for the profile's location
6. Restart the profile. Some network and browser parameters apply only at launch

Inspect a possible WebRTC leak separately. WebRTC creates ICE candidates for direct communication and may use UDP outside the path taken by ordinary HTTP requests. If a proxy cannot carry that route, a checker may observe an address from another interface.

DNS leaves a different trace. The page can load through a proxy while domain lookups use the operating system's normal connection. A DNS leak test should show a resolver compatible with the current route. The mere presence of a third-party DNS provider is not automatically a leak.

Which Whoer Warnings Should You Fix First?

Fix signals that directly expose another network route first: a public WebRTC address, a home ISP resolver, or IPv6 traffic outside the proxy. They matter more than a minor locale mismatch or a disappointing overall percentage.

Move to identity conflicts next. When an HTTP header reports one browser version and JavaScript reports another, inspect extensions, an old User-Agent override, and the selected browser core. Treat OS, GPU, and WebGL renderer as a group. Changing the renderer alone can make the combination less realistic.

Repair the score last. Two checkers can rate the same profile differently because their IP databases and scoring rules differ. A stable profile without an obvious leak is more useful than a constantly changing setup that gained five percentage points.

Keep a short test log with the date, IP, ASN, browser-core version, and warnings. If a later update causes trouble, comparing two records shows which layer changed. Without that note, troubleshooting quickly becomes guesswork.

How Should You Test a Profile in Whoer and Other Checkers?

Profile checking should be a short, repeatable procedure. Use one tool for network signals and a second for detailed fingerprint data, then compare the basics. Running ten checkers until every badge turns green is poor troubleshooting because each service has a different database and scoring model.

Use this sequence:

1. Create the profile with the intended OS, browser version, and screen size
2. Assign the proxy and verify connectivity before launching the browser
3. Open Whoer in that profile and record the IP, ISP, ASN, DNS, and WebRTC results
4. Compare browser signals with profile settings, especially User-Agent, platform, language, and time
5. Open a second fingerprint checker and compare Canvas, WebGL, Audio, and ClientRects
6. Fix one mismatch and retest after a complete profile restart
7. Save the configuration and avoid changing it without a reason after the first working session

A warning from one checker does not prove that a profile will be blocked. A green report proves even less. Checkers cannot see account history, cookie quality, action speed, repeated automation patterns, or the IP reputation held by a particular platform.

How Do You Align a Proxy, Timezone, Language, and WebRTC?

A consistent fingerprint starts with the network exit. Choose a stable proxy for the intended location first, then configure timezone, language, and WebRTC behavior around it. Randomizing every browser value before selecting an IP creates needless contradictions.

Long sessions usually benefit from a sticky IP. Rotating the address in the middle of an authenticated session changes the network identity while cookies and the browser fingerprint stay fixed. Mobile and residential labels do not guarantee a clean route either. Check ASN, location, stability, and whether the exact proxy carries UDP when required.

Use the IP location to select a timezone, but do not treat a timezone as an exact address. One zone may cover several regions. Pick a browser locale that a real user in that market could plausibly use. Timezone spoofing works only when the zone, system clock, and locale remain consistent.

How Does Afina Help Diagnose and Fix Whoer Results?

Afina isolates every account in a separate Chromium profile with its own cookies, cache, proxy, and fingerprint settings. You can configure User-Agent, browser core, timezone, languages, CPU, RAM, and noise for Canvas, WebGL, and Audio. This makes it possible to fix one conflict found in a report without regenerating the entire profile.

A proxy is assigned per profile and can be checked for connectivity, type, and location before launch. If Whoer still reports an unexpected IP or WebRTC value, the cause is narrowed to the route or protocol support instead of getting lost among system-wide settings.

Build one reference profile, test it, reuse the configuration logic for a group, and vary only the values that need to differ. This material is provided for informational and educational purposes only.

Afina reduces technical contradictions, but it cannot predict every site's policy or guarantee an account outcome. Behavioral signals, session history, and IP reputation still matter. The antidetect and anonymity overview explains the limits of this model in more detail.

Download