The secure address opens
Whether https:// opens with a certificate browsers accept. A certificate that has run out, or was made for a different name, gets a full-page warning instead.
Do your visitors get a secure connection, or a warning? This free checker opens your site, reads who issued your certificate and when it runs out, and checks the rest of the secure connection, in plain English. Usually in a few seconds. No signup, and we keep no record of the site you check.
We open your site the way a browser would and read its certificate from the public logs. We keep no record of the site you check.
Opening your site…
Five things, each one a reason a visitor might see a warning instead of your site.
Whether https:// opens with a certificate browsers accept. A certificate that has run out, or was made for a different name, gets a full-page warning instead.
Who issued your most recent certificate and the day it runs out, read from the public certificate logs. We warn you a month ahead.
Whether people who type your address without https, or click an old link, are moved to the secure address, and whether the move is permanent.
Whether your homepage pulls in scripts, styles or images over plain http. Browsers block some of these, and parts of the page break.
Whether the other version of your address, with or without www, opens securely too. People type both.
Security headers, keys left in your code and old software are covered by the website security scanner.
Scan Your Website Free →The check runs on our server, not in your browser. A web page cannot open another site's plain http address or see whether its certificate was accepted, so we do it for you, as WPfoss-SiteCheck/1.0, with ordinary page requests and nothing else.
We keep no record of the site you check, and nothing about you: no name, no email address, no IP address. Our own analytics count that a check happened and its overall result, never the site. To read the certificate details we ask a public certificate log run by SSLMate (Cert Spotter), which receives the name of the site. Full detail is in our privacy policy.
It is free and there is no signup. You do not enter an email address, and we do not ask for one.
No. This checker keeps no record of the site you check, and nothing about you: no name, no email address and no IP address. Our own analytics count that a check happened and whether it came out secure, needs attention or has problems, and nothing more. To read the certificate details we ask a public certificate log run by SSLMate (Cert Spotter), which receives the name of the site.
Every certificate that browsers trust has to be written to public logs, called Certificate Transparency logs. We read the most recent certificate for your site that is valid today. That is almost always the one your site sends. If your server is still sending an older one, the check that opens your site will show it, because browsers refuse an expired certificate.
A secure page that loads some of its parts, such as scripts, styles or images, over a plain http address. Browsers block the scripts and styles, so parts of the page can break, and may stop showing the page as fully secure because of the images.
Some sites, or the firewall in front of them, turn away automated visitors. When that happens we cannot see whether the plain http address moves people to the secure one, so we say so rather than guess. Open the http version of your address in a private browser window to see for yourself.
No. The free website security scanner does that, along with keys left in your code and signs of old software. This checker is about the secure connection and the certificate.
Your secure connection is in good shape, which is one part of it. A safe website also needs the browser protections, the code and the software behind it to be right. Run the free website security scanner for those.
Website security is part of the Security Review. We fix problems in stages so your site never goes offline, write down what changed, and run this check again with you at the end.