How to Identify Problem Links

It is possible to test any site’s SSL capability simply by changing an “http://…” URL to “https://…”.   If the page does not load, the browser may return an error like: “Unable to connect” or “This webpage is not available” or ERR_CONNECTION_REFUSED. In this case, the browser cannot connect to the SSL-enabled web service, which probably means it isn’t configured correctly for your domain.

However, sometimes even though the page might load, certain images and formatting may be broken. If you wrote all of your pages yourself, you may be able to figure out which links are causing problems. Even so, that can be tedious, and there’s a good chance you’ll miss something.

Identifying Problem Links

We suggest using third-party web tools to check your site for you. These tools should list exactly which links caused the problems. They may also tell you which file to change to fix the links. JitBit SSL Check is used to analyze an entire site and determine which pages contain problem files. Why No Padlock is for use on individual pages to determine which specific files are returning errors. By using these two together it is possible to work through a site and locate any problem links.

Why No Padlock?

This tool is located at:

There you may enter the URL of a single page on your site. The tool will load the page and all of its support files. Then it will give you back a report on where you have problems to fix.

JitBit SSL Check

This tool is located at:

Enter the homepage of your website. The tool will load up to 200 linked pages within your site and check them all for insecure links. This SSL Check will only tell you which pages contain insecure content. It will not tell you what links need to be fixed on each page. This is mostly useful for identifying problem pages, then use those URLs in the Why No Padlock tool to find the specific errors.