Skip to content

Book a call

Email address verification before a campaign: what to check beyond the address itself.

Email verification before a campaign consists of several separate checks: syntax, the domain and its MX record, the server's response, and whether the domain accepts every address. On top of that comes a question that no technical test will settle: whether the address belongs to the right person at the right company.

Published
Updated
Reading time
6 min
Category
Profile and data
Author
DYNTRO team

Why verify addresses if the contact list looks good?

An address that looks correct does not necessarily work. People change jobs, companies merge and change domains, and former employees' mailboxes are closed. Every such address in a campaign ends in a bounce, i.e. the message being returned by the recipient's server.

A few bounces are not a problem. Many bounces in a short time signal to mailbox providers that the sender does not look after its list. In its sender guidelines, Google recommends reducing volume when messages start to bounce and removing from the list addresses that have bounced several times. Verification before the start limits this problem before it even appears.

What does email verification check?

Verification has several layers. Each filters out a different type of error.

LayerWhat it checksWhat it filters out
Syntaxwhether the address is written correctlytypos, spaces, a missing @ sign
Domainwhether the domain exists and has an MX recordexpired or taken-over domains, domains with a typo in the name
Serverwhether the server will accept a message to this addressmailboxes that no longer exist
Catch-allwhether the domain accepts every addressaddresses the server will not confirm

The MX record indicates the server that receives email for the domain. If the domain does not have one, the SMTP standard (RFC 5321) allows email to be delivered to the domain's own IP address. A missing MX record is therefore not proof of an error, but it is a reason to take a closer look at that company.

Why does the server not always tell the truth about an address?

The SMTP standard has a VRFY command which, as its name suggests, is for verifying addresses. However, RFC 5321 allows servers to disable it for security reasons. The server then responds with code 252, which means roughly: I cannot verify this user, but I will accept the message and attempt to deliver it. Such a response confirms nothing.

Then there are catch-all domains. Their server accepts a message to any address in the domain, including a made-up one. The test will then show “accepted” both for a director's real mailbox and for an address with a typo. It also happens that a server accepts a message during sending and sends the bounce back only later.

In practice, the verification result is therefore not binary: an address may be confirmed, rejected or impossible to confirm. This last state has to be flagged separately. In DYNTRO campaigns, we verify addresses before sending and handle catch-all and unknown addresses with caution.

Does a valid address belong to the right person?

A technical test will not answer this question. An address may exist and accept email, yet belong to someone other than the person in the contact list. That is why, in addition to the test, it is worth checking the consistency of the whole record:

  • whether the first name and surname match the address, e.g. the address contains this person's first name or surname, not someone else's;
  • whether the address domain belongs to the company in the record, and not to its former brand, a company from another group or an entirely different company;
  • whether the job title and company are current, i.e. the person still works there and still deals with this area.

At DYNTRO, we check the company's website and how up to date the data is for this purpose. An inconsistent record is better corrected or removed than sent. A message to the wrong person is not just wasted. It can also end in a spam complaint, because the recipient does not understand why they received it.

What should you do with generic addresses such as office@ or info@?

Generic addresses are flagged separately. Behind office@ or info@ there is no specific person, just a mailbox read by reception, an assistant or several people at once. A message written to a sales director that lands in such a mailbox rarely reaches them.

A generic address can be useful when there is no other way to contact the company, but then the message should be written to the company and not pretend to be a letter to a specific person. In most cases, it is better to find the right person or leave the company out of this campaign.

Does a valid address mean it is worth sending?

No. Verification answers the question of whether the message has a chance of arriving. It does not answer whether it should be sent at all. That depends on how well the company and the person fit the ideal customer profile and on the exclusion list.

That is why it is worth making the “send” decision only when the record passes both assessments:

  • technical: the address is confirmed, the domain works, the record is consistent;
  • business: the company matches the profile, the person has the right role, the company is not on the exclusion list.

In the business assessment, at DYNTRO we assess company fit and job title fit separately.

A record that passes only the first assessment is a good address of the wrong person. A record that passes only the second is the right person whom the message may not reach.

When should you verify the contact list?

Ideally just before sending, not once at the start of the project. A contact list prepared a few weeks earlier will already be partly out of date. If the campaign runs longer, it is also worth checking further batches of contacts before adding them to the send.

Verification is not the end of dealing with bounces. During the campaign, you still need to read returned messages and remove addresses that bounce. Preparing the contact list is one of the campaign stages on which all the following ones depend.

Example of assessing records in a contact list

Example records, people and addresses; domain example.com.

RecordTest resultDecision
Anna Nowak, operations director, anna.nowak@example.comconfirmedsend if the company matches the profile
Jan Kowalski, CEO, j.kowalski@example.com, catch-all domaincannot be confirmedflag separately, send only if the data is certain
Piotr Wiśniewski, finance director, address in a different domain from the companyconfirmedclarify whether it is the same company
office@example.comconfirmedgeneric address, flag separately

Summary.

  • Verification has several layers: syntax, the domain and MX record, the server's response, and checking whether the domain accepts every address.
  • A server may not confirm an address, and a catch-all domain will accept any. Such addresses are flagged separately.
  • A valid address still needs to be compared with the first name, surname, company and job title.
  • A technical result is not a decision to send. That decision depends on the fit with the customer profile.

We run email and LinkedIn campaigns to decision-makers, from data and domains to replies, while your salespeople focus only on conversations. See the service: B2B email campaigns.

Book a call

Questions and answers.

Does verification guarantee no bounces?

No. Some servers do not confirm addresses, or they accept every message and send a bounce back only later. People also change jobs, so an address that is valid on the day of the check may disappear before sending. Verification reduces the number of bounces but does not rule them out, which is why bounces are also checked during the campaign.

What should you do with catch-all addresses?

Flag them separately and do not treat them as confirmed addresses. The server of such a domain accepts every address, so a test will not tell you whether the mailbox exists. It is worth sending to such addresses only when the first name, surname, job title and company are certain, and only as a smaller share of the contact list, so that any bounces do not harm the campaign domain.

Sources.

Related articles.

All articles

Let's start talking to the right companies.

Leave your details.

Your answer helps us see which channels bring enquiries.

DYNTRO sp. z o.o. processes the data from this form to reply to your enquiry. More in our privacy policy.

What happens next.

  1. On the first call, we define your customer profile, market and exclusions.
  2. We choose the scope: email, LinkedIn or both channels, in one or several segments.
  3. If working together makes sense, you receive a proposal with terms for your company.

Prefer email? kontakt@dyntro.pl