Skip to content

// transactional email

Via API

Amazon SES email verification with pingutil

Amazon SES tracks your account's bounce rate, and hard bounces land on the account-level suppression list, where later sends are accepted but not delivered. Checking addresses with pingutil before SendEmail keeps bad addresses out of that loop, and SES bounce notifications tell your app which users need a new address.

Where it connects: Your code before SendEmail (SES API v2), plus SES bounce notifications and the account-level suppression list

What goes wrong without it

  • We got an SES review notice for our bounce rate and most of the bounces were fake signups.
  • Once an address is on the account suppression list, SES accepts the message but never sends it, and our app thinks the reset email went out.
  • Bots fill our signup form with throwaway addresses and every confirmation email counts toward our daily sending quota.

What you can do with Amazon SES and pingutil

  • Verify before the first SendEmail call

    Call /v1/verify in the signup path or in the worker that sends the confirmation. Skip SendEmail for invalid addresses so they never reach the suppression list or your bounce rate.

  • Keep disposable signups off your quota

    Disposable domains come back invalid with reason disposable_domain, before SES counts the send against your daily quota.

  • Reconcile bounce notifications with your users table

    Subscribe an SNS topic to bounce notifications, mark the matching user as bouncing, and verify the replacement address with pingutil before you remove the old one from the suppression list.

Set it up

  1. 1

    Store PINGUTIL_KEY alongside your AWS credentials (for example in Secrets Manager).

  2. 2

    In the code that sends the first email to a new address, call POST /v1/verify and skip the send on status invalid.

  3. 3

    Send everything else with the SES API v2 SendEmail operation.

  4. 4

    Make sure the account-level suppression list is enabled for bounces, and set up bounce notifications through SNS or an event destination.

  5. 5

    When a user updates a bouncing address, verify the new one with pingutil, then send to it.

boto3 (SES API v2): verify, then send
import os
import boto3
import requests

ses = boto3.client("sesv2")


def verify(email: str):
    try:
        r = requests.post(
            "https://pingutil.com/v1/verify",
            headers={"Authorization": "Bearer " + os.environ["PINGUTIL_KEY"]},
            json={"email": email},
            timeout=10,
        )
        return r.json() if r.ok else None  # 429 quota_exceeded / 5xx: fail open
    except requests.RequestException:
        return None


def send_confirmation(email: str, link: str) -> bool:
    v = verify(email)
    if v and v["status"] == "invalid":
        # Never reaches SES, so it can't bounce or land on the suppression list
        return False

    ses.send_email(
        FromEmailAddress="hello@yourapp.com",
        Destination={"ToAddresses": [email]},
        Content={
            "Simple": {
                "Subject": {"Data": "Confirm your email"},
                "Body": {"Text": {"Data": "Confirm here: " + link}},
            }
        },
    )
    return True

What to do with each result

pingutil resultAction in Amazon SES
status invalid (mailbox_not_found, no_domain, no_mx)Skip SendEmail and ask for another address. Nothing reaches your bounce rate.
status invalid, reason disposable_domainRefuse the signup before any send counts against your SES quota.
status risky, reason accept_allSend. If it bounces, SES adds it to the account-level suppression list.
status unknownSend, and rely on bounce notifications to flag the user.

Limits to plan for

  • SES now has its own Email Validation feature: an API you call on demand and Auto Validation, which filters outbound mail by a delivery-likelihood threshold. pingutil is an alternative when you want verification plus disposable and work-email classification at the point of capture, or one verifier across several senders.
  • Per the SES docs, only hard bounces are added to the account-level suppression list, and sends to suppressed addresses still count toward your daily sending quota.
  • In the SES sandbox you can only send to verified identities, so test the pingutil check with addresses you control until you have production access.

Amazon SES documentation

Amazon SES is a trademark of its owner. This integration uses Amazon SES's documented extension points; it is not an official Amazon SES app.

Common questions

Do I still need the SES suppression list if I verify with pingutil?
Yes. Verification happens once, when the address is captured. Mailboxes close later, and the suppression list is what stops repeat bounces after that.
Can I verify addresses in a Lambda before sending?
Yes. Call pingutil over HTTPS from the Lambda and give the request a timeout shorter than the function's own, then send with SES as usual.
Is "verified" in SES the same thing?
No. SES identity verification proves you own a From address or domain. pingutil checks whether a recipient address can receive mail.

Stop bad addresses in Amazon SES today

Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your Amazon SES setup will receive.