Both dates come from public sources that need no credential, which is why this can answer a question you only think to ask occasionally. The batch call with its own thresholds is what turns it from a one-off lookup into an audit you can run over everything you own.
Two tools for domain health: registration expiry read over RDAP, the successor to WHOIS, and TLS certificate expiry read from crt.sh Certificate Transparency logs. Both sources are free and unauthenticated, so nothing needs signing up for.
- One domain checked for both expiries at once, with the days left on each and the certificate's issuer, and a negative number where it has already lapsed
- URLs normalised for you — a full address with protocol and path is reduced to the domain before the lookup
- Up to 50 domains checked in parallel, each classified ok, warning, critical, expired or error
- Warning thresholds you set: 30 days for registration and 14 for the certificate by default, adjustable to match how slow your renewal process actually is
- A summary of counts by status beside the per-domain detail, so a portfolio audit reads as a number first
- A failed lookup reported as an error status against that domain instead of taking down the batch
A current Node.js and nothing else — no API key and no account. Run over stdio from npm as domain-monitor-mcp-server, through npx or a global install. It reads rdap.org for registration data and crt.sh for certificates, so it needs outbound network access; crt.sh documents a rate limit of about 10 requests per second.