Tools

Tools & operations

Reading the WillItInbox report, API integration, CI/CD workflows, and the operational craft of running mail.

How to use this topic

Start with the pillar guide for the full model, follow the diagnostic workflow for the current problem, and use the commercial destination when the evidence needs to become a repeatable team process.

Explore free email tools

Run bounded MX, SPF, DMARC, MTA-STS, and header diagnostics before moving into monitored product workflows.

Curated guide

Pick the diagnostic that matches the question

Use narrow public tools for one DNS, header, or policy question. Use the full deliverability tester when the problem spans authentication, content, routing, links, and sender reputation.

Turn one report into an operating workflow

A single report is useful; repeated checks become operational leverage when they are connected to release reviews, regression tests, webhooks, and team-visible evidence.

Automate what repeats

API, SDK, and webhook workflows are the right fit when validation, monitoring, and deliverability checks need to run inside product flows or release pipelines without manual copy-paste.

Diagnostic workflow

  1. Step 1

    Choose the smallest diagnostic

    Start with the free check that matches the current DNS, policy, or header question.

    Open workflow
  2. Step 2

    Run the complete workflow

    Use message testing, validation, monitoring, or placement when the job crosses multiple evidence layers.

    Open workflow
  3. Step 3

    Automate repeatable checks

    Use API, SDK, webhook, and CI patterns for release and operations workflows.

    Open workflow

Relevant free tools

Pillar guide

How to read a WillItInbox deliverability report

·3 min read

Prioritize authentication, routing, headers, content, links, and infrastructure findings without treating the score as a delivery guarantee.

Read pillar

Supporting guides

Frequently asked questions

When should a free check become a monitored workflow?
Move to monitoring when evidence must be retained, compared over time, shared with a team, or connected to alerts and remediation.
Can the API be used in CI/CD?
Yes. Use stable check identifiers, explicit thresholds, bounded polling or signed webhooks, and archive the report with the release.