Where Silktide connects from

Silktide's testing browsers run on AWS and normally use a large, dynamic set of IP addresses. Allowlisting that entire range is usually impractical for a firewall team.

Prefer a proxy

Under the website's Advanced settings, set a proxy location. Testing then comes from a small set of known Silktide proxy IP addresses for that region (EU, US, or Australia). Use the location closest to where the site is hosted when you can - or closest to the audience whose experience you care about, if the site varies by geography.

Exact proxy IP address lists can change. Confirm the current ranges with Silktide support or your Customer Success contact if you are building a firewall rule.

A proxy is also the usual first fix when:

• Bot protection blocks or challenges the crawler
• Silktide sees different content than you do because of geo-targeting
• Your security team needs a short allowlist instead of a wide AWS range

See When crawling fails for the full troubleshooting path.

User agent

Silktide imitates the device it is simulating (desktop or mobile) and appends a configurable suffix - by default including "Silktide". Your server logs can use that suffix to identify testing traffic.

You can change or remove the suffix in Advanced settings. Some sites that already trust a known Silktide user agent may prefer stealth mode off; others need stealth on to look more like an ordinary browser. Those trade-offs are covered under Loading a page.