Network Tools

Port Reachability Checker – Test Open Ports Online (Browser-Safe)

Check whether a port on any host or IP address answers a WebSocket or HTTP request, right from your browser.

Enter a hostname and port to check open ports online and test port accessibility in seconds. This free browser port checker tests one port at a time, runs entirely on your device, and never scans or sends anything through our servers.

Nothing is sent through our servers

Common:

Turn secure off for services that don't use TLS, such as a plain web server on port 8080.

Result
Enter a host and port, then press Check Port.

Reachable means something answered. Unreachable can mean the port is closed or that the service doesn't use this protocol. Only test hosts you own or have permission to test.

What is port reachability?

A port is a numbered door on a computer that a service listens on, such as 443 for secure websites. Port reachability means a connection to that door gets through and something answers. It depends on the service running, the host being online, and nothing in between, such as a firewall, blocking the way. If you are asking is a port open, this tool gives you a quick answer from your own connection.

Reading the Result

Reachable

Something is listening on the port and answered the browser's request. The tool also shows how long the reply took.

Unreachable

The connection failed quickly. The port may be closed (connection refused), or a service there may not speak the protocol you tested.

Timeout

Nothing came back in time. A firewall may be silently dropping the traffic, or the host may be offline or very slow.

Blocked by browser

Browsers refuse web requests to certain ports, such as 22, 25 and 6000, so those can't be tested from a web page. This says nothing about whether the port is open.

WebSocket vs HTTP Testing

Browsers can't open raw TCP connections, so this browser port checker uses the two kinds of connection a web page is allowed to make. Pick the one that matches the service on the port.

HTTP / HTTPS test

Sends a web request to the port. Use it for websites, APIs, dashboards and dev servers. If a web server answers, the port counts as reachable.

WebSocket test

Tries a WebSocket handshake. Use it for real-time services such as chat, live data and game servers. It is reachable only if the server accepts the handshake.

No Scanning, No Servers

This is not a port scanner. It checks one port at a time, only when you ask. The request goes directly from your browser to the address you enter, so nothing passes through our servers and your results are never uploaded, logged or stored. The test also reflects your own network, which is useful when you want to know whether a port can be reached from where you are. Only test hosts you own or have permission to test.

Common Uses

Developers

Confirm that a service, API or WebSocket server is up and reachable after a deploy or a config change.

Network debugging

Find out whether a firewall, router rule or security group is blocking a port you expect to be open.

Local testing

Check that a server on localhost or your local network is listening, and that it can be reached from your device.

Quick checks

Answer the question is this port open from where I am, without installing anything or opening a terminal.

Works on Mobile and Desktop

The checker works in any modern browser on phones, tablets and computers, with nothing to install. On a large screen the settings and the result sit side by side. On a phone they stack, and every control is sized for touch. Checking from your phone is a quick way to see whether a service is reachable on mobile data as well as on your home Wi-Fi.

Frequently Asked Questions

How do I check if a port is open?
Enter the hostname or IP address and the port number, pick HTTP / HTTPS or WebSocket, and press Check Port. The result appears straight away. Use HTTP for web services and WebSocket for real-time servers.
Why can't this tool test any port or protocol?
Web pages aren't allowed to open raw network connections. A browser can only make web requests and WebSocket connections, so the tool can only tell whether a port answers one of those. It can't test services such as SSH, SMTP or databases.
Does Unreachable mean the port is closed?
Not always. The browser doesn't say why a connection failed. The port may be closed, or something may be listening that doesn't speak HTTP or WebSocket. A Timeout usually points to a firewall dropping the traffic.
Why is my port marked as blocked by the browser?
Browsers keep a list of ports they won't connect to from a web page, to stop pages from misusing services such as mail and SSH. These ports can't be tested here, and the result doesn't say whether they are open.
Can I test a service on my local network or localhost?
Yes. Enter localhost or a local IP address. Turn off Use secure connection for services without TLS. Some browsers ask for permission before a public website can reach local devices.
Why can't I test http or ws addresses?
This page is served over https, and browsers block insecure connections from a secure page, except to localhost. Use the secure option, or put TLS in front of the service.
Is this a port scanner? Is my data sent anywhere?
No. It tests one port at a time, and only when you press the button. Requests go straight from your browser to the address you enter, and nothing is sent through our servers or stored. Only test hosts you own or have permission to test.