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.

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

Have questions? We're here to help.

Online Support Available

Telegram Discord

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.

The Afina proxy manager attaches a dedicated proxy to every profile and supports the modern stack: HTTP, SOCKS5, SOCKS5 with UDP relay for QUIC / HTTP/3, residential, datacenter, mobile and ISP. Bulk-check thousands at once, rotate by group, and stop WebRTC / DNS leaks at the browser level — paired with fingerprint management for an end-to-end antidetect profile.

System-wide proxies leak through WebRTC's ICE candidates and through alternate DNS paths. Browser extensions that set proxies don't isolate per-profile and don't survive QUIC traffic. Afina binds the proxy inside Chromium per profile, intercepts WebRTC at the engine level, routes DNS through the proxy and exposes the result to your scripts and to the local API.

What's inside the proxy manager

1. All major protocols, including UDP-over-SOCKS5

HTTP, HTTPS, SOCKS4, SOCKS5 with authentication. SOCKS5 with UDP relay carries QUIC and HTTP/3 traffic — most antidetect browsers can't, and modern sites increasingly require it.

2. Geo coverage from any provider

Bring your own proxies from Bright Data, Oxylabs, Smartproxy, IPRoyal, Proxywing or any other vendor — Afina is provider-agnostic. The partners page lists discounts our customers actually use.

3. Anti-leak at the Chromium layer

WebRTC ICE candidates restricted to the proxy interface, DNS routed through the proxy by default, no localhost / private-network leaks. The same setup that lets Afina pass fingerprint and leak checkers on every layer.

4. Bulk health checks

Validate hundreds of proxies in parallel — latency, country geo, ISP, blacklist hits, IPv6 reachability. Bad proxies are quarantined before they wreck a multi-account run.

5. Per-profile, per-group or pooled

Assign one proxy per profile for tight cluster isolation, share a sticky proxy across an account group for warm sessions, or use a rotating pool for scraping. Each pattern is one config switch in the profile.

Where the proxy manager fits in

Multi-accounting on Meta, TikTok and Google requires real residential or ISP IPs per profile — pooling is the fastest way to get every account banned together. Web scraping needs rotating residential at scale. QUIC / HTTP/3 targets require the UDP-over-SOCKS5 path. Geo-locked content and price-checking on travel / e-commerce sites work only with country-pinned IPs. Afina supports every pattern out of the box.