Submit a public Direct Connect hub for hourly checks, searchable indexing, and inclusion in the public NMDC, NMDCS, ADC, and ADCS hublist files.
View the IPv4 or IPv6 address that reached this page, together with locally resolved ISP, city, region, and country details.
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.
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.