SOCKS5 configuration guide
Configure a SOCKS5 dedicated static residential endpoint in axios: exact syntax, authentication, DNS handling, and verification.
Quick answer
Point axios at socks5://host:port with your NobleProxy username and password, prefer the hostname (remote DNS) form, and verify the exit IP with an echo request.
Configure a SOCKS5 dedicated static residential endpoint in axios: exact syntax, authentication, DNS handling, and verification.
Point axios at socks5://host:port with your NobleProxy username and password, prefer the hostname (remote DNS) form, and verify the exit IP with an echo request.
axios runs in Node: pass a socks-proxy-agent instance as httpsAgent with the endpoint URL..
Use the hostname form (socks5h in libraries that distinguish) so DNS resolves at the endpoint.
Fetch an IP echo URL through the tool and confirm the endpoint address.
Keep the mapping stable so session history accumulates on one identity.
Facts last reviewed 2026-09-01.
SOCKS5 carries the handshake credentials and (in the hostname form) resolves DNS at the endpoint, so both traffic and lookups stay on one identity. Static residential endpoints keep that identity stable across runs.
Yes - credentials are part of the SOCKS5 URL or the tool's dedicated auth option. If a 407 or handshake error appears, re-check the credential order and encoding.
Buy self-serve now, or talk with us about a larger agency inventory.