Tool guide limitationsGuides explain the intended workflow but cannot cover every device, provider or operating condition.
Interfaces and external services can change. Follow the current on-screen controls, check dates and vendor documentation, and verify important results independently before acting on them.
Important: Do not rely on this result alone for purchasing, configuration, security, safety, compliance, contractual or fault-diagnosis decisions. Results can be incomplete, delayed, misleading or wrong. Verify important findings with the relevant provider, manufacturer documentation and an appropriate independent test or qualified professional.
Technical diagnostics
Port Test guide
Check whether the hosted service can make a TCP connection to an authorised public hostname or IP and port.
Open Port TestWhat you need
- Public hostname or IP address
- TCP port
How to use it
- 1Confirm you are authorised to test the destination.
- 2Enter the public destination and port.
- 3Run the test.
- 4Review the open, closed or unavailable result.
Understanding the results
- Open confirms only that the hosted test source connected at that moment.
- Closed or timed out can reflect filtering, routing or the service state.
Recommended next actions
- Compare with a permitted test from the affected network and check firewall logs.
Common problems
- Private addresses are blocked; firewalls may treat the hosted source differently from your device.
Privacy and security
- Only public lookup data is requested. Avoid entering internal names, credentials or confidential notes.
Worked example
- Scenario
- Checking a public HTTPS service
- Example input
- example.com on TCP 443
- How to read it
- Open means the hosted service reached port 443; it does not validate the application behind it.
Limitations
- The test does not originate from the end user's network.
Do not rely on one result for a production, security, safety, purchasing or contractual decision. Verify important findings independently.