What IP address and user agent does Silktide use?
Without a proxy, Silktide's testing browsers run on AWS and use a large, changing set of IP addresses. Allowlisting that whole range is not practical, so if your firewall or bot protection needs a short list, set a proxy preset first.
Get a short list of addresses
A proxy preset sends all of a website's testing through two fixed Silktide IP addresses in the region you choose.
- Open the website in Silktide, choose Settings in its sidebar, then Advanced.
- In the Proxy section, pick a Preset: EU (Dublin), US (Ohio) or AU (Sydney). Pick the one closest to where the site is hosted, or closest to the audience your site changes its content for.
- Choose Save changes.
- Allowlist both addresses for that preset, from the table below.
- Retest the website. The preset applies from the next test.
| Preset | IP addresses to allowlist |
|---|---|
| EU (Dublin) | 52.18.199.206, 52.209.191.79 |
| US (Ohio) | 52.14.69.69, 18.224.35.114 |
| AU (Sydney) | 3.104.57.83, 3.24.44.162 |
These addresses only apply when the preset is set. With No proxy, testing comes from the wide AWS range, and allowlisting these six addresses lets nothing through. With a custom proxy, testing comes from your own proxy instead. Silktide may use either address of a preset for any request, so allowlist both.
User agent
Silktide's user agent imitates the device being tested, desktop or phone, and adds a suffix to the end. The default suffix is Silktide, so your server logs and firewall can pick out testing traffic by looking for that word.
To change or remove it, open the same Advanced settings and edit User agent suffix in the Crawler section. Leave it empty to send no suffix at all. Choose Save changes, and it applies from the next test.
More detail
Where Silktide connects from has the same addresses, and when a proxy also helps with geo-targeted content. If a website will not test because of bot protection, see What should I do if a website will not test?