No KYC — no ID, no selfie, no documents · Pay in crypto: BTC, USDT, USDC, ETH, SOL, LTC
Buy with crypto

Guide · 6 steps

Quick start: your first request through Nameless Proxy

From account number to a working proxied request, with the username syntax, both ports, sticky sessions and a troubleshooting table.

Last updated: · 7 min read

Quick answer

How do I set up Nameless Proxy?

Nameless Proxy, a privacy-first, no-KYC proxy provider, takes a few minutes to set up: create a random 16-digit account number, top up your balance in crypto (minimum $25) and buy a plan from it, copy your proxy username and password, and send traffic to gw.namelessproxy.com on port 7777 for HTTP(S) or 7778 for SOCKS5. Country, city and session go in the username. No KYC — no ID, no selfie, no documents.

Connection details

Gateway hostgw.namelessproxy.com
HTTP and HTTPS port7777
SOCKS5 port7778
Username formatUSERNAME-country-{cc}-city-{city}-session-{id}-ttl-{minutes}
AuthenticationUsername and password, or IP whitelist
Sticky sessionsSame session ID keeps the same IP, for up to 60 minutes
BillingDecimal GB: 1 GB = 1,000,000,000 bytes
Top-upIn crypto (BTC, USDT, USDC, ETH, SOL, LTC). Minimum top-up $25; unused balance stays on your account (never expires, non-refundable)
Smallest purchase1 GB for $1.88, bought from your balance — paid from a $25 minimum top-up; the rest stays on your balance (never expires, non-refundable)

How to make your first request

  1. Create an account

    Click sign-up and save the random 16-digit account number: it is your login. Email, password and 2FA are optional.

  2. Top up your balance in crypto

    In the client area, top up your balance in any accepted coin (BTC, USDT, USDC, ETH, SOL, LTC); the minimum top-up is $25. The top-up is credited after the network confirmations shown on the top-up screen, and unused balance stays on your account (never expires, non-refundable).

  3. Buy a plan from the balance

    Choose a plan on the pricing page, for example the 1 GB test at $1.88, and buy it from your balance (the minimum top-up is $25; the rest stays on your balance, never expires, non-refundable). Purchases are instant, so your credentials appear right away.

  4. Copy your credentials

    Open the residential subscription in the client area. Copy the base proxy username, the proxy password and the endpoint. The proxy password is not your account password.

  5. Add targeting

    Append the country to the username, for example USERNAME-country-ae for the United Arab Emirates.

  6. Send a request

    Run the curl command below. The response is your exit IP.

First request over HTTP(S)
# Rotating residential IP in the UAE, over HTTP(S)
curl -x "http://USERNAME-country-ae:[email protected]:7777" \
     https://api.ipify.org

What is the proxy username syntax?

The username carries all targeting, in this order: USERNAME-country-{cc}-city-{city}-session-{id}-ttl-{minutes}. Stop after the country or the city for a rotating IP, which changes with each new connection. Add a session and a TTL after the city for a sticky IP.

PartExampleWhat it does
USERNAMEu7k2m9Your base proxy username, shown in the client area
country-{cc}country-aeExit country: two-letter ISO code, lower case
city-{city}city-abu_dhabiExit city: lower case, _ instead of spaces, no hyphens. The client area lists the cities in stock per country
session-{id}session-a1b2c3Keeps the same exit IP for every request with this ID. Use a short ID of letters and digits
ttl-{minutes}ttl-30How long, in minutes, the sticky IP is held. Sessions last for up to 60 minutes

HTTP or SOCKS5: which port should I use?

Use port 7777 for web traffic and browsers, and port 7778 for SOCKS5 clients. The HTTP port also carries HTTPS: the client opens a CONNECT tunnel, so the proxy sees the destination host and port but not the encrypted content (RFC 9110).

With SOCKS5, use --socks5-hostname in curl or socks5h:// in code, so DNS is resolved at the proxy and lookups also exit in the target country. SOCKS5 sends the username and password in cleartext (RFC 1929), so prefer HTTPS targets.

Same request over SOCKS5
# Same request over SOCKS5; --socks5-hostname lets the proxy resolve DNS
curl --socks5-hostname "gw.namelessproxy.com:7778" \
     --proxy-user "USERNAME-country-ae:PASSWORD" \
     https://api.ipify.org
