What counts as a role address
Some role names are standardised. RFC 2142 reserves mailbox names such as postmaster, abuse, webmaster, info, support, sales and marketing for the functions they describe. Over time, organisations have added many more, such as admin, billing, careers, contact, hello, help, office, press and team.
- Contact points: info@, contact@, hello@, office@.
- Departments: sales@, marketing@, support@, billing@, hr@.
- Technical: admin@, webmaster@, postmaster@, abuse@, noc@.
Why they are risky for marketing
Nobody personally signed up to receive your newsletter at sales@. Several people may see the message, any of them can mark it as spam, and the person who handles the mailbox may have left months ago. Complaints from a shared inbox count the same as complaints from anyone else.
Some role addresses, such as abuse@ and postmaster@, exist to receive reports about mail problems. Sending promotional email there is a poor look and can attract complaints directly. Others are forwarded to automated systems that never read the content.
When it is fine to email them
Role addresses are not always wrong. A small business may use hello@ as its only inbox, and transactional email such as invoices to billing@ is exactly what that mailbox is for. B2B outreach to a generic address can also be legitimate when you have no named contact, as long as you follow the consent and unsubscribe rules that apply in your region.
The point is to make the decision on purpose. Do not mix role addresses into a marketing list by accident and treat their results as if they came from engaged people.
How to filter them
You can match the local part against a list of known role names, but the list is long and a plain match misses variations. Email verification does this for you. VeriDock marks role addresses as risky with the reason role_account, so you can write your own rule: exclude them from marketing, keep them for transactional email, or review them by hand.
const { status, reason } = await veridock.verify(email);
if (status === "risky" && reason === "role_account") {
// Keep for invoices and account notices, skip for newsletters.
return { marketing: false, transactional: true };
}A simple policy
For newsletters and promotions, suppress role addresses by default. For product and billing notices, send to them. For cold outreach, prefer a named person, and if you must use a role address, send fewer messages and make unsubscribing easy.
A role address is not invalid. It is a different kind of recipient, and it deserves its own rule.
Key takeaways
0/4Try it on a real address
Run syntax, DNS, MX, disposable, and role checks on any address. No signup needed.
Enter an address and press Check.
Runs real syntax, DNS and mail-server checks.
This demo checks syntax, domain, mail server, disposable and role-address rules. Sign up free for live mailbox checks.
Frequently asked questions
Verify addresses with one API call.
250 free checks to start, no card required. Unknown results are never billed.