UDP Port Check
A UDP test sends a single datagram to the specified host and port and waits for a reply.
How to Use
• Target:Enter host:port (e.g. 8.8.8.8:53); the default port is 53 (DNS) when none is given
• What is checked:A single UDP datagram is sent and the probe waits for an application-layer reply within the timeout
• Why no reply is ambiguous:A closed UDP port usually stays silent too, so open and filtered cannot be distinguished without raw ICMP — a reply proves open, silence proves nothing
• Node selection:Optionally select specific nodes; all available nodes are used by default
What UDP port testing is for
A UDP test sends a single datagram to the specified host and port and waits for a reply. Because UDP is a connectionless protocol with no handshake, receiving a reply proves the port is open and a service is answering, but receiving nothing is ambiguous — the port could be open-but-silent, filtered by a firewall, or the packet could simply have been lost.
Common uses include checking that a DNS resolver (port 53), NTP server (port 123), SNMP agent (port 161), or a game / VoIP service is reachable and responding, and diagnosing whether a firewall is silently dropping UDP traffic to a service.
Frequently asked questions
Why can't the tool tell me if a UDP port is closed?
Unlike TCP, UDP has no handshake. A closed UDP port may respond with an ICMP 'port unreachable' message, but many hosts and firewalls suppress or rate-limit those messages, so the absence of a reply looks identical to an open port that simply didn't answer. Only a positive reply is conclusive.
What payload should I send?
By default the probe sends a single null byte, which is enough to elicit a response from simple echo-style services. For protocol-specific services you can supply a hex payload (e.g. a DNS query) so the service recognises the request and replies.
Which port does it use by default?
If you enter a bare host with no port, the probe uses port 53 (DNS), the most common UDP service to reach for a quick reachability check. Specify host:port to target any other service.
A reply came back — does that mean the service is healthy?
It means the port is open and something answered at the transport layer. It does not validate the application-level response content; use a protocol-specific tool (e.g. the DNS or NTP test) to confirm the service behaves correctly.
References and result limitations
Online results reflect the queried source or probe state at that time. Record the target, time, nodes or data source, and parameters when citing them. A single result does not establish continuous availability everywhere.
These references explain protocol or format rules; they do not endorse results produced by this site.