> For the complete documentation index, see [llms.txt](https://docs.does.qa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.does.qa/configuration/block-hostnames.md).

# Block Hostnames

Block Hostnames stops named hosts from loading during a Run. Use it when a third-party script injects a popup, banner, or other noise that makes a Test Case flaky.

## When to use it

* Quiet a marketing or chat popup that appears on only some loads.
* Keep analytics or widget domains from changing the DOM under test.
* Stabilise a journey that is otherwise correct when those hosts stay out.

## Find the hostname

1. Open the page in a normal browser.
2. Watch network requests on load for hosts that are not your application domain.
3. Note the hostname that serves the popup or script, such as `popup.example.com`.

Common third-party popup and lead-capture hosts include domains from Popup Maker, Elementor, OptinMonster, Sumo, Ninja Popups, Bloom, TrustPulse, WP Popups, Thrive Leads, and ConvertPlus. Use the exact hostname your page calls, not the marketing site name alone.

## Set blocked hostnames

{% stepper %}
{% step %}

## Open Runner settings

In DoesQA, go to **Settings → Runners**.
{% endstep %}

{% step %}

## Add the hosts

Find **Hostnames To Block (comma separated)**.

Enter one or more hostnames, separated by commas, for example:

`api.ads.example.com,popup.example.com`
{% endstep %}

{% step %}

## Save and re-run

Save the Runner options, then run the Flow again. Confirm the popup or script no longer appears in the journey.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Pro tip:** Block only the hosts that interfere. Leave your application API and asset hosts unblocked so the journey still exercises the real stack.
{% endhint %}

## Related

* [Whitelisting IPs](/configuration/whitelisting-ips.md)
* [Max Concurrency](/configuration/max-concurrency.md)
* [Open](/test-steps/starter/open.md)