MailSlurp logo

support

MailSlurp Domain Pool Support Guide

Understand how MailSlurp domain pools work, when to use pooled domains, and how to combine pool usage with custom domains for resilient testing workflows.

MailSlurp domain pools let you create inboxes across multiple MailSlurp-managed domains instead of relying on a single suffix. This is useful for test resilience and routing validation when one domain pattern is filtered or blocked in a target system.

What is a domain pool

A domain pool is a rotating set of MailSlurp-owned inbox domains that can be used when creating inboxes. Instead of always receiving addresses ending in @mailslurp.com, pooled inboxes may use alternative managed suffixes.

When to use domain pools

Use pooled domains when you need to:

  • Test systems that treat different sender/recipient domains differently.
  • Reduce dependence on one domain suffix in large QA programs.
  • Validate routing and filtering rules under varied domain conditions.

For strict brand consistency or production sender reputation, your own verified domain is usually a better fit.

Domain pool vs custom domain

Choose based on intent:

  • Domain pool: fastest way to diversify test inbox suffixes.
  • Custom domain: best for production-like sender identity and brand alignment.

You can combine both in larger programs: pooled domains for broad automation coverage, custom domains for release-candidate and policy-sensitive tests.

See custom domain setup for verified-domain workflows.

Operational notes

  • Keep test assertions flexible enough to accept approved pool domains.
  • Do not hardcode a single suffix if domain diversity is intentional.
  • Track deliverability behavior by domain in your test telemetry.
  • Pair domain pool usage with webhook-based event monitoring.

For event handling, see email webhooks.

Troubleshooting

If your flow is still being blocked:

  • Confirm whether target systems allow test-domain traffic.
  • Check if allowlists are pinned to a single suffix.
  • Validate SPF/DKIM/DMARC expectations for production-like tests.
  • Use email deliverability testing to isolate policy vs content issues.