How to Test a TCP Connection to a Public Host

What the TCP test measures

Ping Test measures the elapsed time needed to establish TCP connections to a public host. It helps you check whether a selected host and port accept TCP connections and compare the timing of several attempts. This is a connection-establishment check, not an ICMP ping, a general round-trip measurement, or proof that the host or service is healthy.

How to configure and run it

1. Enter a host name, or leave the host field empty to use the default example.com value. The host must be non-empty when the run is processed. 2. Enter a port, or keep the default 443. The value is converted to an integer and must be from 1 through 65535. 3. Enter an attempt count, or keep the default of 3. The value is converted to an integer and must be from 1 through 5. 4. Start the test. It uses network connections for the TCP attempts, and this behavior is supported by the tool's enabled network access; each attempt has a 3-second timeout. 5. Read the returned timing and outcome information. The run also requires a supplied, prevalidated public target address, so a non-empty host by itself does not ensure that connection attempts will begin. If the port or attempt count cannot be converted to an integer, the operation stops before attempting a connection.

How to interpret the output

Successful connection times appear in milliseconds and are rounded to two decimal places. The average is calculated from successful connections and is displayed with the same two-decimal precision. The unsuccessful-attempt percentage is rounded to one decimal place, so the displayed figures can contain different numbers of decimal places by design. A run may include both successful and unsuccessful attempts; in that situation, the result can show timing statistics for the successful connections alongside the resulting loss percentage. Use the average to understand completed TCP establishments, rather than treating it as a duration for attempts that did not connect. When no attempt succeeds, the operation fails and reports 100% loss. Connection errors, the selected port, and target availability can affect the outcome, so the result describes the attempts made by this test rather than the overall condition of a host or service.

Worked example

A user checks whether TCP connections to example.com on port 443 can be established across three attempts.

Enter example.com as the host, 443 as the port, and 3 as the attempt count, then start the test.

The result may list successful and unsuccessful attempts, successful times in milliseconds rounded to two decimal places, an average with two decimal places, and an unsuccessful-attempt percentage with one decimal place. The outcome depends on the connection attempts.

Limitations

• The check is limited to TCP connection establishment for a supplied, prevalidated public target; it can fail when no attempt succeeds and does not verify overall service health.

Common errors

• A port or attempt count containing a value that cannot be converted to an integer stops the operation before connection attempts begin. Correct the entry to a whole-number port from 1 to 65535 or a whole-number attempt count from 1 to 5.

FAQ

Can I test any website with this tool?

Only when the host is non-empty and a supplied, prevalidated public target address is available for the run. Under that condition, the test measures TCP connection attempts to the target rather than checking general website health.

What port values can I enter?

Use an integer from 1 through 65535. The operation stops before making connection attempts when the port cannot be converted to an integer or falls outside the accepted range.

What happens when a connection attempt fails?

A mixture of outcomes can produce successful timing statistics and a loss percentage. If no attempt succeeds, the operation fails and reports 100% loss.