IT
OmnvertImage • Document • Network

Port Checker (Single Port)

Test if a TCP port is open, closed or filtered on a public host.

Paste a URL (https://example.com) — we’ll extract the host automatically.

Common ports

Tap to fill the port field.

Result

Single-port reachability with timeout and connect time.

Ping this hostTraceroute
Run a check to see details here.

About

This port checker tests a single TCP port on a public host and reports whether it’s open, closed or filtered, along with connect time and the resolved IP. It’s built for quick diagnostics: verifying a new firewall rule, checking if a service is reachable from outside your network, or confirming that a port forward/DMZ rule is actually exposed. Port ranges are intentionally blocked and timeouts are short to keep probes safe.

Use it before asking someone to allowlist you: enter the host and port, copy the result as JSON, and share the connect timing plus any error notes. If the status is filtered, a middlebox or firewall likely dropped the SYN/ACK; if closed, the host actively refused the connection or nothing is listening. Open indicates a completed TCP handshake, not full application health—pair this with HTTP ping or a service-specific check when needed.

Because SSRF protections reject private/reserved addresses, you can’t accidentally scan internal networks. Tests are single-target, single-port to reduce noise on the destination and to respect rate limits. Timeouts default to ~1.5s (configurable up to 3s), giving fast feedback without hanging your tab.

Common scenarios: confirming 443/8443 reachability to a reverse proxy, testing 22/2222 before enabling SSH from the internet, checking whether CGNAT blocks inbound connections, or verifying that a port forward on home broadband really exposes the intended device. Results are formatted for quick copy/paste into tickets and runbooks.

If you see inconsistent results, repeat the check from multiple networks—some ISPs filter uncommon ports or apply intrusion prevention that can rate-limit successive connects. Combine with traceroute or ping to see where filtering may start if the TCP handshake never completes.

FAQ

What do open/closed/filtered mean?
Open = TCP handshake succeeded. Closed = connection refused. Filtered = timeout/drop, often due to firewall/NAT.
Can I scan a range?
No. Only a single port per request is allowed to prevent abuse and reduce load on the target.
Does open mean the app works?
It only confirms the TCP handshake. The application could still return errors—pair with HTTP or app-specific checks.
Why is my LAN host blocked?
Private/reserved addresses are rejected to prevent SSRF and internal scans. Use the tool only for public hosts.
Why does it say filtered?
The connection timed out. A firewall, IDS/IPS or upstream filter likely dropped the packets instead of refusing them.
Is repeated testing safe?
Tests are short and single-port, but some providers rate-limit unusual ports. Space out retries if you see throttling.

Related Tools