Afina

Download app

AppleWindows
EN

Proxy manager for the Afina antidetect browser

Built-in proxy manager with per-profile assignment, HTTP / SOCKS5 / UDP-over-SOCKS5 support, bulk health checks and anti-leak by default. Geo-aware routing keeps every account in the right region.

Proxy manager for the Afina antidetect browser
HTTP • SOCKS5 • UDP-over-SOCKS5

Right proxy, right account, every time

Multi-account ops live or die by proxies. Afina stores them once, attaches them per profile, validates them in bulk and watches for IP/timezone/language drift against the profile fingerprint — so a stale proxy never quietly kills a campaign.

Per-profile proxy assignment

Attach a proxy to a single profile, group or whole batch. Inline proxy data, saved proxy from your library, or no-proxy mode — toggled per profile in one click.

HTTP / SOCKS5 / UDP-over-SOCKS5

Standard HTTP and SOCKS5, plus UDP-over-SOCKS5 for QUIC and HTTP/3. Latest multi-accounting platforms increasingly use UDP — most antidetect browsers can't.

Bulk health checks

Check 500 proxies at once, with UDP probing for SOCKS5. Failed proxies surface immediately with reason codes; healthy ones populate a per-account proxy_usage cache for fast attachment in RPA task groups.

Anti-leak by default

WebRTC and DNS leaks are blocked at the network layer. Country/timezone drift triggers an optional block via the per-profile antidetect guards.

FAQs

HTTP, HTTPS, SOCKS5 and SOCKS5 with UDP relay for QUIC/HTTP/3 (a.k.a. UDP-over-SOCKS5). Authentication via username/password or IP whitelist — set per proxy.

Modern browsers route HTTP/3 over QUIC, which is UDP. SOCKS5 by default proxies TCP only; UDP-over-SOCKS5 forwards UDP too. Without it, a QUIC-enabled site sees your real IP for HTTP/3 traffic — a major leak on ad and social platforms.

Yes — POST /api/proxies/check-all runs concurrent health checks across your whole proxy pool (or a filtered subset). Each proxy reports latency, exit IP, geo and protocol-specific tests (UDP probe for SOCKS5). Failed ones surface with reason codes.

An internal cache that records which profile last used which proxy, when, and what country it resolved to. Used to suppress drift (country/timezone mismatch with fingerprint) and to attach the same proxy consistently across reruns.

No. WebRTC is locked to the proxy's exit IP; DNS resolution goes through the proxy (or via DoH if configured). Both can be tested with standard checkers — see the IP/WebRTC test inside the desktop UI.

Yes, but the more profiles share a proxy the more correlated they look. Afina lets you attach by reference (proxyId) or inline (proxyData) per profile, and groups them in the library so you can pool by use-case (e.g. 'facebook-ads').

Stop chasing dead proxies — manage them once

Add, attach, bulk-check and roll proxies for hundreds of profiles from one place.

Proxy manager — HTTP, SOCKS5, UDP-over-SOCKS5 | Afina