Skip to content

HTTPS Checker Usage Examples

Andrew Stilliard edited this page Mar 21, 2017 · 5 revisions

With any of these examples the report will show all mixed content issues found. With these you will then need to track them down and fix them.

Crawling a site that blocks robots crawling it

E.g. a development / staging version of a site.

  1. Enter the URL of the site (or upload the CSV of URLs).
  2. Open the advanced options menu.
  3. Un-tick "Use Robots.txt File Rules"
  4. Also consider selecting a different User Agent if the site also blocks requests it believes are bots.
  5. Click Run to begin.

Finding just the Chrome/Firefox 2017 "Not Secure" message on sites

  1. Enter the URL of the site (or upload the CSV of URLs).
  2. Select "Chrome Not Secure Warning" as the Mode.
  3. Click Run to begin.

Crawling a logged in area of a site

  1. Enter the URL of the site (or upload the CSV of URLs).
  2. Open the advanced options menu.
  3. Select "Session" and this page will guide you through the process.
  4. The basic flow for this is to login as a user on your site, grab the cookies the site uses to identify them, and then paste these cookies back into the app. If you have any problems setting this up, please contact us here.
  5. Click Run to begin.
  • As an aside note, an alternative solution that works well for these logged in areas is to use our HTTPS Reporter tool which receives reports automaticaly as users browser sites.

We also have a video available here: https://www.youtube.com/watch?v=fn1lBr9Pggk

Looking for the desktop checker? Download it here.

Looking for the online reporter? Find it here.

Clone this wiki locally