UDP Test
Test IPv4 and IPv6 UDP connectivity through proxies, VPNs, firewalls, and NAT using simple terminal commands
Test IPv4 and IPv6 UDP connectivity through your proxy, VPN, or NAT
Send a UDP datagram to our echo server over IPv4 or IPv6 and wait for a reply. Useful for validating SOCKS5 UDP support, VPN tunnels that should carry UDP, firewall and NAT rules, and any setup where UDP is supposed to work but might be silently dropped.
Hello, message received from: {ip}, at: {timestamp}, message: {message}UDP Test Access — 15 minutes
UDP responses are enabled for 15 minutes after you visit this page. Once the time expires, the server will stop responding to your UDP requests. Simply revisit or refresh this page to enable UDP responses for another 15 minutes.
UDP test commands for each platform
Choose IPv4 or IPv6, copy the command for your operating system, and run it in a terminal. A successful echo reply confirms UDP connectivity to our server over the selected IP version. UDP responses are available for 15 minutes after visiting this page. Refresh to renew access.
Linux
Most Linux distributions support netcat (nc). Use -4 or -6 to select the IP version.
echo "udp-test-from-linux-ipv4" | nc -4 -u -w 2 65.21.106.102 8080macOS
macOS includes BSD netcat. Select IPv4 or IPv6 explicitly.
echo "udp-test-from-macos-ipv4" | nc -4 -u -w 2 65.21.106.102 8080Windows (PowerShell)
No additional tools required. Uses .NET UdpClient with explicit IPv4 or IPv6 support.
$server = "65.21.106.102"
$port = 8080
$msg = "udp-test-from-windows-ipv4"
$udp = New-Object System.Net.Sockets.UdpClient(
[System.Net.Sockets.AddressFamily]::InterNetwork
)
$udp.Client.ReceiveTimeout = 2000
try {
$bytes = [Text.Encoding]::UTF8.GetBytes($msg)
[void]$udp.Send($bytes, $bytes.Length, $server, $port)
$remote = New-Object System.Net.IPEndPoint(
[System.Net.IPAddress]::Any, 0
)
$respBytes = $udp.Receive([ref]$remote)
[Text.Encoding]::UTF8.GetString($respBytes)
}
finally {
$udp.Close()
}Android (Termux)
Install netcat-openbsd in Termux, then select IPv4 or IPv6.
pkg update -y
pkg install -y netcat-openbsd
echo "udp-test-from-android-ipv4" | nc -4 -u -w 2 65.21.106.102 8080iOS (iSH Shell)
Install netcat-openbsd in iSH. IPv6 availability depends on the iSH networking implementation.
apk update
apk add netcat-openbsd
echo "udp-test-from-ios-ipv4" | nc -4 -u -w 2 65.21.106.102 8080- If you get no response, first make sure you have visited this page within the last 15 minutes. Refresh it to renew UDP access, then try the command again. If the problem persists, UDP may be blocked by a firewall, NAT rules, or a network policy (common on public Wi-Fi).
- IPv4 and IPv6 connectivity are independent. A successful IPv4 UDP test does not guarantee IPv6 UDP connectivity, and vice versa. Your device, network, and internet provider must support the selected IP version.
- HTTP/HTTPS proxies generally do not relay arbitrary UDP datagrams. For UDP traffic, you typically need a SOCKS5 proxy that supports UDP ASSOCIATE or a VPN. Your application must also support SOCKS5 UDP relay; running these commands directly does not test a browser's proxy configuration.
- If testing through a VPN, try both "VPN on" and "VPN off" to isolate whether the tunnel or your local network is blocking UDP.
- If UDP access is authorized using your public IP address, the UDP request must come from an authorized source IP. IPv4 and IPv6 use different source addresses, so both may need to be authorized separately by the backend. Proxies and VPNs may also change your outgoing IP.
- Compare UDP-capable SOCKS5 proxies or a residential WireGuard VPN if your application needs one. For selective VPN routing, use the AllowedIPs calculator and verify that the test destination is actually included in the tunnel.
Our Services
We offer a variety of static and dynamic IP solutions designed for legitimate business and technical use, with global coverage tailored to your project requirements.
Buy Proxy, SOCKS5 & ShadowSocks Now
Buy Proxy now HTTP Proxies or SOCKS5, Dedicated or Shared, Residential or Datacenter. Fully Anonymous and Premium.
Buy Proxy
We answer your questions
Got questions? We've got answers! Dive into our frequently asked questions below.
A UDP test checks whether User Datagram Protocol (UDP) traffic can successfully reach a server and receive a response. This is important when using proxies or VPNs because many real-time services—such as VoIP, gaming, streaming, or custom networking tools—rely on UDP. If UDP is blocked or filtered, these services may fail or behave unpredictably.
A UDP echo test sends a UDP packet to a server that is configured to reply (echo) the same data back. If you receive a response, it confirms that outbound and inbound UDP traffic is working correctly between your device and the server.
Yes, but only if the proxy supports UDP traffic. SOCKS5 proxies, such as those provided by ProxySocks5, can handle UDP, while HTTP/HTTPS proxies generally cannot. A UDP echo test helps confirm whether UDP forwarding is actually working through the proxy.
Most modern VPNs support UDP, and many use UDP-based protocols by default for better speed and lower latency. Running a UDP test while connected to a VPN helps verify that UDP packets are not blocked by the VPN tunnel or firewall rules.
You can test UDP from the terminal using tools like netcat (nc). For example, sending a UDP packet to a UDP echo server and waiting for a reply allows you to quickly verify UDP connectivity on Linux, macOS, or Windows.
UDP is connectionless, meaning there is no handshake or guaranteed delivery like TCP. A UDP test relies on receiving an echo response; if no response arrives, it may be due to packet loss, firewall rules, NAT behavior, or filtering by a proxy or VPN.
If TCP works but UDP fails, it usually means UDP traffic is being blocked or filtered somewhere along the path—often by a firewall, router, proxy, or VPN configuration. This is common in restrictive networks or misconfigured proxy setups.
Yes. Gaming, VoIP, video calls, and live streaming often rely on UDP for low latency. A successful UDP echo test indicates that these applications are more likely to function correctly through your proxy or VPN.
Yes. UDP tests can be performed from the terminal on Linux, macOS, and Windows using common networking tools. The commands may vary slightly, but the underlying test logic is the same across platforms.
Running a UDP test before deploying a proxy or VPN setup helps ensure that UDP traffic is properly supported and routed. This avoids unexpected issues later when using applications that depend on UDP performance and reliability.
