Achieving 100% on iphey.com with Afina — Step-by-Step

iphey.com is the dashboard the rest of the industry secretly uses to grade anti-detect browsers. Full green across all sections is the public score every vendor would love to show — and few can.

This is the exact procedure to hit 100% in Afina.

What "100%" requires

iphey runs a series of checks grouped as:

1. IP / Proxy — IP type (residential vs DC), country, IP-vs-Tor, ASN class
2. WebRTC — STUN-revealed IP, local IPs, mDNS leaks
3. DNS — resolver country, DoH detection, DNS leak
4. HTTP / HTTPS — header consistency, cipher suites
5. Time — system clock vs timezone vs IP
6. Browser — UA-CH consistency, plugins, language
7. Fingerprint — Canvas, WebGL, Audio, Fonts, ClientRects

Each section yields Trustworthy / Suspicious / Risky badges. 100% = all Trustworthy.

Step 1 — Pick a real residential proxy

Datacenter proxies fail the IP/Proxy section immediately ("Datacenter IP" → Risky). You need residential or mobile with an ISP-class ASN.

• Test the proxy at ipinfo.io — "type" should be "isp" (mobile) or "broadband" (residential).
• Country should match what you'll claim. iphey checks IP country vs claimed locale.

If your proxy provider is questionable, see our proxy provider guide.

Step 2 — Create the profile with IP alignment

In Afina:

1. New profile → assign the proxy
2. Click "Align fingerprint to IP"
3. Pick a device profile (Windows 11 / Chrome 132 is the safest default)
4. Confirm timezone, locale, language match the proxy country

Afina pre-fills these. If you override anything, do it consistently — change timezone and locale together.

Step 3 — Verify UDP routing

The single most common reason for losing 100% is a WebRTC leak. Open a test profile, load browserleaks.com/webrtc:

• Public IP — should match the proxy IP
• Local IP — should be hidden or randomised
• No mDNS .local leaks

If anything fails, your anti-detect doesn't support UDP properly. Afina handles this with native SOCKS5-UDP / WireGuard.

Step 4 — Load iphey.com

Open iphey.com from the profile. Expect:

• IP — Trustworthy (residential, country match)
• WebRTC — Trustworthy (tunnel, no leaks)
• DNS — Trustworthy (proxy country resolver)
• HTTP — Trustworthy (UA-CH matches UA)
• Time — Trustworthy (TZ matches IP)
• Browser — Trustworthy (full client hints)
• Fingerprint — Trustworthy (consistent, plausible)

All green = 100%.

Common failures and fixes

"WebRTC IP doesn't match HTTP IP"

Your proxy doesn't tunnel UDP. Switch to Afina + a proxy with SOCKS5-UDP, or enable Afina's embedded WireGuard.

"DNS country differs from IP country"

Your proxy uses a global DNS (like 1.1.1.1) that resolves from a non-matching location. Use Afina's "proxy DNS" toggle to force the proxy itself to resolve.

"Timezone differs from IP"

You haven't aligned. Open profile settings, set timezone to match the proxy country.

"Suspicious user agent"

You set a UA-CH override but didn't update navigator.userAgent. In Afina, use the device-profile selector instead of editing UA strings manually.

Why iphey, specifically

There are other test pages — pixelscan, whoer, browserleaks — but iphey's value is the categorical grading. It tells you exactly which signal is wrong, not just whether you "look like a bot." For diagnosing a leaking profile, iphey is the fastest path.

When all sections are Trustworthy, you have a baseline-good profile. Beating real anti-bot systems on top requires behaviour (Scenarios) and clean IP history.

Bottom line

100% on iphey is achievable in under 5 minutes with the right tool and proxy. Most anti-detects can get 80–90%; the last 10% requires UDP support, IP-aligned injection, and per-region font sets — which is why we rank Afina #1.