1
Address and domain readiness
Find malformed addresses and domains that do not appear configured to receive email before they enter your sending workflow.
Pre-send address verification
Check email-list deliverability signalsKnow what the evidence can—and cannot—tell you
Paste addresses or upload a CSV to review address, domain, mail-server, and mailbox signals before sending. Peopledat helps you improve a list decision; it does not predict inbox placement.
- Input
- Paste addresses or upload CSV
- Output
- Verdicts with supporting signals
- Fair billing
- Unknown results do not use credits
What it means
Address verification is one part of email deliverability
A verification result can identify clear address failures and conditions that need review before a send. It cannot measure your sender reputation, inspect message content, or show whether a future campaign lands in the inbox or spam folder. Those outcomes depend on the sender, message, recipient, and mailbox provider as well as the address itself.
Useful context
The pre-send evidence Peopledat provides
2
Receiving-server evidence
Review SMTP connectivity and mailbox-response signals when the receiving server is willing to provide a useful answer.
3
Conditions that remain uncertain
Keep catch-all, disposable, role-account, inbox-full, disabled, and unknown conditions visible so they can receive an appropriate policy decision.
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
Turn verification into a responsible sending decision
Separate clear failures
Keep strong invalid results out of a campaign import while retaining the original list and verification evidence as your source of record.
Review uncertain addresses
Segment catch-all, risky, and unknown results instead of treating every technical response as a promise that a future message will be delivered.
Pair verification with sending controls
Use authentication, consent, suppression, sender-reputation, content, and post-send bounce data alongside address verification.
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 does Peopledat check before I send?
Peopledat presents available syntax, domain, mail-server, mailbox, and risk signals for addresses in a pasted list or uploaded CSV. The evidence varies because receiving systems do not all disclose the same information.
Does this test inbox or spam-folder placement?
No. Peopledat verifies address-level signals; it does not send a campaign, seed messages into mailbox-provider accounts, or measure where a message lands. Inbox placement also depends on sender reputation, authentication, message content, recipient behavior, and mailbox-provider filtering.
Does a deliverable verdict guarantee delivery?
No. It reflects the evidence available when the address is checked. Mailboxes and receiving-server policies can change, and a later message can still be blocked, bounced, filtered, or rejected for reasons outside the address check.
Does Peopledat detect spam traps?
Peopledat does not market a definitive spam-trap database or spam-trap guarantee. Use the displayed address and risk signals as decision support, and combine them with the consent, source, suppression, and engagement evidence in your own systems.
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