Hub Traceroute Tool

Created: 2026/07/02 19:41:27 America/Chicago

By: admin

Modified: 2026/07/17 08:40:53 America/Chicago

By: admin

What This Tool Checks

The traceroute tool shows the network hops between the hublist server and a public hub target when intermediate routers reply.

Use it when ping or TCP checks suggest routing problems, long paths, upstream filtering, or regional connectivity issues.

Traceroute gives hub owners a wider view than a single ping result, especially when the route fails before reaching the server.

Some networks hide or rate-limit traceroute replies, so missing hops are not always failures.
Compare traceroute with ping, TCP connect, and port scan results.
Long routes can explain high latency even when the hub is technically online.

Trace the network path from the hublist server to a public hub hostname or IP address.

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

Solve CAPTCHA

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

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 specific public Direct Connect TCP port accepts connections from the hublist server for NMDC, NMDCS, ADC, and ADCS hubs.

Check whether your DC++ client listening port appears reachable from the public internet for active mode.

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.

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