About this video

This video uses sample data, not real Dropcontact data. Some column names may differ in your own file. BillionVerify is not affiliated with or endorsed by Dropcontact. File verification needs a paid account.

Video transcript

1. 00:00How Dropcontact labels an email

   Dropcontact labels each email with two words joined by an at sign. Here's how to read that label, and when a second check makes sense. The label has two parts. The left side says what kind of address it is. The right side says what kind of domain. nominative@pro is a verified work address for one person. catch-all@pro sits on a domain that accepts everything. generic@pro is a department. nominative@perso is personal, and Dropcontact says that needs consent. invalid@pro doesn't exist. And neither does a domain marked invalid. catch-all@pro deserves a closer read. Dropcontact gives you its best candidate, and it's upfront about the limit.

2. 00:46What changes in your file

   Your file also changes. If an address is invalid, Dropcontact moves it to the Note field, then looks for a new one to put in the Email column. So the Email column may not be what you uploaded. Download that file soon. Dropcontact keeps it for a limited time.

3. 01:02Should you verify again?

   Now the part to read carefully. Dropcontact advises against running its emails through another verifier after enrichment. Its reason: catch-all addresses it has validated can come back risky. We take that seriously. So don't recheck by reflex. A file you enriched today can go straight out. A second check earns its place when time has passed, when rows are marked no_validated, or when the list came from somewhere else. Time is the real reason. A label describes that day. People change jobs after it, and Dropcontact has a whole feature for detecting those moves.

4. 01:39Verify an aged file

   Upload the file to File List Verify. History records the date, so you can see how old this check is. Long runs carry on by themselves. Each result shows up as it lands, and we'll email you at the finish.

5. 01:52When labels disagree

   Your label stays in the file, next to our result. Expect some disagreement. A nominative@pro row can come back catch-all here. We ask the mail server, and that server says yes to everyone. That doesn't make the address bad. It means our check can't confirm it, and Dropcontact's label comes from its own method. So don't delete those rows. Send them as a separate, smaller batch, and judge by real bounces.

6. 02:19Route the rest

   Dropcontact splits bounces in two, and it helps. A hard bounce means the address is bad. A refuse bounce points at your own domain setup. If hard bounces show up, Dropcontact asks for the file and recredits legitimate ones. The rest maps cleanly. generic@pro is close to our role status. Dropcontact advises against sending to those, so keep them out of your main send. Hold unknown. Remove invalid and disposable.

7. 02:48What it costs

   Last, our credits. Each result is one credit, even catch-all or role. Bad syntax, disposable and unknown are not charged. The file route sits behind a paid account, and any purchase of credits opens it.

8. 03:01Get started free

   20 free credits every day you use your account, up to 600 a month. No credit card required. Start at billionverify.com.

Featured in this video