# When should I use a catch-all address instead of an alias?

Canonical URL: https://help.iagenify.com/faqs/mail/when-should-i-use-a-catch-all-address-instead-of-an-alias

[← Back to Mail FAQs](https://help.iagenify.com/faqs/mail)

HELP CENTER · FAQ Mail 2 min read
# When should I use a catch-all address instead of an alias?
An alias maps a specific alternate address, while a catch-all handles otherwise unrecognized addresses for a host. The catch-all can be useful for broad intake, but it also accepts mail sent to mistyped or unwanted names.
IaGenify
Mail

## Choose based on how specific the address should be
Create an alias when you know the exact additional address that should reach a mailbox. This makes the route explicit and helps you control which alternate names are valid. Use a catch-all only when you intentionally want unmatched addresses at that host to reach a designated destination.
Because a catch-all can receive messages for many unplanned names, consider whether the recipient can handle the extra volume and whether messages may contain sensitive information. It may make typos easier to receive, but it can also attract unsolicited mail and make it harder to notice that someone used the wrong address.
## Test resolution order and maintain the rule
Before relying on the setup, test a known mailbox address, a configured alias, and an address that matches neither. Confirm each message reaches the intended destination. Mail routing resolves an exact address before an alias and the catch-all, so test cases should reflect the addresses people will actually use.
Review the catch-all destination when a mailbox or alias changes, and remove the rule if broad acceptance is no longer needed. Keep one clear owner responsible for monitoring the destination. If a particular address should not be accepted, use a specific mailbox or alias policy rather than assuming the catch-all can distinguish the sender's intent. [← Back to Mail FAQs](https://help.iagenify.com/faqs/mail)