Product tour

See the workflow before you create a workspace.

These tours run in the browser. They do not send email or open a tenant inbox.

Nothing is sent from this page

The names and threads here are authored so you can click through a campaign, a DNS check, an inbox and a cost scenario without creating a workspace.

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

Tours

Every walkthrough is also listed as text.

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