Wiki / Email

Warning: DMARC recordno DMARC record found

The domain does not tell mail servers what to do with messages that fake your address, so the recipient's mail system has no instruction to stop them. The first record takes 5 minutes and cannot break anything.

What it does not mean. It does not mean your mail is failing to arrive or that someone is already sending in your name. Gmail requires DMARC only from senders of more than 5,000 messages a day (since 1 February 2024); everyone else needs SPF or DKIM.

Aleksandr IzmalkovFacts checked:

In our report
Warning (yellow), category weight 0.8 of 2.0
Time to fix
5 minutes for the first record; a few weeks of reports before p=reject
Can it break things
Not with p=none. With quarantine and reject, yes

How to fix it

DMARC is a single TXT record at _dmarc.yourdomain.com. It works only when the domain already has SPF or DKIM. Tighten the policy in three steps, not in one go.

Step 1: watch only

_dmarc   TXT   "v=DMARC1; p=none; rua=mailto:[email protected]"

Nothing changes for your mail. Reports arrive at the rua address and show who sends mail in your domain's name.

Step 2: to spam

_dmarc   TXT   "v=DMARC1; p=quarantine; rua=mailto:[email protected]"

Once the reports show every real sender of yours passing the check: the mail server, the newsletter tool, website forms, invoicing software.

Step 3: reject

_dmarc   TXT   "v=DMARC1; p=reject; rua=mailto:[email protected]"

The final value. In the Cloudflare DNS panel: Type TXT, Name _dmarc, Content is the text inside the quotes.

How to check

dig +short TXT _dmarc.example.com

Expected

"v=DMARC1;p=reject;sp=reject;adkim=s;aspf=s"

An empty result means there is no record. There must be exactly one: when two v=DMARC1 records are found, both are discarded.

Terminal: dig shows the DMARC records of three domains with quarantine and reject policies
Real records on 18 November 2026: aguard.lt (quarantine), google.com and example.com (reject).

What can break

  • With p=reject your own messages are rejected too when they go through a system that does not sign DKIM with your domain: a newsletter tool, a CRM, online shop notifications. Gmail answers with error 550 5.7.26.
  • When a message is forwarded (from a company address to a personal Gmail, for example) SPF no longer matches. The message passes only if it carries a valid DKIM signature.
  • Without sp, subdomains get the same policy. If a separate system sends from shop. or mail., find it in the reports before tightening.
Gmail's reply to the sender: 550 5.7.26 Unauthenticated email is not accepted due to domain's DMARC policy
What the sender gets back when the domain policy is reject and the message fails the check. Text from Google's error reference.

Possible values

In May 2026 DMARC became an Internet standard (RFC 9989), replacing RFC 7489 from 2015. Existing records keep working, but several tags changed.

TagWhat it doesNote
p=noneTake no action, only send reportsFor the start; left for good, it does not protect against forgery
p=quarantineTreat failing messages as suspiciousThey usually land in spam
p=rejectReject failing messagesThe strongest protection
sp=A separate policy for existing subdomainsWithout it, p applies to subdomains
np=Policy for subdomains that do not existNew in RFC 9989
rua=Where aggregate reports are sentWithout it you cannot see who sends in your name
t=yTest modeNew in RFC 9989; replaces pct
pct=Apply the policy to a share of messagesRemoved in RFC 9989: do not rely on it in a new record

Our data

68.5%

of 64,910 inspected .lt domains (44,466) have no DMARC record. Another 25.3% have only p=none, which stops nothing. 6.2% tell receivers to quarantine or reject forged mail. Dataset, 16 November 2026

Sources

Next