SOCKS5 UDP support checker
Most providers sell SOCKS5 but don't actually support UDP. Paste your proxy below and the tool sends a real UDP packet through it (DNS query to Google) to verify.
Free, anonymous, takes about 5 seconds.
UDP / Detail check
SOCKS5 proxies onlyIP:Port:User:Pass
Why this matters
SOCKS5 supports UDP through the UDP ASSOCIATE command in RFC 1928. It's optional in the spec, and most "SOCKS5 proxy" providers skip it. TCP through their proxy works fine, UDP just silently fails.
You only find out when the application that needed UDP — DNS resolver, game client, WebRTC stream, Telegram bot, QUIC/HTTP3 connection — stops responding without a useful error message.
What needs UDP through a proxy
- DNS over UDP. Most resolvers prefer UDP for performance. TCP-only proxy means slower DNS
- Online games. Most multiplayer games use UDP for low-latency state sync
- WebRTC. Voice and video calling, screen sharing, anything peer-to-peer
- QUIC and HTTP/3. Modern web browsers prefer QUIC where available
- Telegram bots and clients. MTProto can run over UDP for performance
- Streaming protocols. Some video/audio streaming negotiates UDP transport
- Custom applications. Any tool that does
connect()on a UDP socket and expects responses
This is a real packet round-trip, not a configuration check. Some providers configure SOCKS5 to accept the UDP ASSOCIATE command but don't actually relay UDP packets. This tool catches that.
What the result includes
- Field Description
- UDP support Yes if the DNS query came back. No with reason if it failed
- Exit IP The IP address sites see when you connect through this proxy
- Geo Country and city of the exit IP
- Type Residential or Hosting (datacenter), based on ASN/org keywords
- ISP The organization that owns the exit IP block
FAQ
Why "No" if my proxy works for browsing?
Browsing uses TCP. Your proxy supports TCP just fine. UDP is a separate capability that requires explicit support from the proxy server. Most don't include it.
Does it work for HTTP or HTTPS proxies?
No. UDP relay is a SOCKS5-only feature. HTTP and HTTPS proxies don't have a comparable mechanism.
Why DNS query specifically?
DNS over UDP is the canonical use case for UDP through a proxy and the easiest to verify with a deterministic response. If DNS works, other UDP applications usually work too.
What if my proxy supports UDP for some destinations but not others?
Possible — some providers limit UDP relay to specific port/destination ranges. The test uses 8.8.8.8:53 which is universally allowed. If this fails, your proxy doesn't support UDP at all. If this passes but your application still fails, you're hitting a destination filter.
Is the test result accurate?
Yes for the specific path (DNS to Google over UDP). If you need a stricter test, run our open-source benchmark code against your own UDP destinations.
Do you store my proxy credentials?
No. Credentials pass through the server in memory only. Nothing is logged.
What's the timeout?
5 seconds for the UDP relay setup, 5 seconds for the DNS response. Slow proxies fail this — UDP needs to be fast to be useful.
Looking for a proxy with real UDP support?
UDP is enabled on all our SOCKS5 endpoints. The same checker, run against any of our locations, returns a positive result with sub-100ms round-trip times.