Anonymity score for this browser
This check grades what your browser’s request tells a website: proxy headers, the User-Agent, language and Accept settings, and whether your IP belongs to a hosting provider. Run it before competitor research or ad reviews, where sites should see the proxy’s location rather than your office network.
For the browser side, add the DNS leak test and WebRTC leak test.
Findings
Proxy headers present
Your request carried X-REAL-IP. They tell the site the visit came through a proxy, and many sites handle such requests differently.
Browser-style User-Agent
The User-Agent reads like an ordinary desktop or mobile browser.
Accept-Language present
Your browser asks sites for content in: en-US,en;q=0.5
Detailed Accept header
The request lists content types the way a browser does.
Where the points go
Every request starts at 100. Points come off for each sign that the visit is relayed or automated:
- -30 for proxy headers (Via, X-Forwarded-For and similar) in the request.
- -25 for a User-Agent that belongs to a script or command-line tool (curl, wget, python-requests and the like).
- -20 if your IP’s reverse DNS names a data-centre or cloud operator such as AWS, GCP or OVH.
- -20 for a request with no User-Agent at all.
- -10 when the browser states no language preference (Accept-Language).
- -8 for an Accept header that is empty or only says
*/*.
Expect 95-100 from an everyday browser at home or in the office. A basic Python script left on its defaults, such as an in-house price monitor, typically gets 30-50. Give that tool a browser User-Agent and full headers, run it on our residential proxies, and the score reaches 90+.
What the score can’t see
We calculate the score server-side, using only the request, so four things stay out of view:
- WebRTC leaks - your office or home IP exposed through the browser’s calling features. Check with our WebRTC leak test.
- Leaking DNS lookups - name lookups that leave over your own connection instead of the proxy. Check with our DNS leak test.
- Fingerprints from canvas, fonts and hardware - details that scripts collect inside the page. See yours in our browser fingerprint tool.
- Behaviour on the page - how a visitor scrolls, clicks and paces requests, which many sites also weigh up.
Getting a team setup above 90
A sensible order to work through:
- Use residential or mobile IPs for sites that handle hosting ranges strictly. Datacenter addresses still suit plenty of other tasks.
- Make sure automated tools identify as a current version of Chrome, Safari or Firefox rather than keeping their built-in User-Agent.
- Set Accept and Accept-Language to match the market you are checking. Copying them from an ordinary browser request is the simplest way.
- Choose a proxy that leaves Via and X-Forwarded-For out of your requests; ours run at the elite level and add neither header.
- If your team keeps several client accounts in separate browser profiles, multi-profile browsers (Multilogin, Dolphin Anty, GoLogin and others) keep audio, canvas, font and WebRTC settings separate for each profile. Use them within each platform’s terms.
