Frequently Asked Questions

What is a catch‑all email address?

A catch‑all mailbox receives mail sent to any address at your domain, even if the specific alias doesn’t exist.

Why does a catch‑all increase spam risk?

Spammers often blast common aliases (info@, sales@, admin@). A catch‑all guarantees those messages reach your server instead of bouncing.

How do you calculate the risk score?

We check public leak datasets, paste sites, and search indices for standard aliases at your domain, then weight findings into Low/Medium/High.

Do you store my domain input?

No—queries are processed on‑the‑fly. We don’t log or save the domains you test.

Is this a replacement for spam filtering?

No—it helps you decide whether to run a catch‑all in the first place. You should still use robust spam filtering if you keep one enabled.

Can I whitelist specific aliases only?

Yes—most providers let you disable catch‑all and create explicit aliases instead, greatly reducing random spam.

Does disabling catch‑all hurt deliverability?

No—legitimate senders will target valid addresses. Unknown senders will get a bounce, which is normal and DMARC‑friendly.

Can I use this tool for multiple domains?

Absolutely—check as many domains as you like. Great for MSPs or email hosting resellers.

Is there an API version?

Coming soon—join the wait‑list in the footer to get early access to JSON endpoints.

Does this tool cost anything?

It’s free for manual checks. Enterprise API & bulk reports will have tiered pricing.