Network & Domain

TCP Port Check

Test a public hostname on a restricted set of common service ports.

Read the guide

Run the tool

JVR Software’s server processes the public target you enter. The diagnostic is rate-limited. Use a system you own or are authorised to check.

More information

Back to the tool

What it is and when to use it

TCP Port Check tests whether one supported service port on a public hostname accepts a connection from JVR Software. Use it to verify a service you manage after a planned change, check that a public listener is reachable, or document a reachability difference for your hosting provider.

How it works

The checker first resolves the hostname and rejects private and reserved addresses. It then attempts a single TCP connection to the requested port with a short timeout. The result reports whether that connection opened, how long the attempt took and, when available, the connection error.

How to use it

  1. Use only a hostname you own or are authorised to diagnose.
  2. Enter the one port your service is supposed to use and run the check.
  3. Compare the result with the application and firewall configuration for that listener.

Worked example

After moving your own HTTPS endpoint, check its expected port 443. If it accepts a connection but the website still fails, use SSL Certificate Checker or URL Status Checker to examine the next layer instead of assuming the TCP result proves the site works.

Reading the result

Reachable means a TCP handshake completed from this server's network. A refusal can mean the destination rejected the connection or no service was listening. A timeout can reflect network filtering, a route problem or a busy endpoint.

For an HTTPS service you administer, a successful TCP connection on its known port is only the first check. Follow it with SSL Check for the expected hostname and URL Status for the intended public page. The three tests measure connection establishment, certificate presentation and HTTP response independently.

Common mistakes and limits

The checker does not identify service versions, log in, test weaknesses or scan ranges. A success does not show that a service speaks the expected protocol. Keep administration ports private unless your approved network design explicitly requires public reachability.