What Is a Proxy Address? Proxy IP, Port, and Login

A proxy address is the connection information your browser, bot, script, or operating system uses to send traffic through a proxy server. It always includes a host, which is a proxy IP address or a hostname, and a port. Private proxies usually add a username and password.

Example: proxy.example.com:12345 or 192.0.2.10:8080. The part before the colon is the proxy server address. The number after it is the port.

Two terms cause most of the confusion:

• The proxy server address is where your app connects. Your provider, employer, or network gives it to you.
• The exit IP is the address websites see after the proxy forwards your request. With a rotating gateway, one proxy address can lead to many exit IPs.

Most setup problems come from putting the host, port, protocol, username, and password in the wrong format for the tool.

Proxy address quick example

A full proxy URL can look like this:

http://username:password@proxy.example.com:12345

That breaks down into:

Many tools do not want the full URL. They ask for the same information in separate fields.

Host: proxy.example.com
Port: 12345
Username: username
Password: password
Protocol: HTTP

The parts are the same. Only the format changes.

Proxy IP address, hostname, and gateway

The host is the proxy server address your tool connects to. It can be a hostname:

proxy.example.com

Or a direct proxy IP address:

192.0.2.10

With many residential and rotating proxy services, the host is a gateway. You connect to one hostname, authenticate with your account, and the provider routes your request through an exit IP from the selected pool. With static ISP or datacenter proxies, the host may map more directly to a specific proxy server or assigned IP.

Do not assume the host is always the final exit IP. For rotating pools, the host is often just the entry point. A common mistake is pasting the exit IP you saw on an IP checker into the host field. The gateway will not accept connections there, because that IP is the far end of the tunnel, not the door into it.

What the port does

The port tells your app which service to connect to on the proxy host.

Example:

proxy.example.com:12345

Here, 12345 is the port. Providers often use different ports for different products, protocols, or rotation modes.

Common reasons the port matters:

• HTTP and SOCKS may use different ports.
• Residential and ISP products may use different ports.
• Sticky and rotating sessions may use different ports.
• Some providers assign one port per proxy.
• Some tools silently fail when the port is missing or not numeric.

If the host is correct but the port is wrong, you may see connection timeouts, authentication failures, or a proxy checker result that says the proxy is dead. In Chrome that often shows up as ERR_PROXY_CONNECTION_FAILED.

Common proxy port numbers

Paid proxy services usually hand out their own port numbers, so treat this list as a guide for self-hosted and corporate proxies, not a rule.

If a tool asks for a port and you were only given a hostname, do not guess one of these. Check the dashboard or ask whoever issued the proxy.

Username and password

Private proxies usually require authentication. The username and password prove that your account is allowed to use the proxy.

In simple setups, the username is just an account username:

customer123

In more advanced residential proxy setups, the username can include routing options:

customer123-country-us-session-profile1

Those extra parts can tell the provider to use a country, state, city, sticky session, rotating session, or zone. The exact syntax depends on the provider.

Keep two rules in mind:

1. Use the plain credentials first to confirm the proxy works.
2. Add location and session parameters only after the basic connection succeeds.

A wrong or missing login usually returns 407 Proxy Authentication Required. If the failure shows up inside a Windows app, read proxy authentication error 2606 for a deeper troubleshooting checklist.

Common proxy address formats

Different tools expect different formats.

Host, port, user, pass

This is common in bot imports and proxy lists:

host:port:username:password

Example:

proxy.example.com:12345:user123:pass456

If your tool wants a different layout, the proxy converter rewrites a whole list between host:port:user:pass, URL, and other common formats.

URL format

This is common in code, cURL, environment variables, and some browser tools:

http://username:password@host:port

Example:

http://user123:pass456@proxy.example.com:12345

If the password contains @, :, or /, percent-encode those characters in the URL form (@ becomes %40, : becomes %3A). Otherwise the tool splits the string in the wrong place.

Separate fields

This is common in anti-detect browsers, profile managers, and desktop apps:

Protocol: HTTP
Host: proxy.example.com
Port: 12345
Username: user123
Password: pass456

No username or password

Some proxies use IP allowlisting instead of credentials:

host:port

With allowlisting, the proxy provider checks the public IP of your machine or server. If that IP is on the allowed list, the proxy accepts the connection. If not, it rejects the request.

HTTP, HTTPS, and SOCKS proxy addresses

The protocol tells your app how to speak to the proxy.

Common proxy protocol prefixes:

http://
https://
socks5://

HTTP and HTTPS proxy addresses are widely supported by scrapers, browsers, bots, and API clients. SOCKS5 is more flexible for some tools and traffic types, but support depends on the app.

For a full protocol comparison, read SOCKS5 vs HTTP proxy. Protocol choice affects compatibility, but it does not replace good session handling, request pacing, and credential hygiene.

Proxy address vs proxy IP

A proxy address is the connection string or settings your tool uses. A proxy IP is the IP address the target website may see after the proxy forwards your traffic.

They are related, but not always the same.

With static ISP proxies, your assigned proxy address may consistently map to the same exit IP. With residential rotating proxies, one gateway address can route to many different exit IPs depending on session settings.

How to find your proxy address

Where you look depends on who set up the proxy.

Proxy you bought. The provider's dashboard lists the host, port, username, and password. Copy them from there instead of typing them.

Proxy set by your employer, school, or network. The address is in your device settings, or it comes from a PAC script that picks the proxy automatically. Ask the network administrator before you change it.

To read the current setting on each system:

