NetDig/Port Checker

Port Checker

Test if TCP ports are open or closed on any host or IP. Verify port forwarding, firewall rules, and server connectivity.

port-check.sh
Testing connection…
common-ports.sh
Scanning ports…

Common TCP Port Numbers

PortServiceDescription
21FTPFile Transfer Protocol
22SSHSecure Shell — remote access
23TelnetUnencrypted remote access (insecure)
25SMTPSimple Mail Transfer Protocol — sending email
53DNSDomain Name System
80HTTPHypertext Transfer Protocol — web traffic
110POP3Post Office Protocol — receiving email
143IMAPInternet Message Access Protocol — email
443HTTPSHTTP Secure — encrypted web traffic
445SMBServer Message Block — Windows file sharing
587SMTP/TLSSMTP with TLS — modern email submission
993IMAPSIMAP over SSL
995POP3SPOP3 over SSL
3306MySQLMySQL database server
3389RDPRemote Desktop Protocol — Windows remote access
5432PostgreSQLPostgreSQL database server
6379RedisRedis in-memory data store
8080HTTP AltAlternative HTTP port — development/proxies
8443HTTPS AltAlternative HTTPS port
27017MongoDBMongoDB database server

Frequently Asked Questions

Our server attempts a TCP connection to the specified host and port with a 5-second timeout. If the connection succeeds, the port is marked open. If it times out or is refused, the port is marked closed or filtered. Note: this tests from our server's perspective, not your own network.
Open: a service is actively listening on that port and accepted the connection. Closed: the host responded but no service is running on that port. Filtered/Timeout: a firewall is blocking the connection and not responding at all. A closed port returns a TCP reset; a filtered port just times out.
Set up your port forwarding rule in your router's admin panel, make sure the target service is running on the internal server, then enter your public IP address (found on the IP Lookup page) and the forwarded port number here. If it shows open, port forwarding is working correctly.
Common causes: your firewall (Windows Firewall, iptables, UFW, cloud security groups) is blocking the port; port forwarding is misconfigured on your router; the service is binding to 127.0.0.1 instead of 0.0.0.0; or your ISP is blocking the port (ISPs often block ports 25, 80, and 443 on residential connections).