To check a WordPress site's SSL certificate, type its domain above and press Check. The checker reads the certificate your site sends on port 443 and shows the expiry date, the days left, who issued it, the names it covers and whether browsers trust the chain. It works the same for a WordPress.com site and a self-hosted one. You don't install a plugin or log in to WordPress.
How to check a WordPress site's certificate
- Type the domain your visitors use, such as example.com, and press Check.
- Read the expiry date and days left, the issuer, the names the certificate covers and whether browsers trust the chain.
Look at the names first. If the address people type, such as the www version, isn't in the list, browsers warn on that address even when the certificate is valid for the other one.
SSL on WordPress.com sites
WordPress.com gives every domain and subdomain it hosts a free certificate. A new one usually takes a few minutes, and it can take up to 24 hours. If the checker still finds no certificate after that, look at your DNS.
Some DNS settings stop WordPress.com from issuing the certificate. One common cause is a CAA record that doesn't allow Let's Encrypt to issue it. Those details are in WordPress.com's support guide on HTTPS and SSL, read in October 2026.
On a self-hosted WordPress site your host or your server supplies the certificate. WordPress works over HTTPS once it's installed, and the checker reads it the same way.
When the padlock is missing but the certificate is fine
If the checker shows a trusted certificate and a page still has no padlock, look for mixed content: files on that page loading over http. WordPress.com notes it affects single pages, so the padlock can show on some pages and not on others. The checker reads the certificate and doesn't scan your pages for http files. It also doesn't check whether the certificate has been revoked.
This sSL checker is free with no signup. SearchBlueprint, who make it, sell SEO planning for websites: which searches each page should answer.