Use the port checker for a specific public service
This checker attempts TCP connections from the site server to a public address. Choose Single port for one service or Fixed preset for a small, explicit list. Enter the destination, choose the address family, provide a whole port number from 1 to 65535, and start the check. A result describes that particular connection attempt. It does not enumerate every open service, measure your browser's route, or certify that the application behind a reachable port works correctly.
Read more
Choose the port checker target
Use a public IPv4 or IPv6 address, or an ordinary public hostname. Do not paste a full URL, a path, or an address with a port appended. The checker takes a single port in its separate field or shows every port in the chosen preset. Private, loopback, link-local, shared-address, documentation, and other unsupported special-use targets are rejected. This remote server cannot use your household's 192.168.1.1 address to identify your particular router.
For hostnames, Google Public DNS supplies the selected A or AAAA family. The server follows aliases, validates the public addresses and selects one literal target. That resolution step remains visible in the report.
The example fills a public resolver and TCP port 443 without starting. Use my IP retrieves the selected family’s observed address through ipify, then lets you review it before probing. It does not establish that an inbound service exists.
Select the port and IP version
Single mode accepts one integer port; fixed presets check four web ports or six common ports. No custom port range or UDP scan is available. Select the family matching your literal address.
Run a fixed port checker preset
The web preset contains TCP ports 80, 443, 8080, and 8443. The common preset contains 22, 25, 80, 443, 3389, and 8080. These names summarize conventional uses, not detected applications. The checker displays the complete list before submission. It checks one port at a time, reusing one validated public address selected at the start, so DNS rotation cannot silently change the destination between rows.
Every received row keeps its own outcome, duration and observation time. Pending and not-tested rows remain explicit; stopping does not label unfinished ports closed.
Each TCP attempt has a five-second deadline. Presets have a thirty-five-second server budget including resolution, so a partial response can leave ports untested.
What the port checker sends
After validation, the server initiates bounded TCP connections and closes each socket once the outcome is known. No banner, application login, certificate or UDP response is inspected.
Read the port checker outcome
Read the entered target, selected literal address, port, server origin, resolution method and observation time with every outcome. Duration concerns that connection attempt, not your browser’s full request.
Read more
Port checker connection success
TCP connection established means the server completed TCP establishment and closed the connection. It does not identify the listening program, verify HTTPS or certify secure configuration.
Port checker connection refusal
Connection refused records an active refusal during the attempt. The listener, host or an intervening policy may be responsible; the result does not prove every port on the device is closed.
Port checker timeout and unreachable results
Timeout means no connection completed within five seconds. Filtering, routing, congestion or a silent host can cause it. Missing replies do not identify one definite fault.
Port checker environment restrictions
Hosting restrictions can prevent a valid check. Cloudflare’s TCP socket documentation describes environment limits. Restricted or unavailable outcomes leave the port state unestablished.
The summary counts connections established separately from refused, timed out and unavailable attempts. Read incomplete rows before interpreting the preset as a complete inventory.
Port checker limits when troubleshooting incoming access
Behind ordinary NAT, inbound access can require a mapping to the correct private device and port. Check the listener, local firewall and router rule. A successful local connection does not prove external reachability.
Read more
With carrier-grade NAT, subscribers may not control the provider’s inbound mappings. Compare the router’s WAN address with external observations and ask the provider about inbound access. No unanswered probe alone proves CGNAT.
Stopping and clearing a port checker request
Stop cancels local waiting. The server closes sockets when an abort reaches it, but a connection may already have occurred. Clear prevents late results from returning to the display; neither removes destination logs.
The protocol reference is TCP in RFC 9293. Common names come from IANA service assignments; names are associations, not identification of a running program. Use DNS lookup for records and ping for separate reply evidence.