SSL Toolkit Logo
Tools Features Compare FAQ Login

Certificate Expiry Calendar Export

Export certificate expiry dates to your calendar application

Calendar Export

About

The Expiry Calendar Export tool generates downloadable calendar files (ICS format) containing certificate expiry dates for all your monitored domains. Import these into Google Calendar, Outlook, Apple Calendar, or any CalDAV-compatible calendar to receive native calendar reminders before certificates expire.

This bridges the gap between SSL monitoring and your daily workflow by putting certificate expiry dates directly into the calendar applications you already use. Calendar reminders provide an additional notification layer beyond email and webhook alerts.

How to Use

  1. 1Select the domains you want to include in the calendar export
  2. 2Choose how many days before expiry to create calendar reminders
  3. 3Click "Generate Calendar" to create the ICS file
  4. 4Download and import the ICS file into your preferred calendar application

Use Cases

What The Calendar Contains

A calendar entry turns a certificate's expiry into something that appears in your calendar rather than something you remember to check. This page generates that entry from the live certificate.

  1. 1Read the real expiry date from the certificate being served and format it as the calendar timestamp the standard expects, in UTC so no timezone conversion can move the date.
  2. 2Add two reminders, at thirty days and at seven, because they trigger different responses. Thirty days is when you start work; seven is when a failure has stopped being comfortable.
  3. 3Generate a standard iCalendar file you can import into whatever calendar you already use, rather than asking you to copy a date by hand — which is precisely the manual step that gets skipped.

The reminder is an input to a process, not a substitute for one. Combine it with automation that renews and with monitoring that checks what is actually served, so a missed calendar entry is a backstop rather than your only protection.

Tips & Best Practices

  • •Create reminders at 30, 14, and 7 days before expiry for maximum visibility
  • •Set the calendar to repeat annually so new reminders are created automatically
  • •Share the calendar with your entire DevOps team for collective visibility
  • •Import into both personal and work calendars to ensure reminders are seen

Technical Details

●Format: ICS (iCalendar) format compatible with all major calendar applications
●Reminders:** Configurable reminder intervals (7, 14, 30, 60, 90 days before expiry)
●Recurring:** Annual recurring events for ongoing monitoring
●Import:** One-click import for Google Calendar, Outlook, Apple Calendar

Frequently Asked Questions

In Google Calendar, go to Settings > Import & Export > Import and select the ICS file. In Outlook, double-click the ICS file and click Open in Calendar. On Mac, simply double-click the file to add it to Apple Calendar. The calendar entries will appear with the domain name and expiry date.
The current export creates static calendar entries. When certificates are renewed, re-export the calendar to get updated expiry dates. We are working on a subscription calendar feature that will auto-update.
Yes, after importing into Google Calendar or Outlook, you can share the calendar with team members. They will see all certificate expiry dates and reminders in their own calendars without needing access to the SSL monitoring dashboard.
Because thirty days and seven days call for different responses. At thirty you are starting the work — checking whether automation will actually renew, whether anyone must approve it, whether a maintenance window is needed. At seven, a failure is no longer recoverable in comfort. One reminder cannot serve both purposes, and choosing the later one is how certificates expire despite a calendar entry existing.
No, and treating it as a replacement is the mistake. The calendar is a backstop that catches automation which failed silently — and silent failure is the common case, since a renewal that succeeds without deploying leaves every record looking correct. Automation plus independent monitoring plus a calendar entry is the combination that works; any one of them alone leaves a gap.
Because the expiry is an absolute instant, and converting it through a local timezone can move it by a day. A certificate expiring at midnight UTC would appear to expire on the previous day in some zones, which shifts the whole reminder schedule. Using UTC keeps the entry aligned with what the certificate actually says, which matters most in the final days when the difference is a full day of margin.
You get one entry per certificate, each with two reminders, which is the behaviour you want — these are genuinely independent deadlines with independent renewal processes. The risk is duplication if a certificate is already tracked elsewhere. Consolidate into one system of record rather than maintaining several, because duplicated reminders tend to produce both being ignored.
They serve different purposes. Scheduled monitoring tells you the current state across everything you own, which is what you need for a fleet. A calendar entry tells you in advance, in a place you already look, which is what catches the one host nobody is monitoring actively. For anything you are not actively watching, the calendar entry is often the thing that actually gets noticed.

Related Tools

Expiry Calendar Expiry Notifier Expiry Calculator Expiry Notifier Renewal Planner Certificate Monitor