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.

Report for us-dal-private.check-host.eu:80

Name: Check-Host us-dal-private.check-host.eu:80 TCP Port Connectivity Test
Author: Check-Host

Info Ping HTTP TCP UDP MTR DNS

Check TCP us-dal-private.check-host.eu:80

Checked Apr 20, 2026 21:54:49 UTC |

| Check again |

ठिकाण	निकाल	वेळ	IP Address
Albania, Tirana	ERROR	-	144.225.93.132
Australia, Sydney	ERROR	-	144.225.93.132
Bosnia and Herzegovina, Novi Travnik	ERROR	-	144.225.93.132
Bulgaria, Sofia	ERROR	-	144.225.93.132
Canada, Montreal	ERROR	-	144.225.93.132
Switzerland, Bern	ERROR	-	144.225.93.132
Chile, Santiago	ERROR	-	144.225.93.132
China, Hohhot	ERROR	-	144.225.93.132
Germany, Nuernberg	ERROR	-	144.225.93.132
Germany, Frankfurt am Main	ERROR	-	144.225.93.132
Germany, Frankfurt am Main	ERROR	-	144.225.93.132
Germany, Limburg	ERROR	-	144.225.93.132
Germany, Frankfurt am Main	ERROR	-	144.225.93.132
Germany, Duesseldorf	ERROR	-	144.225.93.132
Denmark, Glostrup Municipality	Connected	12.0 ms	144.225.93.132
Spain, Bilbao	ERROR	-	144.225.93.132
Finland, Helsinki	ERROR	-	144.225.93.132
Finland, Helsinki	ERROR	-	144.225.93.132
France, Gravelines	ERROR	-	144.225.93.132
France, Paris	Connected	9.0 ms	144.225.93.132
United Kingdom, London	ERROR	-	144.225.93.132
Georgia, Tbilisi	ERROR	-	us-dal-private.check-host.eu
Greece, Athens	ERROR	-	us-dal-private.check-host.eu
Hong Kong, Hong Kong	ERROR	-	144.225.93.132
Croatia, Zagreb	ERROR	-	144.225.93.132
Hungary, Budapest	Connected	15.0 ms	144.225.93.132
Indonesia, Jakarta	ERROR	-	144.225.93.132
Israel, Petach Tikwa	ERROR	-	144.225.93.132
Israel, Netanja	ERROR	-	144.225.93.132
India, New Delhi	ERROR	-	144.225.93.132
Iceland, Reykjavik (Miðborg)	ERROR	-	144.225.93.132
Italy, Como	ERROR	-	144.225.93.132
Kuwait, Kuwait City	ERROR	-	us-dal-private.check-host.eu
Lithuania, Pilaite	ERROR	-	144.225.93.132
Latvia, Riga	Connected	31.0 ms	144.225.93.132
Moldova, Chisinau	Connected	35.0 ms	144.225.93.132
Netherlands, Amsterdam	ERROR	-	144.225.93.132
Netherlands, Amsterdam	ERROR	-	144.225.93.132
Netherlands, Amsterdam	ERROR	-	144.225.93.132
Netherlands, Amsterdam	ERROR	-	144.225.93.132
Norway, Oslo	ERROR	-	144.225.93.132
Poland, Warsaw	Connected	16.0 ms	144.225.93.132
Romania, Bacău	ERROR	-	144.225.93.132
Romania, Bucharest	ERROR	-	144.225.93.132
Serbia, Belgrade	Connected	32.0 ms	144.225.93.132
Russia, St Petersburg	ERROR	-	144.225.93.132
Singapore, Singapore	ERROR	-	144.225.93.132
Turkey, Istanbul	ERROR	-	144.225.93.132
Taiwan, Taipei	ERROR	-	144.225.93.132
United States, Miami	ERROR	-	144.225.93.132
United States, Dallas	ERROR	-	144.225.93.132
United States, Kansas City	ERROR	-	144.225.93.132
United States, Dallas	ERROR	-	144.225.93.132
South Africa, Johannesburg	ERROR	-	144.225.93.132