1
Clear address failures
Find malformed addresses, invalid domains, and strong negative mailbox responses that can create avoidable hard bounces.
Pre-send bounce-risk review
Check a list for avoidable bounce risksUse evidence, not a prediction guarantee
Paste addresses or upload a CSV to find clear failures and review uncertain conditions before sending. Verification can reduce avoidable bounces, but no pre-send check can predict every future delivery response.
- Input
- Paste addresses or upload CSV
- Output
- Verdicts with supporting signals
- Fair billing
- Unknown results do not use credits
What it means
A bounce happens when an actual message is rejected
Before a send, address verification can identify evidence that makes a bounce more or less likely: address structure, domain configuration, receiving-server responses, and conditions such as catch-all or inbox-full. The final outcome still depends on the mailbox and server at send time, plus the sender, message, and receiving policy.
Useful context
What a pre-send bounce review can surface
2
Temporary or policy-sensitive conditions
Keep inbox-full, disabled, catch-all, role-account, disposable, and similar signals separate from clear failures so they can be reviewed deliberately.
3
No decisive response
Receiving servers can hide recipient status, throttle checks, or fail temporarily. Peopledat labels inconclusive results as unknown and does not deduct credits for them.
The dashboard workflow
From raw list to a usable decision
No developer integration is required. Work through a list in the browser and keep the result attached to the address.
- 01
Paste or upload
Sign in to the dashboard, create a list, then paste email addresses or upload a CSV. Keep the original file as your source of record.
- 02
Run verification
Peopledat processes the list and returns verdicts with the supporting signals available for each address.
- 03
Review and export
Inspect uncertain and risk-marked results, decide what fits your sending policy, and export the list for your next workflow.
Read the result
Verdicts are decision support
Keep the verdict and its context together. A single label cannot account for consent, engagement, sender reputation, or a receiving server changing its behavior later.
Safe
The available checks support using the address. It is a positive verification signal, not a promise of delivery or inbox placement.
Invalid
The checks found a strong reason not to use the address, such as invalid structure, domain, or mailbox response.
Review the signal
Catch-all, disposable, role-account, inbox-full, disabled, and similar conditions need a policy decision rather than one universal rule.
Unknown
The receiving system did not provide a decisive answer. Peopledat does not deduct credits for results classified as unknown.
Put the result to work
Use verification before—and bounce data after—the send
Hold clear invalids
Exclude strong negative results from the next send while keeping the original source and result available for review.
Segment uncertain results
Apply a policy suited to catch-all, risky, and unknown addresses rather than assuming they will either bounce or deliver.
Use post-send evidence too
Feed actual hard and soft bounces, suppressions, complaints, and engagement back into your list-maintenance process after each campaign.
Clear limits, so you can use the result responsibly
- Email verification cannot guarantee delivery, inbox placement, engagement, or future mailbox availability.
- Receiving servers may hide mailbox status, throttle checks, or accept every recipient. Those cases can remain uncertain.
- Risk flags are context, not proof of fraud, consent, or a person's intent.
- Use the dashboard for list work, the versioned REST API for server integrations, or the origin-bound widget for advisory form checks. No official SDK is required.
Questions, answered plainly
Frequently asked questions
What can an email bounce checker find before sending?
Address verification can find clear structure, domain, and mailbox failures and surface conditions associated with higher uncertainty. That can reduce avoidable bounces, but it cannot observe the final response to a message that has not been sent.
Can Peopledat predict every hard and soft bounce?
No. A mailbox can fill up, a server can fail, a domain can change policy, or a recipient can disappear after verification. Message size, authentication, sender reputation, and content can also cause a later rejection that an address check cannot predict.
What should I do with risky or catch-all results?
Keep them separate from clear invalids and stronger positive results. Consider consent, source, prior engagement, the cost of a bounce, and your sending policy before deciding whether to send, suppress, or review them further.
Does verification replace bounce processing after a campaign?
No. Continue processing actual delivery failures and maintaining suppression lists in your sending platform. Pre-send verification and post-send bounce handling solve different parts of list hygiene.
Related email verification guides
Bring a list. Leave with a clearer decision.
Paste addresses or upload a CSV, review the evidence behind each result, and pay nothing for verdicts classified as unknown.
Create an account