Data sources, refresh times and limits
Certificate Transparency
We use the Cert Spotter API by SSLMate, which indexes public CT logs. It returns certificates that have not yet expired. Refresh cadence adapts: a domain is re-checked daily while a monitored certificate expires within 30 days or the domain was added in the last 48 hours, and otherwise every 3 days (weekly on the free plan). Lookups are rate-limited by the provider and shared fairly between customers, so a new domain can take a few hours to appear. Very large domains may be too big for automatic discovery.
Domain registration expiry
We use RDAP: the IANA RDAP bootstrap file tells us which registry server to ask. Registries publish terms that limit automated querying, so we check each domain about once a week, and daily only in the 30 days before expiry. Requests are throttled to at most one per second across the service; when the limit is reached the lookup waits for the next run. Registries state that RDAP data is not authoritative. Some TLDs do not offer RDAP, and some registries do not publish an expiry date; we show that instead of a date.
Limits
- We do not connect to your servers. We show the most recently issued certificate per CT logs, which may not be the one being served.
- Certificates from private CAs are not in public CT logs.
- Some TLDs (for example .io and .de) do not offer RDAP. For them we show "registration date not available via RDAP for this TLD" and send no registration alerts.
- All dates are shown in UTC.