Skip to content

SSL & domain expiry

Domain expiry from the registry, SSL checks without guesswork

Domain expiry dates come from RDAP, the registries' official data service, and open domain_expiring issues at 30, 14 and 7 days. If a registry doesn't publish an expiry date, we show 'expiry unknown'. SSL certificate inspection needs a direct TLS connection that our current runtime can't make, so it activates at hosting launch — we never estimate certificate dates.

What it does today

  • Domain expiry via RDAP

    Cached for 24 hours; warnings at 30, 14 and 7 days.

    Available now
  • 'Expiry unknown' when RDAP is silent

    Some TLDs don't offer RDAP or omit the date. We store nothing rather than invent one.

    Available now
  • SSL certificate issuer, validity and expiry

    Requires reading the peer certificate; the probe interface is ready and activates with the VPS move.

    Activates at hosting launch

Why SSL waits for launch

Reading a certificate means opening a raw TLS connection and inspecting what the server presents. The serverless runtime we use today only offers a high-level fetch that hides the certificate. Rather than scrape expiry dates from third-party sources, every SSL field shows 'Checked after hosting migration' until the real probe runs.

Frequently asked questions

Try it on a real domain — free, no account needed.