Port Scanner
See which ports on a host accept connections from the internet.
Scanned from our server in Newark, US · TCP · up to 25 ports
Standing by. Press Scan to try 11 ports from our server in Newark, US.
TargetPlace approx.
· · ·
rDNSlooked up when you scan
Netafter the lookup
Placeafter the lookup
Distance from our server: after the lookup
Openports
Waiting for a scan
Counts11 to try
Heads-uprule of thumb
Open ports that rarely should face the internet (remote desktop, databases, file sharing, Telnet) are flagged here and on their screen.
A rule of thumb from what the port is usually for.
Lanes · 6 at a time2 s
Each lane waits up to the 2 s timeout
Routeapprox.
Our server, NewarkTarget (approx.)
What answered
- Open ports that introduce themselves show their first line here
Every port
11 ports on 216.73.216.94
Each port is tried with an ordinary TCP connection from our server in Newark, US. A port open from there could still be blocked from elsewhere.
Certificate
on open TLS portsTest a port from other countries
Our scan comes from one place, our server in Newark, US. Ask probes on six continents to connect to one open port and see whether it’s reachable from there too.
Scan a host first. Any port that’s open can then be tested from other countries.
Recent scans in this browser
Kept on this device, never sentWhat the port scanner does
The port scanner checks which TCP ports on a host or IP address accept connections from the internet. Our server in Newark, US tries an ordinary TCP connection to each port you choose, six at a time, and reports whether it’s open, closed or filtered, how long the host took to answer and what answered.
Use it after setting up port forwarding for a game or media server, to confirm a firewall rule, or to check that database and remote-desktop ports aren’t reachable.
How to use the port scanner
- Enter a host name or IP address, or use your own IP.
- Choose a group (Common, Server, Game, Application or P2P), or type up to 25 ports of your own, such as
80, 443, 8000-8010. Small scans stay quick and fair. - Press Scan. Each port gets up to two seconds to answer.
Understanding the results
Open means a program accepted the connection and the internet can reach it. Closed means the host refused at once: it’s reachable, but nothing listens there. Filtered means no reply within two seconds, usually because a firewall dropped the attempt. A skipped port wasn’t tried: the scan ran out of time.
On open ports we take one light look at what answered: a service’s greeting line, a web server’s status line and Server header, or the certificate on TLS ports, with its issuer, expiry and name match (the SSL certificate checker shows it in full). A heads-up marks an open port that rarely needs to face the internet: a rule of thumb from the port number, not a security audit.
Scan a host again to compare with your last scan in this browser. A PDF report carries a reference anyone can verify on our site, and email alerts for registered users are coming soon.
Port scanner questions
Is it OK to scan any host?
Only scan hosts you own or have permission to test. Each host can be scanned 8 times in 10 minutes, by everyone together.
I forwarded a port. Why is it still closed or filtered?
The program may not be running, or the forward points at the wrong device. If your provider shares one public IP between customers (CGNAT), forwarding can’t work.
Can it check UDP ports?
No. UDP has no handshake, so an open UDP port looks like a filtered one. The Game group lists TCP ports only.
Why is everything filtered on my home IP?
Home routers drop connection attempts they didn’t ask for: the safe default. Only ports you forward should show open.
Which open ports are risky?
Databases (3306, 5432, 27017), remote desktop (3389, 5900), Windows file sharing (445) and Telnet (23) rarely need to face the internet. Close them or limit who can connect.
Can I test a port from other countries?
Yes. Globalping probes on six continents can try an open port from your scan, since it may still be blocked elsewhere.