Open Port Checker
Check whether a TCP port on a server is open, from probes around the world. See the handshake time from each one, look up what a port is registered for, and learn why a port can look closed.
How to Use
- Type the server’s host name or public IP address. You can also type host:port, such as smtp.gmail.com:587.
- Type the TCP port, or click one in the common ports list (22 SSH, 443 HTTPS, 3389 Remote Desktop and so on).
- Choose how many probes (3 to 8), where they are, and how many handshakes each makes (1 to 5).
- Press Run live check. Each probe reports within a few seconds whether the TCP handshake completed. Until then the page shows a recorded example.
- Read the verdict and Show Work. If the port looks closed, check the section on firewalls, carrier-grade NAT and provider port blocks before blaming the service.
A live run uses 5 of the 250 free Globalping tests per hour for your IP address.
| # | Probe | Result | Handshakes | Connect time min / avg / max | Server address | Output |
|---|
Worked Example
smtp.gmail.com, port 587, from five probes (recorded 6 October 2026). Every probe completed 3 handshakes out of 3, so the port is open from all five. Average connect times: Tokyo 4.64 ms, Falkenstein 6.38 ms, Buffalo 22.74 ms, São Paulo 50.51 ms and Sydney 107 ms. IANA registers 587 as submission, “Message Submission” (RFC 6409).
Same address, very different times. Tokyo and Sydney were both given 142.251.169.108. Tokyo’s fastest handshake took 3.876 ms, so that server is at most 3.876 ÷ 2 × 299.79 = 581 km from Tokyo. Sydney’s 107 ms is therefore mostly the trip from Sydney to a server near Tokyo, 7,811 km away, not a slow port.
The common mistake: testing a port forward on an address that is not really yours. If your router shows a WAN address such as 100.72.15.4, it is inside 100.64.0.0/10, the Shared Address Space for carrier-grade NAT (RFC 6598). That block holds 232−10 = 4,194,304 addresses that providers use between their NAT and customers’ routers. The probes cannot reach it (this tool refuses such addresses), and checking the provider’s shared public address shows the port closed however the router is set, because the provider’s NAT never sends that traffic to you.
Show Work
How a Port Check Decides
Why a Port Shows Closed, and the Common Ports
Ports and the registry. A TCP port number (0–65535) tells a host which program a connection is for. IANA keeps the Service Name and Transport Protocol Port Number Registry under the rules of RFC 6335 (August 2011): System Ports 0–1023 and User Ports 1024–49151 are assigned, Dynamic Ports 49152–65535 never are. A registration is a convention, not a lock: SSH can run on 2222 and anything can run on 443.
A closed result is not always the server. Between a probe and the program sit the server’s own firewall, any network firewall, and the provider. Home connections add two more traps. Behind carrier-grade NAT (100.64.0.0/10, RFC 6598, April 2012) many customers share one public address, so nothing on the internet can start a connection to your router. And some providers block ports to curb abuse; RFC 5068 describes providers blocking outbound port 25. If the check fails, test from inside the network, confirm the program is listening, then work outwards.
Closed or filtered? A closed port answers fast with a reset; a filtered one stays silent until the probe gives up, or returns ICMP type 3 code 13. Silence is common: many firewalls drop rather than reject, and RFC 1812 lets routers be configured not to send code 13 at all.
| Port | IANA service name | IANA description | Reference | Note | |
|---|---|---|---|---|---|
| 20 | ftp-data | File Transfer [Default Data] | |||
| 21 | ftp | File Transfer Protocol [Control] | RFC 959 | ||
| 22 | ssh | The Secure Shell (SSH) Protocol | RFC 4251 | ||
| 23 | telnet | Telnet | RFC 854 | ||
| 25 | smtp | Simple Mail Transfer | RFC-ietf-emailcore-rfc5321bis-43 | Mail between servers. Some providers block outbound port 25 from customer networks (RFC 5068); mail programs submit on 587 instead. | |
| 53 | domain | Domain Name Server | DNS servers must answer over TCP as well as UDP (RFC 7766). | ||
| 80 | http | World Wide Web HTTP | RFC 9110 | Plain HTTP. | |
| 110 | pop3 | Post Office Protocol - Version 3 | |||
| 119 | nntp | Network News Transfer Protocol | RFC 3977 | ||
| 143 | imap | Internet Message Access Protocol | RFC 3501; RFC 9051 | ||
| 389 | ldap | Lightweight Directory Access Protocol | |||
| 443 | https | http protocol over TLS/SSL | RFC 9110 | HTTPS: HTTP over TLS. | |
| 445 | microsoft-ds | Microsoft-DS | |||
| 465 | urd / submissions | URL Rendezvous Directory for SSM / Message Submission over TLS protocol | RFC 8314 | Two registrations share it; RFC 8314 uses it for mail submission over TLS. | |
| 587 | submission | Message Submission | RFC 6409 | Mail submission from mail programs to their provider (RFC 6409). | |
| 636 | ldaps | ldap protocol over TLS/SSL (was sldap) | |||
| 853 | domain-s | DNS query-response protocol run over TLS | RFC 7858 | ||
| 993 | imaps | IMAP over TLS protocol | RFC 3501; RFC 8314; RFC 9051 | ||
| 995 | pop3s | POP3 over TLS protocol | RFC 8314 | ||
| 1194 | openvpn | OpenVPN | |||
| 1433 | ms-sql-s | Microsoft-SQL-Server | |||
| 1723 | pptp | pptp | RFC 2637 | ||
| 1883 | mqtt | Message Queuing Telemetry Transport Protocol | |||
| 3306 | mysql | MySQL | |||
| 3389 | ms-wbt-server | MS WBT Server | Windows Remote Desktop (RDP) listens here by default (Microsoft documentation). | ||
| 5060 | sip | SIP | RFC 3263 | ||
| 5432 | postgresql | PostgreSQL Database | |||
| 5900 | rfb | Remote Framebuffer | RFC 6143 | ||
| 6379 | redis | An advanced key-value cache and store | |||
| 8080 | http-alt | HTTP Alternate (see port 80) | Registered as an alternate HTTP port. | ||
| 8443 | pcsync-https | PCsync HTTPS | Registered to PCsync HTTPS; the registry says what a port is assigned to, not what a given server runs on it. | ||
| 27017 | mongodb | Mongo database system |
Source: IANA Service Name and Transport Protocol Port Number Registry (TCP entries), downloaded 6 October 2026. Where IANA lists no reference the column is blank. Port 80 also has the aliases www and www-http.
About This Tool
Reference: Common Port Numbers.
This open port checker asks probes on the Globalping network (run by jsDelivr) to make TCP handshakes to the host and port you give, 1 to 5 times each, from 3 to 8 probes placed on every continent, on one continent, or by country, city, network or cloud region, over IPv4 or IPv6. It reports per probe whether the handshake completed, how many did, the connect times and the address reached, with the probe’s raw output.
It checks one port on one host, the way a customer or a monitoring service would reach it; it is not a port scanner. Check only systems you run or have permission to test. The common-ports table comes straight from the IANA registry, and a click on any port fills it in.
Privacy: the request goes from your browser to api.globalping.io, not to this site, and only when you press Run. Private, loopback, documentation and carrier-grade NAT addresses are refused before anything is sent. Sources: RFC 9293, RFC 6335, RFC 6598, RFC 1918, RFC 1812, RFC 5068, RFC 6409, RFC 8314, RFC 7766 (rfc-editor.org), the IANA port number and special-purpose address registries, and Microsoft’s Remote Desktop documentation.
Related tools: Ping Test, Traceroute, and IP Lookup.
Frequently Asked Questions
How do I check if a port is open?
Enter the server’s public address and the port and press Run. Each probe tries a TCP three-way handshake: it sends a SYN and waits for a SYN,ACK (RFC 9293 §3.5). A SYN,ACK means a program is listening and nothing in between blocked it, so the port is open from that probe. In our example all 5 probes completed 3 of 3 handshakes with smtp.gmail.com on port 587.
What is the difference between open, closed and filtered?
Open: the server answered the SYN with SYN,ACK. Closed: the host answered with a reset (RST), which TCP sends when no program is listening on that port (RFC 9293 §3.5.2). Filtered: no answer at all, or an ICMP “communication administratively prohibited” (type 3, code 13, RFC 1812), because a firewall dropped the packets. This tool reports both closed and filtered as “no handshake”; the probe’s raw output sometimes tells them apart.
I forwarded the port on my router but it still shows closed. Why?
Check the address you tested. If your router’s WAN address is in 100.64.0.0/10, your provider uses carrier-grade NAT (RFC 6598): you share a public address with other customers, and a forward on your router never receives the traffic. Addresses in 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16 (RFC 1918) are private for the same reason. Other causes: the program is not running, the computer’s own firewall blocks it, or the provider filters that port.
Why is port 25 blocked?
Port 25 carries mail between servers, and some internet providers block outbound port 25 from customer connections to stop infected computers sending spam. RFC 5068 (BCP 134) describes the practice and steers mail programs to the submission port 587 (RFC 6409) or 465 with TLS (RFC 8314). So a failed check of port 25 from a home connection says little about the mail server itself.
What are well-known ports?
RFC 6335 splits the 65,536 TCP port numbers into System (well-known) Ports 0–1023 and User (registered) Ports 1024–49151, both assigned by IANA, and Dynamic Ports 49152–65535, never assigned and used for the client side of connections. IANA’s registry lists 22 for SSH, 443 for HTTPS and 3306 for MySQL, but a registration does not force anything: any program can listen on any port.
Common Use Cases
Test port forwarding for a game or camera
Check your public IP and the forwarded port; if your WAN address starts 100.64–100.127 you are behind carrier-grade NAT.
Confirm a firewall rule
After opening 443 or closing 22, check from 5 probes that the rule works from the internet.
Debug mail settings
smtp.gmail.com answered on 587 from all 5 probes in 4.64 to 107 ms, so a failure from your own network points at your provider or firewall.
Check a database is not exposed
Ports 3306 (MySQL), 5432 (PostgreSQL) and 27017 (MongoDB) should show no handshake from the internet.
Verify a new server
Before announcing a service, make sure its port answers from Europe, the Americas, Asia and Oceania.
CCNA and Network+ study
See the three-way handshake succeed, and learn the well-known, registered and dynamic port ranges (0–1023, 1024–49151, 49152–65535).
Last updated: