Skip to main content
All Proxies.fo endpoints use user : password authentication over HTTP, HTTPS, and SOCKS5. Targeting is controlled by modifiers appended to your username — no API, no config file, no SDK.

​
Credential format

Your base username and password live in the dashboard. Modifiers are optional — without them, the network picks an IP at random from the pool for whichever regional gateway you connected to.

​
Real-world examples

Residential — targeting Westlake Village:
Residential — targeting AT&T (ASN 7018):
Mobile — US carrier IP:
Datacenter — sticky session for 300 seconds:
Shared ISP — rotating:

​
Modifier reference

Residential and Mobile use ttl-<minutes>. Datacenter uses duration-<seconds>. Don’t mix them — passing ttl- to a DC endpoint or duration- to residential is ignored or rejected. Mobile does not support state- or city- — only country- and asn- for carrier targeting. Datacenter does not support country / state / city / ASN — the regional endpoint determines geography. Dedicated ISP uses static assigned IPs, so no targeting modifiers apply. Shared ISP uses session- and ttl- for sticky rotation but doesn’t take geo modifiers — region is set by which endpoint (pr-us or pr-eu) you connect to.

​
Plan-based routing

Residential, Mobile, and Shared ISP all connect to the same gateway hostnames (pr-us.proxies.fo, pr-eu.proxies.fo, plus pr-sg.proxies.fo for residential only) on port 13337. Your plan type determines which pool serves your request — there’s no port switch or product modifier. A username with a residential plan exits through residential IPs. A mobile plan username exits through mobile IPs. Same endpoint, different pools.

​
Targeting granularity (residential)

​
ASN targeting

asn-<number> pins your IP to a specific ISP (residential) or carrier (mobile) by Autonomous System Number. Common US ASNs: Find the ASN for any IP using whois, bgp.he.net, or ipinfo.io.

​
Session IDs

Use alphanumeric strings, 6–16 characters. Same ID = same IP. Good examples: 5s5d4xud, bot-nyc-01, a4f8c2e1 Avoid:
  • Spaces or special characters ($, @, :, /) — these break URL parsing
  • Sequential IDs (session-1, session-2) if you want session isolation
  • Reusing IDs across unrelated workflows

​
Protocols

​
Rotating credentials

If credentials leak, rotate from the dashboard under Account → Security. Existing sessions drop within 60 seconds. Never commit credentials to version control.