dnswatchdog.iodocs

Certificates

Monitor SSL/TLS certificates across your DNS estate — track expiry dates, detect hostname mismatches, identify weak keys, and manage certificate lifecycle.

Open Certificates →

A Certificate represents an SSL/TLS certificate discovered during HTTPS scanning. DNS Watchdog scans every HTTPS-capable record for its certificate and analyses it for expiration, hostname mismatches, weak keys, and chain issues.

Certificates are deduplicated by fingerprint — if multiple records serve the same certificate (e.g. a wildcard certificate used across many subdomains), it appears once with links to all associated records.

The Certificates page showing SSL/TLS certificates with issuer, expiry date, and status indicators

Key fields

Identity

FieldDescription
HostnameThe hostname this certificate was retrieved from
PortThe port scanned (typically 443)
Common NameThe CN from the certificate subject
Subject Alternative NamesAll SANs listed on the certificate — the hostnames the certificate is valid for
Associated RecordsAll DNS records that serve this certificate

Subject details

FieldDescription
OrganisationOrganisation name from the certificate subject
Organisational UnitOU from the certificate subject
CountryCountry code from the certificate subject
StateState or province from the certificate subject
LocalityCity or locality from the certificate subject

Issuer details

FieldDescription
Issuer Common NameThe CA that issued this certificate (e.g. "Let's Encrypt", "DigiCert")
Issuer OrganisationOrganisation of the issuing CA
Issuer CountryCountry of the issuing CA

Validity and expiration

FieldDescription
Valid FromCertificate start date
Valid ToCertificate expiration date
Is ExpiredWhether the certificate has already expired
Days Until ExpiryCountdown to expiration — negative if already expired
Duration DaysTotal validity period in days

Technical details

FieldDescription
Serial NumberUnique serial number assigned by the CA
Signature AlgorithmAlgorithm used to sign the certificate (e.g. SHA256withRSA, SHA384withECDSA)
Fingerprint (SHA-256)Unique hash used for deduplication across records
Key TypeCryptographic key type: RSA or ECDSA
Key SizeKey length in bits (e.g. 2048, 4096 for RSA; 256, 384 for ECDSA)
Hostname ValidWhether the certificate matches the hostname it was retrieved from
Is Self-SignedWhether the certificate is self-signed (not issued by a trusted CA)

Certificate chain

FieldDescription
Certificate ChainFull chain of certificates from leaf to root
Chain LengthNumber of certificates in the chain

Management

FieldDescription
Scan Statuspending, completed, or failed
Scan ErrorError details if the certificate scan failed
IgnoredWhether this certificate has been marked as ignored
Ignored ReasonUser-provided reason for ignoring (e.g. "internal service, self-signed is expected")
Ignored ByWho ignored the certificate and when

Associated issues

IssueSeverityDescription
Expired CertificateCriticalCertificate has expired — browsers will show warnings and may block access entirely
Certificate Hostname MismatchCriticalCertificate does not match the hostname — indicates misconfiguration or a potential security issue
Certificate Expiring SoonWarningCertificate will expire within 30 days — renew to avoid service disruption
Weak Certificate KeyWarningRSA key under 2048 bits or ECDSA key under 256 bits — vulnerable to brute-force attacks
Self-Signed CertificateInfoNot trusted by browsers — consider using a certificate from a trusted CA

Actions

  • Ignore — mark a certificate as ignored with a reason (e.g. internal service)
  • Unignore — remove the ignored status
  • Bulk ignore / unignore — manage multiple certificates at once

Common tasks

How do I find certificates expiring soon?

The Certificates page shows days until expiry for each certificate. Sort by expiry date to see which certificates need renewal first. Certificates expiring within 30 days are flagged with a Certificate Expiring Soon warning.

How do I find all domains using a specific certificate?

Each certificate entry shows its Subject Alternative Names (SANs) and associated records. Click a certificate to see every DNS record that serves it — useful for understanding the blast radius of an expiring wildcard certificate.

How do I handle self-signed certificates?

If a self-signed certificate is expected (e.g. an internal service), use the Ignore action with a reason like "internal service, self-signed is expected". This suppresses the info-level issue without hiding other certificate problems.

How are certificates discovered?

DNS Watchdog scans every record that responds on port 443 (HTTPS). The SSL/TLS handshake is performed and the full certificate chain is captured and analysed. Certificates are deduplicated by SHA-256 fingerprint.

On this page