Proxy protocols

TrueProxies supports HTTP/CONNECT, HTTP/CONNECT over TLS, and SOCKS5 on every product, and UDP over SOCKS5 on paid residential plans. Copy the connection host from the service in the dashboard; the ports are the same everywhere.

Residential IPv4 protocols

Residential IPv4 publishes three ports on the service’s connection host, one of them encrypted to the proxy edge:

• HTTP and CONNECT: http://YOUR_HOST:8080
• HTTP and CONNECT over TLS: https://YOUR_HOST:8443
• SOCKS5: socks5://YOUR_HOST:1080

SOCKS5 over TLS is not offered.

The HTTP endpoint accepts normal proxy requests and CONNECT tunnels. The SOCKS5 endpoint supports authenticated TCP proxying with clients that implement SOCKS5, and carries UDP to ports 443 and 53 on paid plans (UDP over SOCKS5). Both billing options use this Residential IPv4 transport; compare current Unlimited and GB-based commercial terms on their canonical product pages.

Datacenter IPv6 protocols

Datacenter IPv6 uses the same three ports, 8080, 8443 and 1080, on the connection host of the city you bought. Copy that host from the service in the dashboard; do not assume port 443.

Residential IPv6 is not yet a connection product. It has no current endpoint or protocol contract.

Comparison

Feature	HTTP	HTTPS	SOCKS5
Proxy-edge encryption	No; encrypt target traffic with HTTPS	Yes	No; encrypt application traffic where supported
Port on every product	8080	8443	1080
Standard client support	Broad	Requires HTTPS proxy support	Requires SOCKS5 support
UDP	No	No	Yes on paid residential plans: UDP over SOCKS5, destination ports 443 and 53

UDP over SOCKS5

SOCKS5 can carry UDP as well as TCP. Use the same host, port 1080, username and password you already use for SOCKS5; there is nothing extra to turn on.

• Plans: paid Unlimited Bandwidth plans and traffic packs (Residential IPv4). Not available on the Free trial, the Free comparison or Datacenter IPv6.
• Ports: UDP to destination ports 443 (QUIC, HTTP/3) and 53 (DNS) only. Packets to any other port are dropped.
• Connections: up to 256 UDP connections per service at the same time. A UDP connection closes after 60 seconds without traffic; open a new one.
• Packet size: keep packets at 1,400 bytes or less. Larger packets do not get through the residential path.
• Sticky sessions: when your username selects a sticky session, the whole UDP connection stays on the same exit IP as your TCP traffic.
• Firewalls: the proxy answers your UDP request with a UDP port on the gateway in the range 40000 to 49999. If your network restricts outbound traffic, allow outbound UDP to that range on the connection host.
• Traffic: UDP traffic counts toward your traffic like TCP does, including the small SOCKS5 header on every packet. This matters on a traffic pack.
• Packet loss: residential exits can drop some packets at high packet rates. QUIC and DNS clients retransmit; plan for it in your own tooling.

HTTP and HTTPS proxies carry TCP only; there is no UDP in HTTP CONNECT. That is true of every provider, not only TrueProxies.

curl does not support SOCKS5 UDP. Use a client that does (tool authors: this is the SOCKS5 UDP ASSOCIATE command). Python with PySocks:

import socket
import socks

s = socks.socksocket(socket.AF_INET, socket.SOCK_DGRAM)
s.set_proxy(socks.SOCKS5, "YOUR_HOST", 1080, username="USER", password="PASS")
# minimal DNS query for example.com (A record) to 1.1.1.1 port 53
query = bytes.fromhex("123401000001000000000000076578616d706c6503636f6d0000010001")
s.sendto(query, ("1.1.1.1", 53))
reply, _ = s.recvfrom(1500)
print(len(reply), "bytes")

Replace YOUR_HOST, USER and PASS with the values from your service page.

Product-specific controls

• Residential IPv4 supports the documented country and sticky-session username forms. Its exits cannot reach IPv6-only destinations.
• Datacenter IPv6 uses assigned city endpoints. Do not copy Residential IPv4 username suffixes onto those credentials.
• Residential IPv6 is planned and does not yet have endpoints or credentials.
• Endpoint inventory and authentication mode in the dashboard are authoritative.

See How to connect for safe examples and the exact username grammar.