Hub Protocol Test Tool
The hub protocol test tool opens a bounded public connection from the Public DC Hublist server to a selected Direct Connect endpoint. It helps operators confirm that the advertised dchub, NMDC, NMDCS, ADC, or ADCS service is reachable from outside their own network.
When To Use This DC++ Tool
Use it after changing hub software, updating firewall rules, moving a hostname, switching to TLS, or importing a hub from another public hublist provider. A successful test means the selected protocol port accepted a TCP or TLS socket; a returned banner gives extra evidence that a hub service answered immediately.
Why It Helps Direct Connect Hub Owners
This is more specific than a basic ping because DC++ clients need the protocol port itself to be reachable. It is also safer than a broad scan because it tests one selected protocol and one selected port only.
Safe Protocol Testing Notes
Leave the port empty to use the common default for the selected protocol, or enter the exact port published in the hub address. Private, local, reserved, and documentation networks are blocked, and the tool does not run shell commands from user input. Some ADC or NMDC hubs may accept the socket without returning an immediate banner, so review TCP/TLS status together with ping, DNS, TLS, and port-scan results.