Our check browser

Seeing requests with "OutperformerzSelfCheck" in the user agent in your logs? Then someone started the free self-check for your shop on outperformerz.com, usually you, your team or a service provider. That person confirmed it is their shop or one they work for.

How to recognise it

The user agent is a regular Chrome identifier with this suffix:
OutperformerzSelfCheck/1.0 (+https://outperformerz.com/crawler)

Requests come from our server in Germany (46.4.100.119, 2a01:4f8:140:9221::2).

What it does

• It opens the homepage and up to two product pages, like a visitor who doesn't accept the cookie banner.
• It checks once whether http:// redirects to https://.
• It evaluates what loads anyway: tags, requests to tracking services, load time, browser console and security headers.
• At most one fresh check per domain per day. Further requests get the existing result.

Every check is triggered by a person. Like other user-triggered testing tools, the check browser therefore does not read robots.txt.

What it doesn't do

• No orders, no form submissions, no logins
• No clicks on the cookie banner or anything else
• No crawling of further pages, no load or attack tests
• No requests for files or paths a regular visitor wouldn't load

What happens next

We add checked domains to our ongoing observation of public shop signals (Profit Guard). For that, our scanner regularly opens a few public pages. We don't process data about the shop's visitors or customers.

Opting out

Don't want your shop checked via the self-check or observed? Write to andreas@andreas-behr.de. We'll block the domain for the self-check and remove it from the observation.

Go to the free self-check