Help collection
List verification
Catch-all detection by SMTP probing. Eight verdicts, nothing ever delivered.
How to verify an email list before sending
Upload or API-verify the list before the first campaign mail. EmailPal probes catch-alls over SMTP (RCPT TO only, nothing delivered) and returns eight verdicts so you are not paying for bounces with reputation.
Use your list check results
What each List check result means, why role accounts count as safe, the 8% line for saving to a list or campaign, and how to download results, save them as a contact list or add them straight to a campaign, with your original columns if you attach the file.
List verification by EmailPal
EmailPal verifies addresses before you send so catch-alls and disabled mailboxes do not become bounces on a warmed IP. Eight verdicts, SMTP probes that never deliver a message, daily allowances on every plan, and the same engine on the dashboard, REST and MCP.
Verification verdicts
What safe, catch-all, role, disposable, inbox full, disabled, invalid and unknown mean on an EmailPal verification result — and whether you should send to each one.
What is a catch-all email?
A catch-all (accept-all) domain accepts mail to any local-part, so "is this person real?" cannot be answered from SMTP. EmailPal flags catch-alls as their own verdict instead of calling them valid.
Catch-all detection
How EmailPal detects catch-all domains by probing a mailbox that cannot exist before trusting RCPT TO on your contact. Catch-alls are their own verdict, never a valid you cannot rely on.