How to authorize Strike's IPs

Last updated: July 20, 2026

Many environments block traffic that doesn't come from known addresses. For testing to run without interruptions, you need to authorize in advance the IPs Strike works from. This practice is known as IP allowlisting (or whitelisting).

Why it's necessary

If your firewalls, WAF, or access lists don't recognize Strike's IPs, test traffic may get blocked or flagged as suspicious. Authorizing them in advance prevents false blocks and ensures the assessment covers what's expected.

What to authorize

Add Strike's IPs to the allow-list (whitelist) of your firewalls, WAF, load balancers, and any other access control relevant to the assets in scope.

What the IPs are

  • 3.217.45.182/32

  • 52.4.41.179/32

  • 18.210.150.0/32

  • 3.91.124.199/32

What happens if you don't authorize the IPs

If your firewalls, WAF, or access lists don't recognize Strike's IPs, testing traffic may get blocked or flagged as suspicious. This causes false blocks and can prevent the assessment from reaching the full scope planned.

The concrete impact shows up in the pre-flight, the check Strike runs before executing testing to verify it can reach your assets. Depending on how your environment is configured:

  • Warning: if there are partial limitations — for example, filtering or rate limiting — the pre-flight can still pass, but with a warning. Testing runs, though coverage may be affected.

  • Failure: if Strike's traffic is blocked, the pre-flight fails because it can't reach the asset. In that case, you need to authorize the IPs to move forward.

Authorizing the IPs in advance prevents these cases and ensures the assessment covers what's expected.

FAQ

What IPs do I need to authorize for Strike to test?

Strike's four IPs: 3.217.45.182/32, 52.4.41.179/32, 18.210.150.0/32, and 3.91.124.199/32. Add them to the allow-list of your firewalls, WAF, load balancers, and other access controls for the assets in scope.

Where do I need to add the IPs?

In all access controls relevant to the assets in scope: firewalls, WAF, load balancers, and any access list.

Is "whitelist" the same as "allowlist"?

Yes. Both terms refer to the same thing: authorizing Strike's IPs in advance in your access controls. Depending on the tool you use, the feature may appear as "allow list" or "whitelist."

The pre-flight gave me a warning or failed. What should I do?

Check that Strike's IPs are authorized in your firewalls, WAF, load balancers, and other access controls. A failure usually indicates traffic is blocked; a warning indicates partial limitations that may affect coverage.