Deliverability

Know the state of the sending setup.

MAILTIG checks DNS records you publish. A passing check is not an inbox-placement guarantee.

Read the setup guide

Interactive product tour. Does not send messages.

Product tour

DNS diagnostic

Problem, diagnosis, correction. A pass is not inbox placement.

Three authored scenarios

Diagnose a sending domain

Pick a DNS state for send.oakline-realty.example and read what MAILTIG would tell you. No lookups run from this origin.

Product tour

Unknown here: This website does not look up your domain.
Authored test: Each tab is a prepared SPF, DKIM and DMARC state.
Not delivered: Present records authenticate mail. They do not prove inbox placement.

send.oakline-realty.exampleCampaigns blocked

DNS records for the authored domain in this tour
Record	Host	Status
SPFTXT	@	Missing
DKIMTXT	selector1._domainkey	Found
DMARCTXT	_dmarc	Found

SPF value

(no TXT record found)

Receivers cannot confirm which servers may send for this domain.

DKIM value

v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…

Public key for the selector MAILTIG signs with. The key shown is truncated, not a live key.

DMARC value

v=DMARC1; p=none;

Monitoring policy. p=none asks receivers to report, not to reject; tighten only after reports look clean.

Problem

Campaigns cannot start: SPF is not published

Diagnosis

SPF is a required check in MAILTIG's pre-flight. Without it, many receivers treat mail as unauthenticated even when DKIM passes, and DMARC alignment can only rely on DKIM.

Correction

Publish one TXT record at the domain root with your provider's include mechanism and a ~all qualifier, then run the domain check again. A domain may have only one SPF record; merge includes if one already exists.

Why it matters: Authentication failures are the most common reason a technically sound campaign is throttled on day one.

Provider documentation

DNS configuration does not prove inbox placement. It proves that receivers can authenticate your mail.

Read this demo as text

SPF missing: Campaigns cannot start: SPF is not published

SPF (TXT at @): Missing. Receivers cannot confirm which servers may send for this domain.
DKIM (TXT at selector1._domainkey): Found. Value: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…
DMARC (TXT at _dmarc): Found. Value: v=DMARC1; p=none;

SPF is a required check in MAILTIG's pre-flight. Without it, many receivers treat mail as unauthenticated even when DKIM passes, and DMARC alignment can only rely on DKIM.

Next step: Publish one TXT record at the domain root with your provider's include mechanism and a ~all qualifier, then run the domain check again. A domain may have only one SPF record; merge includes if one already exists.

DKIM pass, DMARC missing: Sending allowed, but you are flying without reports

SPF (TXT at @): Found. Value: v=spf1 include:_spf.google.com ~all
DKIM (TXT at selector1._domainkey): Found. Value: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…
DMARC (TXT at _dmarc): Missing. Receivers have no policy to apply and nowhere to send aggregate reports.

SPF and DKIM pass, so MAILTIG lets campaigns run. Without DMARC you receive no aggregate reports, so spoofing or alignment problems stay invisible, and major mailbox providers increasingly expect a DMARC record from bulk senders.

Next step: Publish _dmarc with p=none and a rua= mailbox you monitor. Review reports for two to four weeks before moving to p=quarantine.

All records present: Authentication is in place; now protect reputation

SPF (TXT at @): Found. Value: v=spf1 include:_spf.google.com ~all
DKIM (TXT at selector1._domainkey): Found. Value: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…
DMARC (TXT at _dmarc): Found. Value: v=DMARC1; p=none;

All three records resolve and align. MAILTIG marks the domain verified and campaigns can be started. This proves authentication, not placement: reputation, content and recipient engagement decide where mail lands.

Next step: Keep daily volume inside each mailbox's limit, warm up new senders gradually, verify contacts before the first send, and watch bounce and complaint rates on the Deliverability page.

DNS configuration does not prove inbox placement. It proves that receivers can authenticate your mail.

DNS check

These checks are authored scenarios, not live lookups.

Next Related feature

DNS checks: Add a sending domain and MAILTIG generates the verification, SPF, DKIM and DMARC records to publish, then checks them by DNS lookup on demand and hourly until they pass.
DKIM signing: SMTP sends are DKIM-signed with the sending domain's key once its DNS record passes; Gmail, Microsoft 365 and ESP sends are signed by the provider.
Own-mailbox warm-up: Warm-up exchanges messages between your own connected mailboxes on a ramp, with automatic pause when recent failures exceed 5%. It needs at least two connected mailboxes.
Mailbox limits: Each mailbox has its own daily send limit: 50 by default for personal mailboxes and 10,000 for high-volume providers, adjustable per mailbox.
Bounce pause: After 20 sent emails, a bounce rate of 5% or more pauses the campaign automatically with an explanation.

Provider restrictions

Gmail, Microsoft, SendGrid, Mailgun and Amazon SES keep their own authentication and sending rules. MAILTIG does not run a public domain lookup from this website. Why delivery is not inbox placement.

Guides

Operating notes for this page.

Create a workspace. Prices are on the page.

Start on the Free plan. Credits never expire. There is no overage. Exact numbers are on Pricing.

Create workspace Ask a question

Know the state of the sending setup.

DNS diagnostic

Diagnose a sending domain

Campaigns cannot start: SPF is not published

SPF missing: Campaigns cannot start: SPF is not published

DKIM pass, DMARC missing: Sending allowed, but you are flying without reports

All records present: Authentication is in place; now protect reputation

DNS check

Operating notes for this page.

Gmail bulk sender requirements for outbound email

Own-mailbox warm-up versus a shared warming network

Email warm-up, explained without folklore

SPF, DKIM and DMARC for an outreach workspace

Why delivery does not equal inbox placement

Create a workspace. Prices are on the page.

Diagnose a sending domain

Campaigns cannot start: SPF is not published

SPF missing: Campaigns cannot start: SPF is not published

DKIM pass, DMARC missing: Sending allowed, but you are flying without reports

All records present: Authentication is in place; now protect reputation