Test one public DC++ hub endpoint with the selected Direct Connect protocol and port from the hublist server.
Purpose
The tool makes a bounded TCP or TLS connection for dchub/NMDC, NMDCS, ADC, or ADCS and records reachability, timing, resolved addresses, and an immediate banner or greeting when the service sends one.
When To Use It
- Verify the advertised protocol after changing hub software or ports.
- Check a plaintext-to-TLS migration.
- Confirm an imported hub address before relying on it in a public hublist.
Reading The Results
TCP or TLS connection success is the primary result: the selected endpoint accepted the required socket. A lock, hub name, ADC greeting, or other banner is extra evidence that a Direct Connect service answered immediately.
Limitations
Some valid NMDC or ADC hubs accept a socket without returning an immediate banner, so an empty banner alone is not failure. The bounded check does not complete a full user login, bypass restrictions, or test private and reserved targets.
For protocol examples, mismatch symptoms, and next checks, open Protocol Test.