Two notes on that table. Microsoft's netsh documentation marks the older netsh winhttp show proxy as deprecated in favor of show advproxy, though the old command still prints a result on many machines. Chrome and Edge follow the operating system's proxy settings by default, so the proxy button in Chrome's settings opens the Windows or macOS panel. The exception is a browser launched with a flag such as --proxy-server="host:port", which overrides the system setting for that browser only.

For full walkthroughs, see the guides for Mac proxy settings, the iPhone HTTP proxy, and the Android SOCKS5 proxy. If Windows reports that it could not automatically detect the network's proxy settings, that guide covers the automatic and WinHTTP settings.

If your network uses a PAC file

On work and school networks, the settings screen often shows a script address instead of a host and port. That is a PAC (proxy auto-config) file. Open the URL in a browser to read it.

A PAC file is JavaScript with one function, FindProxyForURL(url, host). The strings it returns hold the real proxy address:

function FindProxyForURL(url, host) {
  if (isPlainHostName(host) || dnsDomainIs(host, ".corp.example.com")) {
    return "DIRECT";
  }
  return "PROXY proxy.corp.example.com:8080; DIRECT";
}

Here, internal hosts connect directly and everything else goes through proxy.corp.example.com:8080. DIRECT at the end is the fallback if that proxy is down. MDN's PAC reference lists the other return types, such as SOCKS host:port.

If every field is empty and no PAC script is set, your device is not using a proxy. Your public IP is then your own connection's IP, not a proxy IP.

How a proxy address works

The request path usually looks like this:

1. Your tool reads the proxy address.
2. It connects to the proxy host and port.
3. It sends the username and password if required.
4. The proxy gateway checks your account, plan, and options.
5. The gateway selects or keeps an exit IP.
6. The proxy forwards the request to the target website.
7. The target website responds to the proxy.
8. The proxy returns the response to your tool.

If the connection fails at steps 2 to 4, you are debugging proxy setup. If it fails at steps 6 to 8, you may be debugging target blocks, rate limits, sessions, or website behavior.

How to test a proxy address

Use a simple endpoint first. You want to confirm the proxy works before testing a complex website.

For HTTP proxies:

curl -x "http://username:password@host:port" https://ipinfo.io/ip

For SOCKS5 proxies:

curl --socks5 "host:port" --proxy-user "username:password" https://ipinfo.io/ip

If the command returns an IP address, the proxy authenticated and forwarded the request. If it fails, check the host, port, protocol, username, password, IP allowlist, and plan status.

The IP the command prints is your exit IP, the proxy IP address websites see. It is often different from the host you connected to.

Once the proxy works on a neutral endpoint, test your real target at low speed. If the target returns a 403, a 429, a Cloudflare block, or an anonymous proxy detected warning, the proxy address is probably correct and the target is refusing the traffic.

Common mistakes

Avoid these mistakes:

• Pasting the entire proxy string into the host field.
• Using host:port:user:pass in a tool that expects user:pass@host:port.
• Choosing SOCKS5 when the provider gave you an HTTP proxy port.
• Forgetting to include the port.
• Adding http:// to a field that only wants the hostname.
• Using a password with @ or : in a URL format without encoding it.
• Allowlisting your home IP while running the bot on a VPS.
• Mixing residential gateway credentials with static ISP proxy ports.
• Changing session parameters before the plain proxy works.

One known-good proxy template saves a lot of time. Once you know the exact format your tool accepts, keep that format and only swap the host, port, username, password, or session ID as needed.

Which proxy address should you use?

Use the proxy type that matches the workflow:

• Use residential proxies when you need broad location coverage, rotating exits, or sticky consumer-style sessions.
• Use ISP proxies when you need stable dedicated IPs for accounts, ticketing queues, retail checkouts, monitoring, or other session-sensitive workflows.
• Compare datacenter proxies vs residential proxies if cost and speed matter more than consumer IP reputation.
• Read how to use residential proxies if the target expects cookies, logins, carts, or profile continuity.

Once you have the address, how to set up a proxy server walks through entering it in Windows, browsers, and bots.

FAQ

Is a proxy address the same as an IP address?

No. A proxy address is the full connection information your app uses, usually host plus port and sometimes credentials. The proxy IP is the exit IP the target website may see.

What is my proxy server address?

If you bought proxies, it is the host and port in your provider's dashboard. If your device uses a proxy set by a network, check your system's proxy settings. On Windows 11 that is Settings > Network & internet > Proxy. On a Mac, run scutil --proxy in Terminal.

How do I find a proxy's IP address?

There are two answers. The proxy server's IP is the host in your settings, and nslookup proxy.example.com resolves it if the host is a hostname.

The exit IP is what websites see. Send a request through the proxy to an IP-check endpoint, as in the cURL test above.

Do all proxy addresses need usernames and passwords?

No. Some proxies use IP allowlisting and only need a host and port. Private paid proxies commonly use username and password authentication, and many providers support both modes.

Why does my proxy address work in one app but not another?

The apps may expect different formats. One may want separate fields, while another expects a URL or a host:port:user:pass line. Protocol support and special characters in credentials can also change behavior.

Can one proxy address give me many IPs?

Yes. Rotating residential proxy gateways often use one host and port while routing requests through many possible exit IPs. Static ISP and datacenter proxies are more likely to keep the same exit IP.

Is proxyAddresses in Active Directory the same thing?

No. In Active Directory and Microsoft Entra ID, proxyAddresses is a user attribute that stores email aliases such as SMTP:jane@contoso.com. It has nothing to do with network proxies. Microsoft documents it in its Entra ID proxyAddresses guide.

Final thoughts

Get the host and port working first, then add the login, then add session or location options. Test every new proxy against a plain IP-check endpoint before you point it at a real target. Save one format your tool accepts and reuse it. When a request fails, the step where it failed tells you whether to fix the address or deal with the target.