Tools that read HTTP_PROXY and HTTPS_PROXY
# Many tools read the standard proxy variables
export HTTP_PROXY="http://USERNAME-country-ng:[email protected]:7777"
export HTTPS_PROXY="$HTTP_PROXY"
curl -s https://api.ipify.org

How do I keep the same IP between requests?

Add a session ID and a TTL after the city. Every request with the same session ID exits from the same IP until the TTL ends. A new ID gives a new IP. A residential device can still go offline before the TTL ends, so make your code accept a change of IP.

Sticky session in Dubai, then a location check
# Sticky session: same session ID = same exit IP while the TTL lasts
PROXY="http://USERNAME-country-ae-city-dubai-session-a1b2c3-ttl-30:[email protected]:7777"
for i in 1 2 3; do
  curl -s -x "$PROXY" https://api.ipify.org; echo
done

# Check where the exit IP is located
curl -s -x "$PROXY" https://ipinfo.io/json

Can I use IP whitelisting instead of a password?

Yes. In the client area, add your server's public IP: an IPv4 address or range from /24 to /32, or an IPv6 address or range from /48 to /128. Private and reserved ranges are refused, and a new entry works at the gateway within 60 seconds. This guide uses username and password because the targeting examples live in the username.

Why is my request failing?

Most first-run problems come from credentials, ports or targeting. Check this table before you open a ticket.

SymptomLikely causeFix
407 Proxy Authentication RequiredWrong username or password, or a typo in a targeting partCopy the credentials again. Keep the order country, city, session, ttl. URL-encode special characters in the password
Timeout or connection refusedHTTP sent to the SOCKS5 port (or the reverse), or a firewall blocks outgoing trafficUse 7777 for http:// and 7778 for SOCKS5. Allow outgoing TCP to both ports
Wrong countryNo country- part, or the IP checker's database disagreesAdd country-{cc}. Compare two checkers: geolocation databases differ
Local DNS results over SOCKS5DNS resolved on your machineUse --socks5-hostname or socks5h://
Worked, then every request failsTraffic used up (subscription depleted)Check traffic left in the client area and add a pack
One site always refusedBlocked category: banking, payment or government portals, SMTPNot available. See the Acceptable Use Policy

Frequently asked questions

What is the difference between my account number and my proxy password?

The 16-digit account number logs you in to the client area. The proxy username and password only authenticate traffic at the gateway, so sharing them gives no access to your account or balance. If they leak, reset the proxy password; the old one stops working within 60 seconds.

Can I give each project separate proxy credentials?

Yes. Each residential subscription can have sub-users, each with its own username, password and optional traffic cap. Give one to each project or teammate and disable it when the work ends. Daily usage is reported per sub-user, so you can see which project spent the traffic.

How long does a sticky session keep the same IP?

Sticky sessions last for up to 60 minutes; set the length with the ttl- part, in minutes. The IP can change earlier if the residential device goes offline, so start a new session ID when that happens. For an IP that stays for days, rent a dedicated 4G/5G port.

Which service should I use to check my exit IP?

https://api.ipify.org returns only the IP, which suits scripts. https://ipinfo.io/json adds the country and city, which helps to confirm targeting. Geolocation databases do not always agree, so a city can appear as a nearby town. Check the country first.

Does this guide work for dedicated mobile ports?

Partly. A dedicated 4G/5G port has its own endpoint, username and password, shown for that port in the client area; the curl commands work the same with them. Its country and carrier are chosen when you rent it. To change its IP, see the mobile IP rotation guide.

Do I need to URL-encode my proxy password?

Only if it contains characters with a meaning in URLs, such as @, :, / or #. Encode it before you put it in a proxy URL, for example with urllib.parse.quote(password, safe="") in Python. Options that take the credentials separately, like curl's --proxy-user, avoid the issue.

Sources (2)
  1. RFC 9110, HTTP Semantics, section 9.3.6 CONNECT — RFC Editor (2026-10-05)
  2. RFC 1929, Username/Password Authentication for SOCKS V5 — RFC Editor (2026-10-05)

Start with a 1 GB test

1 GB for $1.88 from your crypto balance. Minimum top-up $25; unused balance stays on your account (never expires, non-refundable). No KYC — no ID, no selfie, no documents.

From $0.53/GB · no KYC

Buy proxies