Skip to main content

If Shake fails to scan your site

What to do when a Shake audit fails with a 401 or 403 error — private access, anti-bot blocking, and IPs to whitelist.

Written by Alexandre Dias Da Silva

Shake may fail to analyze a website for several reasons. Here's how to identify the cause and, if possible, resolve it.

The audit returns a 403 error — antibot blocking

Some websites protect their access with a WAF (Cloudflare, Sucuri, Imperva, etc.) that detects and blocks automated bots. When the server identifies Shake as an unauthorized bot, it returns a 403 error.

If your website uses this type of protection, add Shake's IP addresses to your server's whitelist.

Primary IP (mandatory) — in the vast majority of cases, this is the only one to add:

  • 54.194.108.249

France proxy IPs (optional) — add if your server blocks the primary IP in France:

  • 178.171.75.71

  • 158.46.140.140

  • 67.159.209.36

  • 67.159.216.117

Proxy IPs for other countries (optional) — add if your server blocks the primary IP outside France:

  • 79.135.147.76

  • 198.20.131.186

  • 185.81.186.93

  • 85.28.39.220

  • 31.105.184.98

  • 103.52.8.90

The audit returns a 401 error — private access

Some websites require authentication before allowing access to their content. Shake does not have this authentication information: the server returns a 401 error to it.

It is not possible to bypass this restriction: Shake does not work on websites with private access.

Did this answer your question?