~/blog/four-records-and-what-they-cannot-fixPOSTED
by Shady Nathan Tawfik · November 16, 2026 · 4 min

Four DNS Records and the Things They Cannot Fix

SPF hardfail, DMARC reject, TLS reporting and CAA close the cheapest half of phishing in four DNS edits. They do not stop a mail from the real mailbox and they do not stop a display name. Knowing which half you closed is the difference between protection and the feeling of it.

Interactive[blog-2.0]

TL;DR: SPF hardfail, DMARC reject, TLS reporting and CAA are four lines of DNS that close the cheapest half of phishing. They do not stop a mail sent from the real domain, and they do not stop a display name. Knowing which half you closed is the difference between protection and the feeling of it.

The scenario

I changed four records on a domain I control, then sent mail through the normal path to see what the receiver would say. The whole change took ten minutes and cost nothing.

The interesting part was not what improved. It was drawing the line afterwards: which attacks are now impossible, and which are exactly as easy as before.

The four records

~/code/text text
spf      "v=spf1 include:provider-a include:provider-b -all"
dmarc    "v=DMARC1; p=reject; sp=reject; adkim=r; aspf=r;
          fo=1; rua=mailto:dmarc@example.tld; pct=100"
tls-rpt  _smtp._tls "v=TLSRPTv1; rua=mailto:dmarc@example.tld"
caa      0 iodef "mailto:dmarc@example.tld"

Each one answers a different question:

  • SPF -all — may this envelope domain send? A hard fail refuses instead of marking.
  • DMARC p=reject — may this visible domain send, and what happens if it cannot prove it? Reject removes the message instead of filing it.
  • TLS-RPT — did the transport use TLS, and did it fail anywhere? Reporting only, but it makes silent downgrades visible.
  • CAA — which certificate authorities may issue for this domain? It limits mis-issuance and records who to notify.

Prove it before you celebrate

The only useful proof is a real message through the real path after the change:

~/code/text text
labels: INBOX, CATEGORY_UPDATES
dkim=pass header.i=@example.tld header.s=esp
spf=pass  ... @send.example.tld ...
dmarc=pass (p=REJECT sp=REJECT dis=NONE)

The receiver confirms the new policy and still delivers. That single line — p=REJECT in the authentication result — is the difference between "we published a policy" and "the other side is enforcing it".

TL;DR: SPF hardfail, DMARC reject, TLS reporting and CAA are four lines of DNS that close the cheapest half of phishing. They do not stop a mail sent from the real domain, and they do not stop a display name. Knowing which half you closed is the difference between protection and the feeling of it.

What the four records close

AttackBeforeAfter
forged sender, direct to the MX550550 (unchanged)
forged sender through a rented relaydelivered to spamrejected at SMTP
envelope spoofingmarked as softfailrefused
certificate mis-issuanceunconstrainedlimited by CAA
silent TLS downgradeinvisiblereported

The relay case is the one that actually changed. Direct spoofing from an arbitrary IP was already refused by the large receivers before DMARC was even evaluated — PTR and authorization checks come first.

What they cannot fix

AttackWhy DNS cannot help
mail from the real mailboxthe message is genuinely signed
brand in the display nameno record covers free text
lookalike domainit belongs to someone else
a user who clicksnot a name-resolution problem
a compromised ESP keyit produces valid signatures

That second row is the one people underestimate. DMARC checks the domain, not the name in front of it. A correctly authenticated domain can wear any display name it likes.

Findings

LayerStatus after the change
forgery from outsideclosed
driftmonitored (reports + posture check)
impersonation with your nameopen
impersonation with your mailboxopen
transport visibilityimproved, not enforced

The chain

SPF -allForged envelope refusedDMARC rejectForged domain removedCAACertificate limitedTLS-RPTDowngrade visibleCheap forgery closedReal mailbox still openDisplay name still open

The parts that need more than DNS

Four items always come up in the same conversation, and none of them is a DNS record:

  • DNSSEC needs a registrar that can publish a DS record. If the registrar cannot, the zone stays unsigned no matter what the DNS provider supports.
  • MTA-STS needs a policy file on a subdomain, which means a host — a web server or a small worker.
  • BIMI needs a verified mark certificate, which is a commercial process.
  • Two-factor enforcement needs a click in an admin console. It is also the only control that touches the mailbox-takeover path.

Closing

Four records, ten minutes, zero cost — and a measurable improvement in one specific class of attack.

That is worth doing. It is not worth confusing with "we are protected". The honest scorecard has two open rows, and both of them live where DNS cannot reach: in the login and in the name.

Once an attacker gains access, they can perform the following actions:

Removes the cheapest forgery path entirely: no message, no spam folder, no click.
Makes policy changes measurable - reports show whether a legitimate sender broke.
Creates a false sense of completeness: teams stop here and never touch the mailbox and the display name.
Leaves the two attacks that actually work - real mailbox, real name - untouched.
Shady Nathan Tawfik

Founder & Cyber IT Security Engineer in Bielefeld. Offensive security, audits and full-stack builds. More at

For educational purposes only. Every reproducible command targets my own lab environment (localhost), never a live system. © 2026