How to use the port checker
Check whether a public host accepts a TCP connection on a specific port from the Richscripts server. Enter a hostname or public IP address, choose a port from one through 65535, and confirm that you are authorized to test the destination. The result identifies the resolved address actually tested, the requested port, and whether the connection succeeded.
This check attempts one connection and closes it without sending application data. A successful connection is reported as open. A refused connection or a timeout is reported as closed-or-filtered because a short TCP test cannot reliably distinguish every firewall and routing condition. The connection timeout is three seconds, and hostname resolution also has a bounded wait.
Private, loopback, link-local, and reserved network destinations are rejected. When a hostname returns multiple addresses, every returned address must pass the public-address check before the server connects to the first one. The connection uses that resolved address directly. Each client address is limited to ten port checks per hour, within the shared network diagnostics request limit. This tool is for individual checks, not bulk scans.
Frequently asked questions
Does open mean the application works?
No. An open TCP port means a connection was accepted from this server. It does not validate TLS, authentication, HTTP responses, or application health. Follow up with the protocol-specific checks appropriate to your service.
Why does the result differ from my computer?
Firewalls, geographic restrictions, routing, and source-address policies can allow one network location while blocking another. This result reflects the Richscripts server’s path. A local test can legitimately produce a different outcome.
Can this check UDP or my home device?
It checks TCP only. A device behind a home router may require suitable routing and firewall configuration before it is reachable on a public address. Private LAN addresses cannot be tested by this public endpoint.