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

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

By: admin

What This Tool Checks

The reverse DNS tool maps a public IP address back to its PTR hostname when the network provider has configured reverse records.

Use it when validating VPS identity, investigating provider reputation, or comparing a hub IP with the hostname shown by hosting tools.

Reverse DNS is not required for every DC++ hub, but it often helps with operational trust, abuse handling, and provider troubleshooting.

PTR records are controlled by the IP owner or hosting provider, not always by the domain owner.
Missing PTR data does not automatically mean the hub is offline.
A mismatch can reveal stale hosting records or a recently moved server.

Resolve public hub IP addresses back to PTR hostnames when reverse DNS is configured.

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

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.

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