Hub TCP Connect Tool 🇬🇧 🇨🇳 🇮🇳 🇪🇸 🇨🇿 🇩🇪 🇳🇱 🇫🇷 🇮🇹 🇵🇱 🇷🇴 🇷🇺

Created: 2026/06/26 19:26:35 America/Chicago

By: admin

What This Tool Checks

The TCP connect tool attempts one bounded Direct Connect connection check from the hublist server to a public host and port.

Use it when ping is blocked but you need to know whether the hub service port itself is reachable from outside.

For hublist indexing, an open TCP port is more important than ICMP ping because DC++ clients need the service port to accept connections.

Try the exact port published in your hub address first.
Common hub ports include 411, 412, 1411, 1511, and 4111, but operators can choose custom ports.
A failed connection can indicate firewall filtering, NAT issues, or a stopped hub service.

Check whether a specific public TCP port accepts a connection from the hublist server.

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

TCP Port Enter a TCP port from 1 to 65535.

Solve CAPTCHA

Submit a public Direct Connect hub for hourly checks, searchable indexing, and inclusion in the public NMDC, NMDCS, ADC, and ADCS hublist files.

Test whether a public DC++ or Direct Connect hub hostname responds to ICMP ping, then review packet loss, latency, and DNS resolution.

Look up public WHOIS, registrar, domain, and network ownership information for Direct Connect hub hostnames and IP addresses.

Run dig-style DNS checks for Direct Connect hub hostnames and inspect A, AAAA, CNAME, MX, NS, SOA, and TXT records.

Review A, AAAA, CNAME, MX, NS, SOA, and TXT records for public Direct Connect hub hostnames from the hublist server.

Check reverse DNS PTR hostnames for public IP addresses used by Direct Connect and DC++ hubs.

Test whether a public DC++ hub endpoint accepts dchub, NMDC, NMDCS, ADC, or ADCS connections from the hublist server.

Inspect public TLS certificate details for secure Direct Connect endpoints, NMDCS hubs, ADCS hubs, or related hostnames.

Trace the network path from the hublist server to a public Direct Connect hub hostname or IP address for routing diagnostics.

Run a bounded public TCP check against common Direct Connect hub ports and see which NMDC, NMDCS, ADC, or ADCS ports appear reachable.