Check any website or mail server's SSL/TLS certificate. See the expiry date, hostname match, certificate chain, issuer, key strength and TLS version, with a clear list of what to fix.
How the SSL Checker Works
The SSL checker connects to your server the same way a browser or mail client does, then validates everything it gets back.
1
Enter a hostname
Type a domain like example.com or the mail server your mail app uses, like imap.gmail.com, and pick the port. Use 443 for websites and 465, 993 or 995 for mail servers.
2
We run a TLS handshake
The checker opens a TLS connection with SNI, collects the full certificate chain, and records the protocol version and cipher the server negotiates.
3
Get a pass, warning or fail
Each check gets a status, and every problem comes with a plain-language fix so you know what to change before visitors or mail servers see an error.
What the SSL Certificate Checker Tests
A certificate can be installed and still fail. These are the checks that decide whether browsers and mail servers trust it.
Expiry date
When the certificate became valid and when it expires, with a warning when fewer than 30 days remain, or the last third of a short-lived certificate's lifetime.
Hostname match
Whether the name you entered is listed in the certificate's Subject Alternative Names, including wildcard matches.
Certificate chain
Whether the server sends every intermediate certificate and the chain ends at a trusted root authority.
Revocation
Whether the issuing authority has revoked the certificate, checked with the authority's own OCSP responder or certificate revocation list (CRL).
Key and signature
Key type and size (RSA 2048+ or ECDSA) and a modern signature algorithm such as SHA-256.
TLS version
The protocol the server negotiates, and whether it still accepts TLS 1.0 or 1.1. TLS 1.2 and 1.3 pass. TLS 1.0 and 1.1 are deprecated and flagged.
Common SSL Certificate Errors and How to Fix Them
These are the problems the checker finds most often, and what to do about each one.
Expired certificate
The certificate is past its end date
Browsers show a full-page warning and mail servers may refuse the connection. Most expiries happen because auto-renewal broke silently.
Renew the certificate, install it, and reload the web or mail server. Then confirm auto-renewal works.
Name mismatch
The hostname is not on the certificate
The certificate was issued for a different name, for example example.com but not www.example.com or mail.example.com.
Reissue the certificate with every hostname you serve listed as a Subject Alternative Name.
Incomplete chain
An intermediate certificate is missing
Desktop browsers often fill the gap from cache, so the site looks fine to you while mobile devices, APIs and mail servers fail.
Install the full chain file from your certificate authority, usually called fullchain.pem or the CA bundle.
Self-signed or untrusted
No trusted authority signed it
Self-signed certificates and private CAs are fine for internal testing, but public visitors and mail servers won't trust them.
Replace it with a certificate from a public CA. Let's Encrypt issues free DV certificates.
Expiring soon
Fewer than 30 days remain
Public certificate lifetimes are getting shorter, so renewals happen more often and manual processes break more easily. Short-lived certificates get the warning in the last third of their lifetime.
Automate renewal with ACME (Certbot or your host's tool) and monitor expiry dates.
Old TLS version
The server still allows TLS 1.0 or 1.1
Both versions are deprecated (RFC 8996), and modern browsers no longer connect with them.
Disable TLS 1.0 and 1.1 and enable TLS 1.2 and 1.3 in your web or mail server configuration.
How to Check an SSL Certificate Manually
You can also inspect a certificate from your browser or the command line.
On the command line Replace example.com with your hostname.
In Chrome or Edge, click the icon left of the address bar, then Connection is secure → Certificate is valid. In Firefox, click the padlock, then Connection secure → More information → View certificate. You'll see the issuer, validity dates and SANs. The browser view does not show whether the server sends the full chain, so use the checker above for that.
Types of SSL Certificates
The checker shows the validation level and every hostname the certificate covers.
Types of SSL certificates
Type
What it verifies
Typical use
Domain Validated (DV)
Control of the domain only
Blogs, most websites, mail servers, MTA-STS hosts
Organization Validated (OV)
Domain control and the legal organization
Business and SaaS sites
Extended Validation (EV)
Strict checks on the legal entity
Banks, payment and regulated sites
Wildcard
One level of subdomains, e.g. *.example.com
Many subdomains on one certificate
Multi-domain (SAN)
A list of different hostnames
Several domains or services on one server
Why SSL Certificates Matter for Email Security
TLS certificates aren't just for websites. Several email security standards depend on them, and a broken certificate can quietly stop them from working.
MTA-STS
Your MTA-STS policy is served from mta-sts.yourdomain.com over HTTPS, and your MX hosts must present valid certificates that match their names. An expired certificate on either one breaks enforcement.
Mail clients connecting on ports 465, 993 and 995 validate the server certificate. A mismatch or missing intermediate causes connection errors for users.
Enter your domain in the SSL checker above and click Check SSL. It connects to your server, reads the certificate and shows the expiry date, issuer, hostname match, chain status and TLS version. You can also click the padlock in your browser's address bar, or run openssl s_client -connect example.com:443 -servername example.com.
How do I know if an SSL certificate is still valid?
A certificate is valid when today's date is between its Valid from and Valid until dates, it lists your hostname, it chains to a trusted root and it hasn't been revoked. The checker tests all four and shows the number of days left before expiry.
What happens when an SSL certificate expires?
Browsers show a full-page security warning and most visitors leave. APIs, apps and mail clients refuse to connect, and services that rely on HTTPS, such as MTA-STS policies and BIMI logos, stop working. Renewing and reinstalling the certificate fixes it immediately.
What does "certificate name mismatch" mean?
The hostname you connected to isn't listed in the certificate's Subject Alternative Names. For example, the certificate covers example.com but you visited www.example.com. Reissue the certificate with every hostname you use.
What is an incomplete certificate chain?
The server sends its own certificate but not the intermediate certificate that links it to a trusted root. Desktop browsers often work around this, but mobile devices, APIs and mail servers fail. Install the full chain file your certificate authority provides.
Is SSL the same as TLS?
TLS is the modern version of SSL. All SSL versions and TLS 1.0 and 1.1 are deprecated, and current servers use TLS 1.2 or 1.3. People still say "SSL certificate", but the same certificate is used for TLS.
Can I check the SSL certificate of a mail server?
Yes. Choose port 465 for SMTPS, 993 for IMAPS or 995 for POP3S, and enter the host name your mail app connects to, which is often not your website's: for Google Workspace that is smtp.gmail.com, imap.gmail.com or pop.gmail.com, and for Microsoft 365 it is outlook.office365.com. If your domain doesn't answer on a mail port, the checker tells you where its mail is hosted. For mail servers that upgrade a plain connection with STARTTLS on port 587, use our SMTP Test.
How long are SSL certificates valid?
Under CA/Browser Forum rules, publicly trusted certificates issued since March 15, 2026 can last at most 200 days. The limit drops to 100 days in March 2027 and 47 days in March 2029. Let's Encrypt's standard certificates last 90 days, then 64 days from February 2027 and 45 days from February 2028. Shorter lifetimes make automatic renewal essential.
Does this tool check SSL certificates for free?
Yes. The SSL checker is free and needs no sign-up. PowerDMARC also offers free tools for DMARC, SPF, DKIM, MTA-STS and BIMI.
Why do SSL certificates matter for email?
MTA-STS needs a valid certificate on your mta-sts subdomain and on every MX host, BIMI logos and VMCs must be served over HTTPS, and mail clients validate certificates on ports 465, 993 and 995. An expired or mismatched certificate can quietly break all of these.
PowerDMARC monitors MTA-STS, TLS-RPT, DMARC, SPF and DKIM in one place, and alerts you when a certificate or policy problem starts affecting mail delivery.
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.