Getting Started
Updated 2026-04-075 min read

Verify Your First Email

Run a single verification, read the result object, and understand what SendSure checks before you move into bulk workflows.

Verify your first email

The fastest way to understand SendSure is to run one manual verification and inspect the result before you upload a file or wire the API.

Start in the manual checker

Go to /manual, paste a single email address, and run the check. Use a real address that you understand well, not a throwaway address you do not control.

The first check is meant to answer three questions:

  1. Did the platform return quickly?
  2. Did the status make sense for the address you tested?
  3. Do you understand what action to take from the result?

If the answer to any of those is no, read the result guide before you scale up.

Read the fields that matter

Focus on these parts of the response first:

  • standard_status: the normalized operational outcome you should act on
  • reason: the plain-English explanation for the outcome
  • quality_score: the confidence and quality signal for downstream decisions
  • recommended_action: the next best operational move

Do not over-optimize on one field alone. The status and reason should lead your decision, and the score should support it.

What a healthy first result looks like

A healthy first result does not just mean valid. It means you can explain why the platform returned that outcome.

Examples:

  • valid: the address passed the verification path and is generally safe to keep
  • invalid: the address should be suppressed from future sends
  • risky: review your policy before sending
  • unknown: wait for retries or use the address more carefully

For a deeper breakdown, continue to Results and Statuses.

Common first-check mistakes

Testing with bad examples

If you test with obvious garbage addresses, you only learn that the syntax layer works. Test at least one address that could plausibly be real.

Expecting every mailbox to return certainty

Some providers are intentionally difficult. A first unknown result does not mean the platform failed. It means certainty was not available at that moment.

Treating risky as valid

Risky is not a soft version of valid. It exists so you can apply policy intentionally.

What to do next

Once you are comfortable reading one result:

  1. Upload a small CSV and run the analysis flow.
  2. Review the Upload Your First List guide.
  3. If you plan to validate addresses at signup, move to the API quickstart.

If the manual checker behaves unexpectedly, open the support widget and include the address domain, the result you saw, and what you expected instead.

Keep reading

More docs from the getting started section.