Skip to main content
This step has two parts: defining the URLs Mjolnir will test, and verifying it can actually reach them. Both happen on the same page.

​
Part A: Target URLs & custom headers

​
Adding target URLs

Enter the URLs that make up your application’s scope. These are the endpoints Mjolnir will test.
You can add multiple URLs. Each one gets its own connectivity check and can have its own custom headers.
Only add URLs you own and are authorised to test. Mjolnir will send real HTTP requests, including probes that may look like attack traffic, to everything in scope.

​
Custom headers

Each URL can have custom HTTP headers attached. These are sent with every request Mjolnir makes to that URL. Common uses: Click Add header under any URL to add key/value pairs.
Not sure what headers to add? If your application uses a WAF like Cloudflare or AWS WAF, see Part B below. Allowlisting our IPs is usually more reliable than header bypasses.

​
Part B: Connectivity check & allowlisting

Once you’ve added your URLs, Mjolnir runs an automatic connectivity check. This takes a few seconds per URL.

​
Status indicators

​
If you see ⚠️ or ❌

You’ll need to add Mjolnir’s IP ranges to your allowlist. This tells your WAF, firewall, or CDN to let our traffic through without interference. See the full allowlisting guide:

How to set up an allowlist for Mjolnir

Step-by-step instructions for Cloudflare, AWS WAF, and others
Once you’ve updated your allowlist, click Re-run check to confirm the issue is resolved.

​
Proceeding with connectivity issues

You can proceed even if connectivity issues remain, but you’ll see a persistent warning banner. Unresolved connectivity issues will reduce test coverage because Mjolnir may miss endpoints it can’t reliably reach.

Next: Code & Documentation

Select source repositories and upload supporting documentation