Enter a domain or hostname, for example example.com.Please enter a valid hostname (e.g. example.com).This checker connects over IPv4. Enter a hostname or an IPv4 address.Only ports 443, 465, 993, 995 and 8443 can be checked.Enter a real hostname, not a wildcard. To test *.example.com, check a subdomain like www.example.com.Network error. Could not reach the SSL check. Please try again.The check failed. Please try again.Please enter a valid hostname (e.g. example.com).This checker connects over IPv4. Enter a hostname or an IPv4 address.This address is private or reserved, so the checker can't test it.Too many checks from your network. Please wait a minute and try again.The checker is busy right now. Please try again in a moment.A check from your network is already running. Please wait for it to finish.The checker is not available right now. Please try again later.We couldn't find {host} in DNS. Check the spelling, or make sure the hostname has an A record.{host} only has IPv6 addresses, and this checker connects over IPv4.{host} has no IPv4 address in DNS.The DNS lookup for {host} failed. Please run the check again.{host} resolves to a private or reserved address, which this checker can't test.The server at {ip} refused the connection on port {port}: nothing is listening on that port.No server answered on port {port} at {ip}. A firewall may block the port, or nothing runs on it.We couldn't reach {ip} on port {port}.We couldn't connect to {ip} on port {port}.The server at {ip} took the connection on port {port} but didn't finish the TLS handshake in time.The server answered on port {port}, but not with TLS. It may serve plain HTTP on this port.The server answered on port 465, but not with TLS. Mail servers that upgrade the connection with STARTTLS on port 587 are tested with the SMTP Test.The server answered on port {port}, but not with TLS. IMAP and POP servers that only offer STARTTLS (ports 143 and 110) can't be tested here.The server accepted the connection, but the TLS handshake failed.The server didn't send a certificate.The check ran out of time. Please run it again.The check failed. Please try again.Open the SMTP Test{ip} is a Cloudflare address: Cloudflare's proxy carries this site's web traffic, not its mail.Mail for {domain} is hosted by {provider}. Mail apps connect to {host} on port {port}.Mail for {domain} is hosted by {provider}, which takes mail from apps on port 587 with STARTTLS, not on port 465.Mail for {domain} is hosted by {provider}, which has no mail-app server on port {port}.Mail for {domain} is received by {mx}.Mail apps may connect to {host}.Your mail provider's setup guide names the host that mail apps connect to.{domain} accepts no email: its MX record says so (a null MX).Check {host}e.g. powerdmarc.come.g. smtp.gmail.come.g. imap.gmail.come.g. pop.gmail.comSSL certificate for port {port}{type} certificateSSL certificate is valid and correctly installedBrowsers and mail clients will trust this certificate for {host}.The certificate works, with 1 warningThe certificate works, with {n} warningsNothing is broken yet, but fix the items below before they turn into errors.Certificate problem found (1)Certificate problems found ({n})Visitors or mail servers connecting to {host} will see errors or refuse the connection.Some checks couldn't finish this time. Run the check again for a complete result.Days until expiryExpired1 day ago{n} days agoValid untilIssuerProtocolChecks{n} of {m} passedCheckResultStatusPassWarningFailInfoExpiry dateHostname matchCertificate chainRevocation statusKey strengthSignature algorithmTLS versionHSTS headerNot valid until {date}Expired {date} (1 day ago)Expired {date} ({n} days ago)Expires {date} (today)Expires {date} (1 day left)Expires {date} ({n} days left)Valid until {date} ({n} days left){host} matches {name}{host} is not on the certificateThe certificate lists no hostnames (no Subject Alternative Names)Complete and trusted (1 certificate sent)Complete and trusted ({n} certificates sent)The chain is complete, but trust can't be confirmed while the certificate is outside its validity datesIncomplete chain: the server doesn't send the intermediate certificateSelf-signed certificateThe chain ends at an untrusted rootA certificate in the chain doesn't match the one that should sign itAn intermediate certificate in the chain has expiredThe certificate isn't issued for TLS serversNot trusted: the chain failed verificationThe chain couldn't be verified this timeNot revoked ({method})Revoked by the issuer ({method}, {date})Revoked by the issuer ({method})Not checked: the certificate lists no OCSP responder or revocation listNot checked: the authority's revocation service didn't answerNot checked: no time was left to ask the authorityNot checked: the authority's revocation list is too large to read hereNot checked: the authority's answer couldn't be verifiedNot checked: the authority's answer is out of dateNot checked: the authority's OCSP responder doesn't know this certificateNot checked: the certificate isn't from a trusted authorityNot checked: the certificate is outside its validity datesNot checked: the issuer's certificate is missingNot checked: the authority's revocation service sent the checker to an address it doesn't contactNot checked: the authority's revocation service turned the request down{type} {bits}-bit{proto} negotiated (deprecated){proto} negotiated, but {old} still acceptedTLS 1.0 and 1.1 refusedTLS 1.0 and 1.1 not tested and Not setSet to max-age=0 (turned off)Couldn't read the server's HTTP responseHow to fixFix firstFix soonOptionalThe certificate isn't valid yet. Check the server clock, or install the certificate that is currently valid.Renew the certificate now and reload the server. Then check why automatic renewal didn't run.Renew the certificate before it expires, and set up automatic renewal (ACME or Certbot) so this doesn't become an outage.Reissue the certificate with {host} as a Subject Alternative Name, or point this hostname at a server that has the right certificate.Reissue the certificate with every hostname listed as a Subject Alternative Name. Browsers ignore the Common Name.Install the full chain (your certificate plus the intermediates). Your CA provides it as fullchain.pem or a CA bundle.Replace the self-signed certificate with one from a public certificate authority. Let's Encrypt issues free DV certificates.The root certificate isn't in public trust stores. Use a certificate from a publicly trusted CA.Reinstall your certificate with the intermediate certificates your CA issued for it.Replace the expired intermediate with the current one from your CA's bundle.Request a certificate issued for TLS server authentication.Make sure the server sends the full chain from a publicly trusted certificate authority.The CA has revoked this certificate. Request a new one and install it immediately.Generate a new key of at least RSA 2048-bit or ECDSA P-256 and reissue the certificate.SHA-1 and MD5 signatures are no longer trusted. Reissue the certificate with SHA-256.Enable TLS 1.2 and 1.3 and disable TLS 1.0, 1.1 and SSL in the server configuration.Disable {old} in the server configuration. TLS 1.0 and 1.1 are deprecated (RFC 8996).Add a Strict-Transport-Security header so browsers always use HTTPS.Certificate detailsConnectionCommon name (CN)OrganizationNot includedIssued byValid fromValid untilSerial numberKeySignatureHost / portServer IPProtocolCipher suiteSHA-256 fingerprintHostnames covered (SANs)No SANs listed+{n} moreCertificate chainTrustedNot trustedServer certificateIntermediateRootTrusted rootMissingNot sentExpiredIssued by {name}In browsers' trust storesExpires {date}Intermediate certificateThe server didn't send the certificate that links this chain to a trusted root.Fetched from the CA to finish the checksChecked {time} UTC. Results reflect what this server presented to our checker; servers behind load balancers may present different certificates to different visitors.Is your mail server's TLS as healthy as your website's?Test STARTTLS on your mail servers and enforce encrypted delivery with MTA-STS.Test STARTTLSCheck MTA-STSChecking, this can take up to 15 seconds.Check finished. {verdict}CopiedCopy this with Ctrl+C (Cmd+C on a Mac), then press Enter.