How do I check if a UDP port is open online?

Enter a host and UDP port (e.g. 8.8.8.8:53) in the UDP checker. The tool sends protocol-appropriate payloads from 50+ global nodes — for example, a real DNS query to port 53 or an NTP request to port 123 — and reports whether a valid response was received from each location.

Why does UDP port testing require a payload?

Unlike TCP, UDP has no handshake. An empty packet sent to most UDP services produces no response because the application is waiting for meaningful data before replying. The tool automatically injects the correct payload for known ports (DNS/53, NTP/123, SNMP/161, game servers/27015) to get a real, meaningful response.

How do I test if my VPN UDP port is reachable?

Enter your VPN server IP and port (typically UDP 1194 for OpenVPN or UDP 51820 for WireGuard) and run the UDP check. Results from multiple global nodes will show whether your VPN port is accessible worldwide or blocked by specific ISPs or regional networks.

Can I test game server ports with this UDP checker?

Yes. For Source Engine game servers (CS:GO, TF2, Rust) on port 27015, the tool automatically sends a valid Source Engine query packet. For other game servers, you can enter a custom hex payload in the advanced options. Results show which global regions can reach your game server.

google.com:80 のレポート

Info Ping HTTP TCP UDP MTR DNS

report.report_types.udp google.com:80

Apr 21, 2026 23:53:23 UTC に確認 |

| 再チェック |

拠点	結果	応答時間	IP アドレス
Albania, Tirana	Timeout	-	192.178.24.174
Australia, Sydney	Timeout	-	172.217.25.174
Bosnia and Herzegovina, Novi Travnik	Timeout	-	142.250.203.142
Bulgaria, Sofia	Timeout	-	172.217.21.238
Canada, Montreal	Timeout	-	142.250.69.142
Switzerland, Bern	Timeout	-	74.125.29.138
Chile, Santiago	Timeout	-	172.217.192.102
China, Hohhot	Timeout	-	142.250.73.142
Germany, Nuernberg	Timeout	-	142.251.20.102
Germany, Frankfurt am Main	Timeout	-	142.251.110.138
Germany, Frankfurt am Main	Timeout	-	142.251.14.138
Germany, Limburg	Timeout	-	142.251.13.100
Germany, Frankfurt am Main	Timeout	-	192.178.183.102
Germany, Duesseldorf	Timeout	-	142.251.39.142
Denmark, Glostrup Municipality	Timeout	-	192.178.25.14
Spain, Bilbao	Timeout	-	142.251.13.139
Finland, Helsinki	Timeout	-	142.251.38.78
Finland, Helsinki	Timeout	-	142.251.38.78
France, Gravelines	Timeout	-	192.178.183.113
France, Paris	Timeout	-	172.217.22.14
United Kingdom, London	Timeout	-	142.250.129.102
Georgia, Tbilisi	UDP checks unavailable: SOCKS5 proxy does not support UDP ASSOCIATE	-	google.com
Greece, Athens	UDP checks unavailable: SOCKS5 proxy does not support UDP ASSOCIATE	-	google.com
Hong Kong, Hong Kong	Timeout	-	216.58.198.14
Croatia, Zagreb	Timeout	-	142.251.110.139
Hungary, Budapest	Timeout	-	172.217.171.174
Indonesia, Jakarta	Timeout	-	74.125.130.113
Israel, Petach Tikwa	Timeout	-	142.250.75.46
Israel, Netanja	Timeout	-	142.250.75.46
India, New Delhi	Timeout	-	142.250.67.78
Iceland, Reykjavik (Miðborg)	Timeout	-	142.250.180.14
Italy, Como	Timeout	-	142.251.141.238
Kuwait, Kuwait City	UDP checks unavailable: SOCKS5 proxy does not support UDP ASSOCIATE	-	google.com
Lithuania, Pilaite	Timeout	-	172.217.19.238
Latvia, Riga	Timeout	-	142.250.102.100
Moldova, Chisinau	Timeout	-	192.178.24.174
Netherlands, Amsterdam	Timeout	-	142.251.142.206
Netherlands, Amsterdam	Timeout	-	192.178.25.206
Netherlands, Amsterdam	Timeout	-	172.217.23.238
Netherlands, Amsterdam	Timeout	-	172.217.17.206
Norway, Oslo	Timeout	-	209.85.203.102
Poland, Warsaw	Timeout	-	142.251.98.101
Romania, Bacău	Timeout	-	142.251.13.101
Romania, Bucharest	Timeout	-	172.217.168.110
Serbia, Belgrade	Timeout	-	142.251.20.101
Russia, St Petersburg	Timeout	-	173.194.221.102
Singapore, Singapore	Timeout	-	142.250.4.101
Turkey, Istanbul	Timeout	-	172.217.22.238
Taiwan, Taipei	Timeout	-	142.250.204.46
United States, Miami	Timeout	-	142.250.176.78
United States, Dallas	Timeout	-	142.250.113.113
United States, Kansas City	Timeout	-	209.85.145.100
United States, Dallas	Timeout	-	142.251.116.101
South Africa, Johannesburg	Timeout	-	142.251.216.14