Domain expiry
PeakNode determines the registrable domain, queries RDAP first and Whois otherwise, and shows the registration date, last update, expiry date, registrar and nameservers. If the registry, the body that manages the domain extension, does not provide an expiry date, the portal points out the missing domain data, and a reminder for the domain is not possible.
Certificate expiry
PeakNode reads the certificate via TLS directly from the host, on port 443 or the SSL port you enter. It also reads an expired or self-signed certificate, because it is precisely its date that should be shown in the portal.
Reminders with the lead time you choose
For the domain and the certificate you set separately when the reminders start and which channels they go to. Within the lead time, PeakNode repeats the notification at intervals of roughly a third of the lead time. The wording, for example: Your “example.org” domain name SSL is expiring in 14 days.
Warning when renewal is at risk
For Let's Encrypt certificates, PeakNode checks whether all names in the certificate still point to the same server as the main domain. If one points elsewhere, automatic renewal through your own web server is likely to fail, and you find out while the certificate is still valid. A short-lived certificate that has not yet been renewed shortly before expiry is reported as well.
Notification after expiry
Once a date has passed, the “has expired” notification is always sent. If, on the other hand, only the query fails, PeakNode does not infer an expiry from an old state: it retries the query every hour, up to six times, and keeps the known data.
Status per domain
The detail page sums up the status in one phrase, for example “domain and certificate valid”. The remaining days are also available in the Prometheus export as peaknode_domain_ssl_days_remaining and peaknode_domain_registration_days_remaining, see API and webhooks.