Port Scan Tool

Check a short, explicit list of public TCP ports used by a DC++ or Direct Connect hub without running a broad network scan.

Purpose

The tool makes bounded TCP connection attempts to the submitted public host and port list, then reports each port as open or closed with timing and error context.

When To Use It

  • Compare the ports published for NMDC, NMDCS, ADC, or ADCS.
  • Check firewall, NAT, or VPS security-group changes.
  • Confirm that an old listener closed after a protocol or port migration.

Reading The Results

An open row means a TCP socket was accepted from the hublist server. A closed or timed-out row points to no listener, filtering, routing, or forwarding trouble. Test the advertised hub port first.

Limitations

This is a bounded hub-port checker, not a vulnerability scanner. An open socket does not identify the service or prove a valid Direct Connect handshake. Only public targets and the limited submitted port set are accepted.

For safe examples and port troubleshooting, open Port Scan Tool.

Hub Port Scan Tool

Run a small bounded TCP connection check against public hub ports to see which common Direct Connect ports appear open.

Enter a public hostname, IP address, or hub-style address such as dchub://example.com:411.
Optional comma-separated ports. Leave empty for common DC hub ports. Maximum 20 ports.

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

Parent Page