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

Enter your server's IP address or domain followed by a colon and the port number (e.g. 1.1.1.1:80 or example.com:443) and run a TCP check. The tool attempts a TCP handshake from 50+ global nodes and reports whether each connection succeeded, was refused, or timed out.

What is the difference between a port being refused versus timing out?

A refused connection (TCP RST) means the port is actively closed — the server replied to reject the connection. A timeout means no reply was received at all, which typically indicates a firewall is silently dropping packets before they reach the server or application.

Which TCP ports can I test?

Any valid TCP port from 1 to 65535. Common examples include port 80 (HTTP), 443 (HTTPS), 22 (SSH), 25 (SMTP), 3306 (MySQL), 5432 (PostgreSQL), and 3389 (RDP). No login or special permissions required — the check only verifies whether the TCP handshake completes.

My port is open locally but fails from external nodes — why?

If a port works locally but fails from external nodes, something between the internet and your server is blocking it — commonly a cloud security group, iptables rule, upstream ISP filter, or geoblocking policy. Running the check from multiple regions helps identify whether the block is global or specific to certain countries or ASNs.

nl-ams-aluy.check-host.eu:80 のレポート

Name: Check-Host nl-ams-aluy.check-host.eu:80 TCP ポート疎通テスト
Author: Check-Host

Info Ping HTTP TCP UDP MTR DNS

TCP チェック nl-ams-aluy.check-host.eu:80

Apr 21, 2026 00:40:41 UTC に確認 |

| 再チェック |

拠点	結果	応答時間	IP アドレス
Albania, Tirana	ERROR	-	185.132.53.50
Australia, Sydney	ERROR	-	185.132.53.50
Bosnia and Herzegovina, Novi Travnik	ERROR	-	185.132.53.50
Bulgaria, Sofia	ERROR	-	185.132.53.50
Canada, Montreal	ERROR	-	185.132.53.50
Switzerland, Bern	ERROR	-	185.132.53.50
Chile, Santiago	ERROR	-	185.132.53.50
China, Hohhot	ERROR	-	185.132.53.50
Germany, Nuernberg	ERROR	-	185.132.53.50
Germany, Frankfurt am Main	ERROR	-	185.132.53.50
Germany, Frankfurt am Main	ERROR	-	185.132.53.50
Germany, Limburg	ERROR	-	185.132.53.50
Germany, Frankfurt am Main	ERROR	-	185.132.53.50
Germany, Duesseldorf	ERROR	-	185.132.53.50
Denmark, Glostrup Municipality	Connected	70.0 ms	185.132.53.50
Spain, Bilbao	ERROR	-	185.132.53.50
Finland, Helsinki	ERROR	-	185.132.53.50
Finland, Helsinki	ERROR	-	185.132.53.50
France, Gravelines	ERROR	-	185.132.53.50
France, Paris	Connected	61.0 ms	185.132.53.50
United Kingdom, London	ERROR	-	185.132.53.50
Georgia, Tbilisi	ERROR	-	nl-ams-aluy.check-host.eu
Greece, Athens	ERROR	-	nl-ams-aluy.check-host.eu
Hong Kong, Hong Kong	ERROR	-	185.132.53.50
Croatia, Zagreb	ERROR	-	185.132.53.50
Hungary, Budapest	Connected	27.0 ms	185.132.53.50
Indonesia, Jakarta	ERROR	-	185.132.53.50
Israel, Petach Tikwa	ERROR	-	185.132.53.50
Israel, Netanja	ERROR	-	185.132.53.50
India, New Delhi	ERROR	-	185.132.53.50
Iceland, Reykjavik (Miðborg)	ERROR	-	185.132.53.50
Italy, Como	ERROR	-	185.132.53.50
Kuwait, Kuwait City	ERROR	-	nl-ams-aluy.check-host.eu
Lithuania, Pilaite	ERROR	-	185.132.53.50
Latvia, Riga	Connected	115.0 ms	185.132.53.50
Moldova, Chisinau	Connected	105.0 ms	185.132.53.50
Netherlands, Amsterdam	ERROR	-	185.132.53.50
Netherlands, Amsterdam	ERROR	-	185.132.53.50
Netherlands, Amsterdam	ERROR	-	185.132.53.50
Netherlands, Amsterdam	ERROR	-	185.132.53.50
Norway, Oslo	ERROR	-	185.132.53.50
Poland, Warsaw	Connected	15.0 ms	185.132.53.50
Romania, Bacău	ERROR	-	185.132.53.50
Romania, Bucharest	ERROR	-	185.132.53.50
Serbia, Belgrade	Connected	100.0 ms	185.132.53.50
Russia, St Petersburg	ERROR	-	185.132.53.50
Singapore, Singapore	ERROR	-	185.132.53.50
Turkey, Istanbul	ERROR	-	185.132.53.50
Taiwan, Taipei	ERROR	-	185.132.53.50
United States, Miami	ERROR	-	185.132.53.50
United States, Dallas	ERROR	-	185.132.53.50
United States, Kansas City	ERROR	-	185.132.53.50
United States, Dallas	ERROR	-	185.132.53.50
South Africa, Johannesburg	ERROR	-	185.132.53.50