Why UDP is harder than TCP
UDP has no handshake. An open service may stay silent if the probe is not a valid application request.
Closed ports sometimes send ICMP port unreachable, but many firewalls drop those messages — so silence often means open or filtered.
For TCP listeners and multi-port scans, use the Port Checker instead.
Verify WireGuard and game port forwards
Your public IP is filled in on load — confirm it anytime with What Is My IP.
Pick WireGuard (51820), OpenVPN (1194), Minecraft Bedrock (19132), or enter a custom UDP port, then Check. An open reply means SkyPath’s Probe reached that forward from outside your LAN.
No reply is common for VPN datagrams: the port may still be open but quiet for our probe. Confirm with the real client if you expect traffic.
How SkyPath probes UDP
For well-known ports we send protocol-native packets — a DNS A query on 53, an NTP client request on 123, SNMP GetRequest on 161, and similar for SIP/IKE where practical.
Other ports get a short generic UDP probe. We never invent open/closed results in the browser.
What open|filtered means
No application reply arrived before the timeout. The port may be open and silent, or filtered by a firewall.
To confirm a service, try a known-good demo (8.8.8.8 DNS) or test with the real client application. If the host might be down entirely, try Ping Test.
Common UDP services
DNS (53), NTP (123), SNMP (161), IKE/IPsec (500), OpenVPN (1194), SIP (5060), WireGuard (51820), and Minecraft Bedrock (19132) are frequent checks.
Need TCP instead? Open the Port Checker for single ports and scan profiles.