Every check / code-calls-insecure-endpoints

Does your site's code fetch things over unencrypted addresses?

We read the script files your site serves from its own domain for written-out addresses that start with plain http.

How it decides

Namespace declarations, such as the ones every inlined SVG carries, and local test addresses are left out. The check speaks up when any remain.

Run this check on any website

Free, with no account. It sends the site nothing an ordinary visitor would not.

Why it matters

Anything fetched from one travels in the clear, so anyone on the same network as your visitor can read it and change it on the way.

In more detail

Browsers block most of these on a secure page, so the feature involved is probably already broken for some people and nobody has said.

Who fixes it, and where it runs

Who usually fixes it
Whoever built your site
Which plan runs it
The free scan, on any website
Proof you own the site
Not needed. It sends your site nothing an ordinary visitor would not.
More about this check
Who it is about
An intruder
Listed under
Things that should not be public
The standard
Its name in a report
code-calls-insecure-endpoints