TLS Certificate Tool

TLS Certificate

Created:: 2026/07/02 19:41:27 America/Chicago
By:: admin
Modified:: 2026/08/06 14:22:10 America/Chicago
By:: admin

Inspect the TLS certificate presented by a public NMDCS or ADCS endpoint used by DC++ and Direct Connect clients.

Purpose

The tool opens a bounded TLS handshake and reports the certificate subject, issuer, validity dates, days remaining, alternative names, and negotiated TLS details when available.

When To Use It

Check a certificate warning reported by secure-hub users.
Verify a renewal before or after replacing a certificate.
Confirm the hostname and port before moving from NMDC or ADC to NMDCS or ADCS.

Reading The Results

The validity window shows whether the certificate is current. Subject alternative names must cover the hostname clients use. Issuer and protocol details help distinguish a self-signed certificate, a missing chain, and a TLS negotiation problem.

Limitations

A successful TLS handshake does not prove that the endpoint completes a Direct Connect login. Client trust policy can differ, and some communities deliberately use self-signed certificates. Only the submitted public endpoint is inspected.

For certificate examples and layered troubleshooting, open TLS Certificate.

Hub TLS Certificate Tool

Inspect the certificate returned by a public TLS-enabled hub or web endpoint.

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

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

Parent Page

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.

DC++ Active Mode Check

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

Protocol Test Tool

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

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.