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.

golem.de:80 のレポート

Info Ping HTTP TCP UDP MTR DNS

report.report_types.udp golem.de:80

Apr 21, 2026 19:04:24 UTC に確認 |

| 再チェック |

拠点	結果	応答時間	IP アドレス
Albania, Tirana	Timeout	-	77.247.84.129
Australia, Sydney	Timeout	-	77.247.84.129
Bosnia and Herzegovina, Novi Travnik	Timeout	-	77.247.84.129
Bulgaria, Sofia	Timeout	-	77.247.84.129
Canada, Montreal	Timeout	-	77.247.84.129
Switzerland, Bern	Timeout	-	77.247.84.129
Chile, Santiago	Timeout	-	77.247.84.129
China, Hohhot	Timeout	-	77.247.84.129
Germany, Nuernberg	Timeout	-	77.247.84.129
Germany, Frankfurt am Main	Timeout	-	77.247.84.129
Germany, Frankfurt am Main	Timeout	-	77.247.84.129
Germany, Limburg	Timeout	-	77.247.84.129
Germany, Frankfurt am Main	Timeout	-	77.247.84.129
Germany, Duesseldorf	Timeout	-	77.247.84.129
Denmark, Glostrup Municipality	Timeout	-	77.247.84.129
Spain, Bilbao	Timeout	-	77.247.84.129
Finland, Helsinki	Timeout	-	77.247.84.129
Finland, Helsinki	Timeout	-	77.247.84.129
France, Gravelines	Timeout	-	77.247.84.129
France, Paris	Timeout	-	77.247.84.129
United Kingdom, London	Timeout	-	77.247.84.129
Georgia, Tbilisi	UDP checks unavailable: SOCKS5 proxy does not support UDP ASSOCIATE	-	golem.de
Greece, Athens	UDP checks unavailable: SOCKS5 proxy does not support UDP ASSOCIATE	-	golem.de
Hong Kong, Hong Kong	Timeout	-	77.247.84.129
Croatia, Zagreb	Timeout	-	77.247.84.129
Hungary, Budapest	Timeout	-	77.247.84.129
Indonesia, Jakarta	Timeout	-	77.247.84.129
Israel, Petach Tikwa	Timeout	-	77.247.84.129
Israel, Netanja	Timeout	-	77.247.84.129
India, New Delhi	Timeout	-	77.247.84.129
Iceland, Reykjavik (Miðborg)	Timeout	-	77.247.84.129
Italy, Como	Timeout	-	77.247.84.129
Kuwait, Kuwait City	UDP checks unavailable: SOCKS5 proxy does not support UDP ASSOCIATE	-	golem.de
Lithuania, Pilaite	Timeout	-	77.247.84.129
Latvia, Riga	Timeout	-	77.247.84.129
Moldova, Chisinau	Timeout	-	77.247.84.129
Netherlands, Amsterdam	Timeout	-	77.247.84.129
Netherlands, Amsterdam	Timeout	-	77.247.84.129
Netherlands, Amsterdam	Timeout	-	77.247.84.129
Netherlands, Amsterdam	Timeout	-	77.247.84.129
Norway, Oslo	Timeout	-	77.247.84.129
Poland, Warsaw	Timeout	-	77.247.84.129
Romania, Bacău	DNS Error: No valid public IP found for golem.de	-	-
Romania, Bucharest	Timeout	-	77.247.84.129
Serbia, Belgrade	Timeout	-	77.247.84.129
Russia, St Petersburg	Timeout	-	77.247.84.129
Singapore, Singapore	Timeout	-	77.247.84.129
Turkey, Istanbul	Timeout	-	77.247.84.129
Taiwan, Taipei	Timeout	-	77.247.84.129
United States, Miami	Timeout	-	77.247.84.129
United States, Dallas	Timeout	-	77.247.84.129
United States, Kansas City	Timeout	-	77.247.84.129
United States, Dallas	Timeout	-	77.247.84.129
South Africa, Johannesburg	Timeout	-	77.247.84.129