How to use this check
Enter a hostname to inspect the certificate served on HTTPS port 443 after public address validation.
NetProbe resolves public A/AAAA answers first, blocks private ranges and then connects with SNI on port 443.
TLS and certificates
ReadyCheck certificate identity, expiry and chain context for public HTTPS endpoints.
Enter a hostname to inspect the certificate served on HTTPS port 443 after public address validation.
Run a point-in-time diagnostic from this page. Results appear above the guide, and methodology, privacy notes and limits stay below the tool.
Optional account features
The free check answers the immediate question on this page. Larger features can add saved history, alerts, reports, API access and regional monitoring when they are enabled for your account.
Enter a hostname to inspect the certificate served on HTTPS port 443 after public address validation.
NetProbe resolves public A/AAAA answers first, blocks private ranges and then connects with SNI on port 443.
A valid certificate should match the hostname, include current dates and be issued by a chain trusted by modern clients.
If the certificate expires in 10 days, renew it and verify that the new certificate is actually served by the edge.
Load balancers, stale CDN edges or missing SAN entries can serve a certificate that differs from the one expected.
Check each public edge, renew through the certificate authority and confirm the active certificate after cache or load balancer updates.
The initial probe reports certificate facts and chain hints; it is not a full browser trust or policy audit.
The server may be serving a default certificate, a stale CDN certificate or a certificate without the hostname in SAN values.
No. It checks the hostname you enter. Use monitoring later for multiple assets and recurring expiry alerts.
Keep the free checks useful by sharing corrections and using the practical pages first. No payment provider is connected here.