SSL certificate expiry alerts

SSL certificate expiry alerts is an ongoing (monthly) service: we regularly read the certificates on your domains and subdomains (HTTPS endpoints) and warn in advance as the expiry date approaches — at several thresholds (e.g. 30, 14, 7, 1 day) so you have time to renew. We also catch basic validity issues: certificate for the wrong domain, incomplete chain, already expired. Honestly about the essence: this is watching the date and alerting, NOT renewing and NOT configuring — we do not issue or renew the certificate for you (that is done by your certificate authority, hosting or control panel) and do not configure TLS on the server; remediation and renewal are your area or separate work. And honestly about scope: this is control of the date and basic validity, NOT a full TLS-configuration audit (protocols, ciphers, vulnerabilities) — that is a separate security task. Coverage is only the configured domains and subdomains; when new ones are added they must be entered into the list together with us. Useful even with auto-renewal (Let’s Encrypt etc.): auto-renewal sometimes silently breaks, and then the certificate expires anyway — our alerts serve as a backstop and catch exactly that case. Someone must react to an alert — renew. An important boundary: this is control of the certificate's expiry, not its issuance, renewal, TLS configuration or a security audit. Honest antisell: if you have a single site with reliable auto-renewal and your host's own alerts, a routine self-check may be enough and a separate service is not needed; it pays off when there are many domains and subdomains. Picture this: instead of "in the morning the site met customers with a red ‘connection is not secure’ screen because the certificate expired overnight on a forgotten subdomain nobody was watching" you get a reminder two weeks ahead and calmly renew. The base price starts from 4,000 ₽ per month; it depends on the number of domains and subdomains.

• You fear missing the renewal date and meeting customers with an "insecure" site.
• There are many domains and subdomains, you cannot track all dates manually.
• Auto-renewal sometimes breaks and you do not know about it.
• You learn about an expired certificate from customers or a traffic drop.

• Regular reading of certificates on domains and subdomains
• Expiry reminders at several thresholds (30/14/7/1 day)
• Basic validity: wrong domain, incomplete chain, expired
• Monitoring of the configured list of domains and subdomains
• A backstop against a silent auto-renewal failure
• Monthly continuous operation of the check
• An alert channel of your choice (email, messenger, webhook)
• A hint on what to check on a problem (renewal — separately)

• You do not miss the certificate renewal date
• You learn about a problem in advance, not from customers
• A backstop if auto-renewal silently broke
• You calmly renew in advance (renewal — your area or separate)

• We agree on the list of domains and subdomains, reminder thresholds and the alert channel
• We set up regular certificate reading and the date and validity check
• We launch continuous control, keep the list current on changes

• Will you renew the certificate if it is expiring?

  No. We watch the date and notify in advance, but we do not issue or renew the certificate — that is done by your certificate authority, hosting or control panel. Our alert needs to be acted on and renewed (by you or as separate work).

• I have auto-renewal (Let’s Encrypt), why do I need alerts?

  Auto-renewal sometimes silently breaks (a config changed, a process died, a domain-validation issue) — and the certificate expires anyway. Our alerts serve as a backstop and catch exactly that case so you have time to intervene.

• Is this a full SSL/TLS security check?

  No. This is control of the certificate's date and basic validity. A full TLS-configuration audit (protocols, ciphers, vulnerabilities) is a separate security task and is not part of this service.