A proxy setup works best when the address format, protocol, port, and login method all match the app using it. A proxy server sits between a client and the internet, which is why it can hide the client IP, filter traffic, or route requests through another location [source: Cloudflare]. Small mistakes cause big delays. Honestly, it feels like proxy tools still enjoy making a missing colon take 20 minutes to find.
TLDR: Most proxy problems come from mixing the wrong format with the wrong setting. For example, 192.0.2.10:8080 may work in a browser, while http://user:pass@192.0.2.10:8080 may be required in a scraper, API client, or automation tool. A team testing 1,000 price pages per hour may cut failed requests by 30% or more simply by using the right protocol, authentication, and timeout settings.
1. IPv4 proxy format
The most common proxy address uses an IPv4 address and port:
- Format:
IP:PORT - Example:
203.0.113.25:8080 - Best for: browsers, bots, API clients, and simple proxy fields
This format is plain and easy to paste. The IP identifies the proxy server. The port tells the app which service to use. Common ports include 8080, 3128, 8000, and 1080.
2. IPv6 proxy format
IPv6 addresses are longer. They also use colons inside the address, which can confuse apps. Many tools require square brackets.
- Format:
[IPv6]:PORT - Example:
[2001:db8:85a3::8a2e:370:7334]:8080 - Best for: systems with IPv6 support and large address pools
The catch is that some older software still handles IPv6 badly. A proxy may be valid, yet the app rejects it because it expects IPv4 only.
3. Hostname and domain proxy format
A proxy can also use a hostname instead of a raw IP address.
- Format:
HOST:PORT - Example:
proxy.example.net:8000 - Best for: managed proxy services and rotating proxy gateways
This format is cleaner. The service provider can change the real server behind the hostname without making the client update settings. That saves time when proxies move between regions or data centers.
4. Protocol-prefixed proxy URL
Some apps need the protocol at the front. This tells the app how traffic should be sent.
- HTTP:
http://203.0.113.25:8080 - HTTPS:
https://proxy.example.net:8443 - SOCKS5:
socks5://203.0.113.25:1080
HTTP proxies are common for web traffic. HTTPS proxies support encrypted connections between the client and proxy. SOCKS5 proxies can handle more traffic types, such as app traffic, games, messaging tools, and some peer connections.
5. Authenticated proxy format
Many private proxies require a username and password. The login can be entered in separate fields, or placed inside the proxy URL.
- Format:
PROTOCOL://USER:PASS@HOST:PORT - Example:
http://alex:myPass123@proxy.example.net:8080 - Best for: paid proxy services, team accounts, and restricted access
This format is handy but risky. Passwords can appear in logs, browser history, or error screens. For shared systems, separate login fields are safer.
6. Rotating and session-based proxy format
Rotating proxies use one gateway address but send traffic through many exit IPs. Session settings are often added to the username, password, or hostname.
- Example:
http://user-session-abc123:pass@gateway.example.net:7000 - Example:
country-us.city-ny.proxy.example.net:9000 - Best for: web scraping, ad checks, SEO checks, and market research
A “sticky” session keeps the same exit IP for a set time, such as 5, 10, or 30 minutes. A rotating session changes the IP more often. Expect to waste time on this setting if the provider names it something unclear, like “identity mode” or “connection profile.”
Core proxy settings that matter
- Host: The IP address or domain name of the proxy server.
- Port: The service door used by the proxy, such as
8080or1080. - Protocol: HTTP, HTTPS, SOCKS4, or SOCKS5.
- Authentication: Username and password, IP allowlist, or both.
- DNS handling: Local DNS or proxy-side DNS. SOCKS5 often supports remote DNS.
- Bypass list: Sites or local addresses that should not use the proxy.
- Timeout: How long the app waits before marking the proxy as failed.
Proxy server address examples
Proxy addresses can look different, but they serve the same basic purpose. A browser may ask for address and port. A command-line tool may need a full URL. A scraping tool may request protocol, host, port, username, password, country, and session ID in separate boxes.
Here are common clean examples:
198.51.100.42:3128proxy.company.net:8080http://proxy.company.net:8080socks5://user:pass@proxy.company.net:1080http://user-country-us-session-77:pass@gateway.proxy.net:7000
FAQ
What is the easiest proxy format to use?
IP:PORT is the easiest. It works in many browser and system settings.
What is the difference between HTTP and SOCKS5?
HTTP is mainly for web traffic. SOCKS5 is more flexible and can carry more kinds of app traffic.
Why does a proxy work in one app but fail in another?
The app may expect a different format. One tool may need host and port in separate fields. Another may need http://user:pass@host:port.
Is it safe to put the password in the proxy URL?
It works, but it is not ideal. The password may be saved in logs or shown in error messages.
Which port should a proxy use?
It depends on the provider. Common ports include 8080, 3128, 8000, 8443, and 1080.
What does a rotating proxy address mean?
It means one gateway can send requests through many exit IPs. This is useful when a task needs many requests without using one single IP.