Email operations

Operational Guide to Email Verification

Email verification is more than syntax checks. Operationally, you're confirming the sending domain is configured correctly, the IP isn't blacklisted, and the address is reachable — without burning your sender reputation.

Quick summary

  • Verify SPF, DKIM, and DMARC every time DNS changes.
  • Check sending IP reputation before launching campaigns.
  • Save the chain as a workflow — bounces are recurring.
  • Monitor the sending domain, not just the mailbox.

What 'verified' actually means for email

  • MX records resolve to a reachable mail host.
  • SPF authorises the sending IPs you actually use.
  • DKIM selectors are published and signing successfully.
  • DMARC alignment matches and the policy is intentional.
  • Reputation — sending IP isn't on Spamhaus, Barracuda, or similar.
  • TLS on the receiving host is valid and current.

When verification breaks deliverability

Most deliverability incidents start with a silent change: DNS edit, IP rotation, vendor swap. Running this workflow on a schedule catches drift before bounces start.

Troubleshooting workflow

Run through these steps in order. Each step links to the right diagnostic tool.

  1. 1

    Check MX and authentication

    MX, SPF, DKIM, DMARC in one DNS pass.

    Open DNS Lookup
  2. 2

    Sweep blacklists

    Both the sending IP and the domain.

    Open Blacklist Check
  3. 3

    Verify the receiving TLS

    STARTTLS support is increasingly required.

    Open SSL Checker
  4. 4

    Save the workflow

    Resume it after every DNS change or campaign launch.

    Open Open dashboard

Frequently asked questions

What does operational email verification cover?

MX resolution, SPF / DKIM / DMARC alignment, sender IP reputation, blacklist status, and TLS on the receiving mail host. Anything that affects whether legitimate mail lands in the inbox.

How is this different from address validation?

Address validation checks if a mailbox accepts mail. Operational verification checks if your sending infrastructure is configured correctly and trusted by receivers.

How often should I re-verify sending domains?

Weekly at minimum, daily for revenue-critical mail streams. SPF drift and silent DNS changes are the usual culprits behind sudden deliverability drops.

Can verification damage sender reputation?

Mailbox-level SMTP probes can. Infrastructure verification — DNS, SSL, blacklist — never touches recipient mailboxes and is safe at any cadence.

Monitor it continuously

Save this check, get alerts on changes, and track multiple domains in one dashboard.

Learn about monitoring