UDP Proxies

• Rated 4.6/5 on Trustpilot (100+ reviews)
• HTTP(S), SOCKS5 & UDP
• No concurrent session limit
• Sticky sessions or new IP per request
• Bandwidth rolls over
• 24/7 support from real people

What a UDP proxy is

QUIC, HTTP/3 and DNS through a residential IP

Most proxy traffic runs over TCP: your tool opens a connection, and the proxy relays it from another IP address. UDP works differently. It sends separate datagrams with no connection, and it carries QUIC, which HTTP/3 runs on, and most DNS lookups. A UDP proxy relays those datagrams from the proxy’s IP, so the target sees a residential or mobile address instead of yours.

Many residential proxy networks carry TCP only. Through them, an HTTP/3 client falls back to HTTP/2, and tools that need UDP don’t work at all. ProxyEmpire’s Rotating Residential and Rotating Mobile proxies carry UDP as well as TCP, so QUIC and DNS traffic can leave from the same pool of real home broadband and carrier IPs. For the protocol side, read our guide to how SOCKS5 works.

• Two ways in. SOCKS5 UDP ASSOCIATE for any client that supports UDP over SOCKS5, or a MASQUE (CONNECT-UDP) tunnel for HTTP/3-native clients.
• Same login as TCP. UDP uses your normal proxy username and password on v2.proxyempire.io:5000.
• Same targeting. Country, region, city, ZIP, ISP or carrier, ASN and sticky sessions work the same way as over TCP.
• Same balance. UDP traffic counts against your GB balance, with no extra fee.
• UDP ports 443 and 53 open by default, for QUIC and HTTP/3 and for DNS.

Buy UDP proxies: prices

UDP is included on both rotating plans

ISP, datacenter, dedicated mobile and unlimited residential proxies carry TCP only. Compare every plan on ProxyEmpire pricing.

UDP residential proxy plans

Rotating residential, UDP and all targeting included

Try the network for $1.97, pay as you go from a single GB at $3.50, or take a larger plan for as little as $1.50/GB. Prices are the same in every location, and plans are billed in US dollars (USD). UDP, SOCKS5, HTTP and HTTPS are all included, targeting costs nothing extra, and unused bandwidth rolls over.

Discounted prices use code EMPIRE50 (limited time, rotating residential and mobile only). Rotating mobile starts at $4.50 for 1 GB and goes down to $2.00/GB on larger plans. Static residential costs $3.50 for a single IP, down to $2.00 per IP a month on larger bundles. All mobile, static and datacenter plans are on the full pricing page.

Connect with SOCKS5 UDP ASSOCIATE

For clients that support UDP over SOCKS5

SOCKS5 defines a UDP ASSOCIATE command next to the usual CONNECT. Your client logs in over a TCP connection, asks for a UDP relay, and then sends each datagram to the relay address the proxy returns. The relay stays open for as long as that TCP connection does.

• Host and port: v2.proxyempire.io:5000, the same as for SOCKS5 and HTTP over TCP
• Login: your Proxy Manager username and password
• Targeting and sessions: in the username, for example -country-us and -sid-123456 for a sticky US session
• Destination ports: UDP 443 and 53 by default

Python example. This sends one DNS query over SOCKS5 UDP with the PySocks and dnspython packages. Google’s name server answers with the IP address it sees, so the reply shows the proxy’s exit IP.

# pip install pysocks dnspython
import socks
import dns.message

s = socks.socksocket(socks.socket.AF_INET, socks.socket.SOCK_DGRAM)
s.set_proxy(socks.SOCKS5, "v2.proxyempire.io", 5000,
            username="USERNAME-country-us-sid-123456", password="PASSWORD")
s.settimeout(10)
query = dns.message.make_query("o-o.myaddr.l.google.com", "TXT")
s.sendto(query.to_wire(), ("216.239.32.10", 53))  # ns1.google.com
reply, _ = s.recvfrom(4096)
print(dns.message.from_wire(reply).answer)

Browsers don’t send UDP through a SOCKS5 proxy, so Chrome and Chromium-based tools keep using HTTP/2 over TCP there. For UDP, use a client or library that implements SOCKS5 UDP ASSOCIATE, or a MASQUE client.

Connect with MASQUE over HTTP/3

CONNECT-UDP (RFC 9298) for HTTP/3-native clients

MASQUE carries UDP inside an HTTP/3 connection. Your client opens QUIC to the gateway, sends an extended CONNECT request for the target host and port, and then exchanges the UDP payloads as HTTP Datagrams.

• Endpoint: v2.proxyempire.io:5000 over QUIC, ALPN h3
• Request: extended CONNECT with the connect-udp protocol, the target’s host and port in the path, and the headers below
• Login: a Proxy-Authorization header with Basic authentication, using your proxy username (with targeting) and password
• Datagrams: your client must send the SETTINGS_H3_DATAGRAM setting (RFC 9297). Without it, replies arrive as DATAGRAM capsules on the request stream.
• Answers: 200 opens the tunnel, 407 means the login is wrong, and 403 means the target port isn’t open

The request your client sends, here for a DNS server at 8.8.8.8 port 53:

:method = CONNECT
:protocol = connect-udp
:scheme = https
:authority = v2.proxyempire.io:5000
:path = /.well-known/masque/udp/8.8.8.8/53/
capsule-protocol: ?1
proxy-authorization: Basic base64(USERNAME:PASSWORD)

What works over UDP, and what doesn’t

Limits worth knowing before you buy

UDP ports 443 (QUIC and HTTP/3) and 53 (DNS) are open by default. Other UDP ports can be opened after KYC and a review of your use case: write to [email protected]. Online games, voice calls and WebRTC use other UDP ports, so they don’t go through the proxy by default. Over TCP, ports 80 and 443 are open by default, and port 25 is never opened. Some site categories are blocked on every proxy type: see blocked websites.

What teams use UDP proxies for

Where UDP through a residential IP helps

ProxyEmpire is built for legitimate data collection, testing and account management. Each website’s terms still apply on any IP, and we don’t support spam, fraud or any illegal activity.

UDP support by proxy type

Which ProxyEmpire proxies carry UDP

UDP proxy FAQ

Straight answers

More on UDP and SOCKS5

Guides and tools