Identifying traffic from Sitebulb Cloud

This article explains how you can identify incoming traffic from Sitebulb Cloud on your websites, which can be used for allowlisting Sitebulb within your Web Application Firewall (WAF) or through your CDN.

Sitebulb has two data centres, one in the UK and one in the US. When you sign up to Sitebulb Cloud, you will be assigned a data centre (based on your location/preference) and an IP address from the ranges below.

Certain Sitebulb Cloud plans include a dedicated IP address that is unique to you. This IP address will not be listed above but will be communicated to you by our Customer Success Team upon signup.

To find the IP address used by your specific Sitebulb Cloud Workspace, navigate to Settings > Logging.

Sitebulb has two user agents, Sitebulb Desktop and Sitebulb Smartphone, which will be selected by default when you first set up an audit with Desktop or Mobile, respectively.

Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Mobile Safari/537.36 +https://sitebulb.com

Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Safari/537.36 (compatible; Sitebulb/1.1; +https://sitebulb.com)

Like Googlebot, Sitebulb uses the placeholder Chrome/W.X.Y.Z to represent the latest version of Chrome, which is regularly updated when new versions of Sitebulb are released. We do this to keep our Chrome Crawler evergreen, in line with Google's rendering policy.

Example user-agent string for Sitebulb smartphone with a value in for W.X.Y.Z:

It is important to note that Sitebulb is not a public bot. The Sitebulb bot will only ever crawl a website if a user proactively chooses to use it while performing an audit within the Sitebulb software.

Although the Sitebulb user agent is the default option, users are able to choose between a number of user agents, including Google, Bing, Yahoo, and Yandex user agents - and even custom user agents.

This changes which user-agent string Sitebulb will use when making HTTP requests, and can impact what content is returned by the website server. For more guidance on customising user agent settings, read our Robots Directives settings guide.

Sitebulb can also be configured to crawl using custom headers, which is an additional way that Sitebulb traffic can be identified - this is often used by customers when crawling staging environments that are otherwise publicly inaccessible.