Allowlisting Binclusive's audit runner
A cloud audit drives a real screen reader through your journeys in a browser we host. If your site only answers known IP addresses — a staging environment behind a firewall, a WAF with an IP allowlist, a CDN rule that blocks data-centre traffic — that browser needs to be let in.
Every cloud audit of a project reaches your site from one address. Which one depends on the project’s Audit location, under Project settings → Project:
| Audit location | Address |
|---|---|
| United States (the default) | 34.27.21.155 |
| Türkiye | 37.230.105.250 |
Pick Türkiye when your site serves visitors in Türkiye differently, or turns away visitors from elsewhere. The site then sees the audit as a visitor in Türkiye.
The United States address is the one our manual testers use, so if you already allowlisted it for a manual audit and the project audits from the United States, you are done.
Allow the address
Section titled “Allow the address”Add your project’s address to whatever decides who can reach the site you audit. The examples
use 34.27.21.155; use 37.230.105.250 for a project that audits from Türkiye.
- Firewall or security group — allow inbound HTTPS (port 443) from
34.27.21.155/32. Add port 80 too if the site redirects from HTTP. - WAF or bot protection (Cloudflare, Akamai, AWS WAF, …) — add an allow or skip rule for the address, so audits are not sent a challenge page. An audit that meets a challenge reports the challenge, not your site.
Check it worked
Section titled “Check it worked”Start a new run of a journey that failed. When the runner can reach the site, the run leaves the Failed — we couldn’t load the site state and produces a report.
If the run still fails with the same reason after the address is allowed, the site did not answer the runner in time for another reason — check that the URL the journey starts from loads from outside your network.
When a run fails for another reason
Section titled “When a run fails for another reason”Only an unreachable site is fixed by allowlisting. The run history names the reason for every run that did not finish:
- the run ran past its time limit — the run hit the time cap before the journey finished.
- the site asked for a login — the persona’s session expired. Re-capture the persona.
- you stopped this run — someone cancelled it. Nothing to do.