How proxies work in Argus
A profile is only as believable as the address it browses from. This page follows one request end to end: the library the proxy lives in, the health check that clears it, and the two leaks — SOCKS5 auth and WebRTC — that Argus closes inside the browser itself.
On this page
Why every profile brings its own proxy
Websites read two things about a visitor before anything else: the device the session presents and the network address it arrives from. Argus builds the device half with coherent fingerprints; the proxy is the network half. A profile that logs in from Warsaw today and Buenos Aires tomorrow contradicts itself — so in Argus the proxy is part of the profile's identity, assigned once and applied at the network layer on every launch, not an extension a page can detect or a global setting the whole office shares.
When you create a profile, one dialog sets the whole arrangement: an assigned proxy from your library, a direct connection, or the free option for throwaway work. The preview rail shows exactly what will be stored before you save.
A library, not a text field
Most tools store a proxy as a string pasted into each profile — which is how an agency ends up with the same credentials copied into forty rows and no idea which of them still work. A shared, searchable proxy library with live health checks — not a text field per profile.
- ✓HTTP and SOCKS5, including SOCKS5 that requires a username and password
- ✓Health checks report egress IP, country, and latency
- ✓Checks run automatically for new or failing proxies, concurrently rather than one at a time
- ✓Any proxy can also be re-checked on demand
- ✓A proxy that fails its check blocks the launch instead of leaking your real IP
- ✓CSV bulk import
Because the library syncs to your organization, a proxy added by one teammate is immediately assignable by every other — and your own tooling can manage the pool too, through the local automation API: create, update and delete proxies, or assign one to a profile, from a script or an agent.
Health checks, and launches that fail closed
Every proxy in the library is checked against the live network: the check reports the egress IP a website will actually see, the country that IP resolves to, and the latency of the hop. Checks run automatically for new and failing proxies — concurrently, so a big import doesn't queue for an hour — and any proxy can be re-checked on demand before an important session.
The rule that matters most is what happens when a check fails: a proxy that fails its check blocks the launch. The session simply does not open, instead of quietly falling back to your real connection and stamping your office IP onto an account that has never seen it. A tool that fails open there has already cost you the account.
Authenticated SOCKS5, handled inside the browser
The clearest reason Argus ships its own browser instead of automating someone else's. Chromium — the engine under nearly every anti-detect tool — only speaks the no-auth variant of SOCKS5, so a proxy that requires a username and password cannot be used with it at all. Argus ships its own build of the browser, and closes this there:
- ✓Chromium's own SOCKS5 client only speaks the no-auth variant, so a proxy that needs a username and password simply cannot be used
- ✓Argus runs a local relay that performs the RFC 1929 handshake on the upstream leg
- ✓The profile is pointed at a loopback address, so no proxy authentication dialog ever appears
- ✓This is not a workaround layered on top — it lives inside the browser process
WebRTC cannot leak around it
A proxy only covers the traffic that goes through it. WebRTC is the classic way around one: a page asks the browser to negotiate a peer connection and reads your real address out of the candidates, proxy or no proxy. Your real address does not escape through WebRTC, and a page cannot switch that off.
- ✓Enforced as browser policy on the profile, beneath the JavaScript layer
- ✓Applied to every profile — it is not a toggle you can forget to set
- ✓Assigning a proxy to a profile that was still reporting its real address upgrades it automatically
Bring proxies from any provider
Argus does not sell proxies and is not tied to anyone who does. Any HTTP or SOCKS5 endpoint works — residential, datacenter or mobile, from whichever provider your team already pays. Import them one at a time or as a CSV, and the health check tells you what you actually bought.
See it with your own proxies
Download the launcher, import your pool, and watch the health checks come back.