Understanding Your Email Validation Results (List Cleaning)
BulkMail’s email verification system assigns a result and code to each email address checked. These codes help you determine which emails are safe to send and which should be removed to protect your sending reputation, reduce bounce rates, and maintain POPIA compliance.
Result Table
| TEXT CODE | NUMERIC CODE | DESCRIPTION | SAFE TO SEND? |
|---|---|---|---|
| Syntax | 1 | Not a valid email format. | No |
| Spam Trap | 2 | Identified as a spam trap address. | No |
| Disposable | 3 | Temporary or fake email account. | No |
| Accept-All | 4 | Domain accepts all emails, validity cannot be confirmed. | Maybe – Not recommended unless using your own server |
| Deliverable | 5 | Confirmed, valid and reachable email. | Yes |
| Invalid | 6 | Address does not exist or is unreachable. | No |
| Unknown | 7 | Status cannot be determined. | No – Unless using a private server |
| Role | 8 | Generic role-based address. | Maybe – If the owner is known and consented |
Explanation of Each Result
Syntax (Code 1)
These are malformed addresses that are not valid emails. Examples: user@@example.com, [email protected] DON’T SEND – These entries are not logically correct and will always fail delivery.
Spam Trap (Code 2)
A spam trap is an email address used by ISPs or anti-spam services to catch senders using bad lists. These addresses are not used by real people and sending to them indicates poor list practices. DON’T SEND – Hitting spam traps can result in blacklisting and permanent damage to your sending domain or IP reputation.
Disposable (Code 3)
Created using services like Mailinator or 10 Minute Mail, these are often used for one-time form fills. They do not reflect real, engaged users and expire quickly. DON’T SEND – These addresses are unreliable, temporary, and not permission-based.
Accept-All / Catch-All (Code 4)
The server is configured to accept any address under the domain, even if the specific mailbox does not exist. These are common in business or government domains, but they often bounce later, especially when sent from third-party platforms.
- SAFE TO SEND – If you use your own email infrastructure with dedicated IPs.
- DON’T SEND – If you're using a shared IP or third-party provider with strict bounce thresholds.
Deliverable / Valid (Code 5)
The address has been confirmed as valid and able to receive mail. SEND – These are ideal for marketing, transactional, and newsletter emails.
Invalid (Code 6)
These addresses have been confirmed as incorrect or no longer active. Sending to invalids increases bounce rates and affects deliverability. DON’T SEND – Clean these from your list immediately.
Unknown (Code 7)
The server did not respond clearly during multiple verification attempts. This may be due to temporary server issues, strict firewalls, or unresponsive domains.
- SAFE TO SEND – If using your own private sending infrastructure.
- DON’T SEND – If using a shared platform or your bounce tolerance is below 4%.
Role (Code 8)
Generic email addresses like info@, sales@, or support@ typically go to multiple recipients and are not tied to a specific person. These may still be valid but often lack consent or engagement.
- SAFE TO SEND – If the contact explicitly subscribed or you have prior consent.
- DON’T SEND – If acquired from a public directory, purchase, or registration form.
Final Tips
- Always segment or exclude risky categories (Spam Traps, Invalids, Syntax Errors).
- Only send to Deliverable addresses, or cautiously to Accept-All/Unknowns if you're in control of sending infrastructure.
- Regular list cleaning improves inbox placement, protects IP reputation, and ensures POPIA compliance.
- Use BulkMail's email verification tools before each campaign to maintain high list quality.