Policies

Data quality guarantee

When an email address that Tomba returned hard-bounces, you can claim a credit refund. This page defines which Email Finder and Email Verifier results qualify and how to claim. It doesn't change the Terms of Service, under which Tomba doesn't warrant that any address is deliverable. If you have a signed agreement with Tomba, its terms take precedence over this page.

Email finder

Covers addresses returned by the email finder, domain search, author finder, and LinkedIn finder, through the API or another Tomba tool.

An address qualifies when it meets the conditions for both products and:

Its score was 60 or higher when Tomba returned it.

Email verifier

Covers addresses that the email verifier returned with the result deliverable (see Result values), through the API, bulk verification, or the Chrome extension.

An address qualifies when it meets the conditions for both products and you sent to it within 30 days of its verification.

Conditions for both products

The message hard-bounced because the address doesn't exist: the receiving server rejected it permanently.
You sent it from a domain authenticated with SPF, DKIM, and DMARC.
You sent it in compliance with the anti-spam policy.

These are not covered:

Soft bounces and other temporary failures, such as a full mailbox or an unavailable server.
Delivery to a spam or junk folder.
Messages that the recipient's server or filters block or throttle, including rejections based on the message's content or the sender's reputation.

How to claim

Report each address that hard-bounced. Use POST /v1/flag with flag_type email and reason hard_bounce, the tomba flag create command, or the report option on the result in the dashboard. Put the bounce message that your mail server received in comment.
Tomba reviews the report and confirms or rejects it. It can ask for the delivery log, the send date, and your domain's SPF, DKIM, and DMARC records to check the conditions above. Follow the report's status with GET /v1/flag, tomba flag list, or the Flags page of the dashboard.
For each confirmed report, Tomba refunds a credit as described in Refunds for incorrect data.

Last modified on October 4, 2026

Security Anti-spam policy

Conditions for both products

The message hard-bounced because the address doesn't exist: the receiving server rejected it permanently.

You sent it from a domain authenticated with SPF, DKIM, and DMARC.

You sent it in compliance with the anti-spam policy.

These are not covered:

Soft bounces and other temporary failures, such as a full mailbox or an unavailable server.

Delivery to a spam or junk folder.

Messages that the recipient's server or filters block or throttle, including rejections based on the message's content or the sender's reputation.

How to claim

Report each address that hard-bounced. Use POST /v1/flag with flag_type email and reason hard_bounce, the tomba flag create command, or the report option on the result in the dashboard. Put the bounce message that your mail server received in comment.

Tomba reviews the report and confirms or rejects it. It can ask for the delivery log, the send date, and your domain's SPF, DKIM, and DMARC records to check the conditions above. Follow the report's status with GET /v1/flag, tomba flag list, or the Flags page of the dashboard.

For each confirmed report, Tomba refunds a credit as described in Refunds for incorrect data.

curl -X POST "https://api.tomba.io/v1/flag" \
  -H "X-Tomba-Key: $TOMBA_API_KEY" \
  -H "X-Tomba-Secret: $TOMBA_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{"flag_type": "email", "value": "jane.doe@stripe.com", "reason": "hard_bounce", "comment": "550 5.1.1 The email account that you tried to reach does not exist."}'

Last modified on October 4, 2026