How I Use Hunter.io Email Verification to Clean Bulk Lists
A stale contact list can waste time and create avoidable bounces. Hunter.io’s Bulk Email Verifier gives you a way to check a list before you use it. The basic process is simple: keep an untouched copy, remove duplicates, upload a small test...
A stale contact list can waste time and create avoidable bounces. Hunter.io’s Bulk Email Verifier gives you a way to check a list before you use it. The basic process is simple: keep an untouched copy, remove duplicates, upload a small test, review each result, and export only the segment you are allowed and ready to contact.
This guide is based on Hunter’s public product, pricing, help, and privacy documentation checked on September 23, 2026. It is a documentation-based walkthrough, not a report of a hands-on test. Verification can help find address problems, but a “valid” result does not guarantee delivery, inbox placement, or that a real person will read your message.
What Hunter email verification checks
Basic email validation checks whether an address is shaped correctly. Verification goes further. Hunter says its verifier checks an address’s format, temporary-mail and webmail status, domain mail records, and the mail server. It contacts the server without sending an email. Hunter’s published list of checks includes:
- Format and syntax: Hunter checks whether the address follows a usable email format. It also screens for addresses that look like random or gibberish strings.
- Disposable domains: Hunter checks whether the address uses a domain associated with temporary inboxes. A temporary address is not the same thing as an ordinary email address that happens to be new.
- Webmail: Hunter identifies consumer services such as Gmail or Yahoo. Webmail is a type of address, not proof that an address is bad. Hunter says webmail addresses can still be verified.
- MX records: Mail exchange, or MX, records point a domain to the mail servers that receive its email. A missing MX record can mean the domain is not set up to receive mail.
- Mail-server and SMTP check: SMTP means Simple Mail Transfer Protocol. Hunter checks whether it can connect to the server and asks the server about the specific mailbox. This is a technical check, not a message sent to the recipient.
- Accept-all or catch-all detection: Some domains accept mail addressed to any mailbox name, including names that do not exist. Hunter checks for this setup because it makes an individual mailbox harder to confirm.
These are Hunter’s documented checks. They should not be treated as a checklist for every email-verification service. Hunter’s public verifier documentation does not promise that it can find every spam trap or classify role addresses such as info@ and sales@ as a separate status.
What a verification result can and cannot tell you
A verifier looks for technical signals at the time of the check. Mailboxes can be removed, filled, or changed afterward. Some mail servers also block verification or give too little information to confirm a mailbox. Hunter returns an Unknown result when it cannot complete a check. Its documentation also describes a Blocked outcome when a server blocks the verification attempt.
Catch-all domains create a different problem. The domain server may accept every address, so a response from the server does not prove that a particular person’s mailbox exists. Secure email gateways or other server protections can also limit the signals a verifier can see. A result can therefore be unclear even when the address is real. Hunter’s verification FAQ says no check is 100% certain and that even a valid address can bounce later.
Verification also does not establish that the person is still at the company, wants your message, or has agreed to receive it. It cannot tell you that a message will avoid spam filters. Treat the result as one input to a contact decision, not permission to send.
Hunter status guide: keep, suppress, retest, or review
Hunter’s exact status labels can change as its product develops. Check the result in your account and compare it with Hunter’s current status definitions. Use this table as a cautious action guide, not a guarantee that an address is safe to email.
| Hunter result or category | What it means | Practical next step |
|---|---|---|
| Valid | Hunter’s checks support that the address can receive mail at the time of verification. | Keep it eligible for review. Confirm permission, relevance, and suppression status before sending. Recheck near the send date for an old or large list. |
| Invalid | The address failed checks or cannot receive email. | Suppress it from the campaign. Correct an obvious typo only from a reliable source, then verify the corrected address. |
| Disposable | The address uses a temporary-email domain. | For business outreach, usually suppress it. For a customer signup, follow your own account and fraud rules instead of assuming every temporary address has the same meaning. |
| Accept-all / catch-all | The domain accepts mail for addresses that may not exist, so the mailbox is uncertain. | Keep it separate from Valid. Review the source and Hunter confidence score. Hunter suggests prioritizing Accept-all addresses above 85%, but a higher score is still not a promise of delivery. If the contact matters, confirm it through a trusted source or another channel. |
| Unknown or Blocked | The server did not give enough information, timed out, or blocked the check. | Do not re-label it as valid. If the contact is important and the list is permitted, retry later or review it manually. Otherwise, leave it out of a broad send. Hunter says Unknown and Blocked results do not use verification credits. |
| Webmail | A provider type, such as Gmail or Outlook, not automatically a failed verification. | Use it only when it fits the purpose and your contact rules. Check the verification status separately. |
| Role address | A shared inbox such as info@, sales@, or support@. Hunter does not document this as a separate verifier status. | Tag it in your source file and decide whether a shared inbox is a suitable recipient. Do not treat a technically valid role address as a named person. |
Hunter recommends using the confidence score especially for Accept-all results. Its guidance says to prioritize scores above 85%, but the score is an estimate, not a live mailbox check. Do not use it to override an Invalid result or to ignore consent and suppression rules.
A practical bulk-verification workflow
- Keep the original file. Save an untouched copy with its source, collection date, and permission notes. Work from a duplicate so you can compare records or restore fields later.
- Review your right to contact people. Remove unsubscribed contacts, complaints, and records that your organization should not use. Verification does not make a purchased, scraped, or otherwise unsuitable list acceptable.
- Clean and deduplicate the copy. Remove blank rows, fix clear formatting mistakes from a trusted source, and check repeated email values in your spreadsheet. Hunter’s bulk help does not promise to deduplicate a file for you. Its pricing page says repeated verifications are counted once per calendar month, but that is not a reason to leave duplicate rows in your working file.
- Run a small test first. Use a small, representative sample to confirm that you chose the right email column and that the results export as expected. A test also helps you estimate the credits needed before you start a larger job.
- Upload a copy to Hunter. The Bulk Email Verifier accepts CSV uploads and pasted addresses. Hunter’s product and FAQ pages also list TXT files. For pasted lists, Hunter says to put one address on each line or separate addresses with commas. Check Hunter’s live screen before processing if your file has several columns.
- Start verification and watch the job. Hunter says processing starts automatically and you can leave the page while results finish. The public bulk help page does not state a fixed completion time or a numeric file-size or row limit. Do not promise yourself a specific turnaround. A bulk operation starts using credits when launched. If you spot a problem, Hunter lets you cancel and reports how many addresses were processed and how many credits were used.
- Export and review the results. Separate Valid, Invalid, Disposable, Accept-all, and Unknown or Blocked records. Keep original fields that help you identify the source and permission basis.
- Import only the approved segment. Keep suppressed and uncertain records out of the sending list unless a person has reviewed them and your contact rules allow their use. Save the export and note when it was checked.
Hunter does not publish a fixed bulk processing time, maximum upload size, or maximum row count in the bulk help pages reviewed for this article. If a file fails or behaves unexpectedly, try a small CSV with a clear email column, use the copy-and-paste option, and consult Hunter support. Avoid guessing at limits that Hunter has not documented.
Bulk upload, Google Sheets, or API?
| Option | Best for | Useful details |
|---|---|---|
| Bulk Email Verifier | A one-time cleanup or a periodic list audit. | Upload CSV or TXT where available, or paste addresses. Export the report and review uncertain statuses before importing to your sender. |
| Hunter for Google Sheets | Teams that already work in a spreadsheet and want repeat checks beside their source data. | The add-on creates a new tab with addresses, statuses, confidence scores, and source counts. Hunter’s help page says you can select up to 1,000 addresses per verification run. |
| Email Verifier API | Developers checking an address during signup, lead intake, or a CRM workflow. | Use a server-side integration, protect the API key, handle delayed responses and errors, and avoid blocking a good user just because a server returns Unknown. Test the flow before relying on it. |
Hunter’s Sheets guide explains how verification results appear in a new tab. Its API guide covers real-time and automated checks. Pick the lightest workflow that fits the job. A periodic spreadsheet does not need a custom integration, while an API is useful when checks must happen as new records enter a system.
Hunter verification pricing and credits
Hunter’s pricing page lists 0.5 credit per verified email on its All-in-One plans. Unknown or Blocked checks that Hunter cannot complete are not charged. Credits are shared across some Hunter tools, so the table below is a way to compare the subscription allowance, not a promise that all credits are reserved for verification. Prices and allowances were checked on September 23, 2026. Review Hunter’s live pricing page before buying because plans and prices can change.
| Plan | Price shown | Credits | Approximate cost per 1,000 verified addresses* |
|---|---|---|---|
| Free | $0 | 50 per month | Up to 100 checks included |
| Starter | $49 monthly, or $34 per month billed yearly | 2,000 per month, or 24,000 per year | About $12.25 monthly, or $8.50 yearly |
| Growth | $149 monthly, or $104 per month billed yearly | 10,000 per month, or 120,000 per year | About $7.45 monthly, or $5.20 yearly |
| Scale | $299 monthly, or $209 per month billed yearly | 25,000 per month, or 300,000 per year | About $5.98 monthly, or $4.18 yearly |
| Enterprise | Custom | Custom | Ask Hunter for a quote |
*Estimate assumes every plan credit is used only for email verification and divides the plan price by its potential verification volume. Hunter credits are shared with other tools, so this is an allocated comparison, not the extra cash cost of one more check. Your actual cost depends on plan use, billing, and how many credits are left.
Worked example: a 1,000-address list
If Hunter completes all 1,000 checks, the list uses up to 500 credits because each verified email costs 0.5 credit. If 100 addresses return Unknown or Blocked, those checks are not charged, so the remaining 900 completed checks use 450 credits. If you have enough unused plan credits, the job may not create an additional bill. On Starter, 500 credits are one quarter of its 2,000-credit monthly allowance. The subscription cost allocated to that quarter is $12.25 at the monthly rate or $8.50 at the listed yearly rate, assuming no credits go to Hunter’s other tools.
Monthly plan credits reset at the end of the billing cycle and do not roll over. Yearly plan credits last for the year and unused credits expire at the end of that 12-month period. Hunter’s help page says purchased credit packs last three months, and their exact price depends on plan and quantity. For example, its current credit-pack page lists 1,000 credits at $70 for Starter, $52.50 for Growth, and $35 for Scale. Since 1,000 credits can cover up to 2,000 completed verifications, use the checkout price and your plan’s shared-credit rules when estimating a top-up. Free accounts cannot buy credit packs. See Hunter’s credit rollover rules and credit-pack details.
Privacy and handling uploaded contact data
An email list can contain personal data. Before uploading it to any third-party service, check that you have a valid reason to process it, that your privacy notice covers the use, and that the upload fits your organization’s policies and applicable law. Send only the fields needed for the check, limit who can access the list, protect exports, and remove working copies when your retention policy allows.
Hunter’s Privacy Policy says email search and verification history is retained for three months. The public policy reviewed here does not give a separate, specific retention schedule for every original bulk-upload file or explain exactly how each uploaded list is deleted. Do not assume the source file disappears immediately. For a clear answer about a particular upload, deletion request, or processing agreement, contact Hunter at privacy@hunter.io and review the current policy before sending the data.
Verification is only one part of deliverability
Verification can reduce avoidable address-related bounces. It does not guarantee inbox placement or fix a weak sender setup. Before sending, use this checklist:
- Permission and relevance: Contact people only under a lawful and appropriate basis. Keep consent and source records where required.
- Suppression: Remove unsubscribed contacts, complaints, and addresses your organization has told you not to contact.
- Authentication: Set up SPF, DKIM, and DMARC for your sending domain and check that they pass.
- List quality: Use recent, relevant contacts. Suppress Invalid results and handle Accept-all and Unknown records with care.
- Sending practices: Use accurate sender details, useful messages, and a clear way to opt out. Do not treat a verified result as permission for unsolicited email.
- Monitoring: Watch hard bounces, soft bounces, spam complaints, replies, and unsubscribe rates. Check provider reputation tools and blocklist signals as part of a wider review, not as a promise of inbox placement.
Bottom line
Hunter’s Bulk Email Verifier is a practical option for checking a list before it enters a campaign. Preserve the source file, deduplicate it yourself, test a small sample, and separate Valid addresses from Accept-all, Unknown, and other statuses. Use a result to guide review, not to promise delivery. Then check permission, suppression, authentication, and campaign performance before you send.
