Certificates expire on weekends. Fajita reads the calendar, warns you at a distance, and catches invalid chains before browsers show your customers a warning screen.
TLS genius.ly:443→ valid · expires 2027-02-13 (212 days)chain complete ✓ issuer trusted ✓reminders at 30 days and 7 daysinvalid chain alerts immediately
What it checks
Certificate expiry dates, validity, and the chain your visitors actually receive.
What failure looks like
The full-screen browser warning with your name on it. It converts nobody and screenshots forever.
What Fajita does
Warns at configurable distances before expiry and alerts immediately when a certificate is invalid, so renewal is a task instead of an incident.
Why it matters
An expired certificate is a total outage with a screenshot. It is also the single most preventable failure in software.
In practice
Fair questions
Auto-renewal fails quietly: a changed DNS record, a moved server, an expired API key at the issuer. Monitoring catches the failure of the safety net itself.
You choose the warning thresholds. Set a comfortable distance and a final urgent one.
Related