How this works. Everything here runs client-side in your browser. A direct request confirms whether your browser can reach the domain and times how long that takes. A public proxy (api.allorigins.win) is used to read the actual HTTP status code, since browsers block reading cross-origin response details directly. SSL validity is inferred from whether an https:// connection completes at all — browsers refuse to complete a connection with an invalid or expired certificate, so a successful HTTPS fetch means the certificate was trusted at check time. For full certificate details (issuer, expiry date, chain), use the "Full SSL report" link. Results reflect a single request and can vary with network conditions, firewalls, or the target blocking automated checks.