Ping Tool

Check whether the Public DC Hublist server can resolve and ping a public DC++ hub host before you investigate its Direct Connect service port.

Purpose

The tool sends a small, bounded ICMP probe to a public hostname or IP address. It reports resolved addresses, packets sent and received, packet loss, minimum, average, and maximum latency, plus bounded raw output.

When To Use It

  • Check a hub that suddenly appears offline.
  • Confirm how the hublist server sees a hostname after a DNS or hosting change.
  • Compare packet loss or latency with a test from your own network.

Reading The Results

Received packets show that the host answered ICMP from this server. Loss and latency can point to filtering, congestion, an overloaded host, or a long route. The resolved-address list confirms which public IPv4 or IPv6 target was tested.

Limitations

ICMP reachability does not prove that an NMDC, NMDCS, ADC, or ADCS login port is open or that a Direct Connect handshake will succeed. Some healthy hosts block ICMP completely. Private, local, reserved, and documentation networks are rejected.

For field instructions, examples, result interpretation, and recovery steps, open Ping Tool.

Hub Ping Tool

Send 10 ICMP packets to a public host and review packet loss, latency, and DNS resolution details.

Enter a public hostname, IP address, or hub-style address such as dchub://example.com:411.

Complete the CAPTCHA challenge to protect this form from automated abuse.

Parent Page