DC++ Active Mode Check

Active Mode

Created:
By:
admin
Modified:
By:
admin

Check whether the public TCP listener configured in your DC++ client appears reachable for Direct Connect active mode.

Purpose

The tool tests the submitted public host and active-mode TCP port from outside your local network. Optional UDP and TLS fields keep the settings together and explain which parts can be checked from a web request.

When To Use It

  • Switch from passive mode to active mode.
  • Verify router forwarding, a local firewall, a VPN-forwarded port, or a changed public address.
  • Investigate small search result sets or failed peer-to-peer downloads.

Reading The Results

An open TCP result means this server reached the listener. A closed or timed-out result points to the client, router, firewall, VPN, CGNAT, ISP filtering, or an incorrect address. An optional TLS listener is reported separately.

Limitations

The page cannot prove UDP active-search reachability without a real DC++ client reply, so the UDP value remains a manual configuration check. An open TCP port also does not prove that every peer can connect or that the client advertises the same address and port.

For forwarding examples, passive-mode context, and recovery steps, open Active Mode.

Hub Active Mode Check

Check whether your DC++ client listening ports appear reachable from outside your network.

Enter the public hostname or IP address that other DC++ users should reach when your client runs in active mode.
Enter the TCP port configured in your DC++ client active-mode connection settings.
Optional. Enter the UDP search port from your client settings. The page records it and explains the manual check because UDP cannot be proven without a listening client reply.
Optional. Enter the secure transfer or TLS port when your client exposes a separate encrypted-transfer port.

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

Parent Page

Direct Connect Hub Guide - DC++ Hublist Profiles

Learn what a Direct Connect hub is, how DC++ hublist profile pages work, and how to read address, protocol, users, share, reliability, and status data.

Related Hub Tools

Add Your DC Hub To The Public DC++ Hublist

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

 My IP Information

View the IPv4 or IPv6 address that reached this page, together with locally resolved ISP, city, region, and country details.

 Ping Tool

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

 WHOIS Tool

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

 DNS Dig Tool

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

 DNS Overview Tool

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

 Reverse DNS Tool

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

 TCP Connect Tool

Test whether a specific public Direct Connect TCP port accepts connections from the hublist server for NMDC, NMDCS, ADC, and ADCS hubs.

 Protocol Test Tool

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

 TLS Certificate Tool

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

 Traceroute Tool

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

 Port Scan Tool

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