Skip to content
AdminKit

Email authentication

What does the Email authentication cluster cover?

AdminKit groups this topic into the Email authentication cluster: SPF, DKIM and DMARC are the three DNS-published records that tell receiving mail servers whether a message from your domain can be trusted — get one wrong and mail lands in spam or gets rejected outright.

Tools (18)

All tools →

Guides (31)

All guides →

Glossary (37)

Full glossary →
  • ARC (Authenticated Received Chain) — ARC (Authenticated Received Chain) lets each server in an email forwarding chain sign a record of what a message's SPF, DKIM and DMARC results looked like before that hop forwarded it onward. AdminKit's guide explains how ARC preserves authentication results across a forwarding chain that would otherwise fail SPF.
  • ARF (Abuse Reporting Format) — ARF (Abuse Reporting Format), defined in RFC 5965, is a machine-readable email format mailbox providers use to report one specific message back to its sender, most often a spam complaint. It's the format behind classic ISP feedback-loop programs and DMARC's optional ruf reports. AdminKit's guide to blacklisting explains how this per-message signal compares to reputation-based blacklisting.
  • Authentication-Results header — The Authentication-Results header (RFC 8601) records the SPF, DKIM, and DMARC verdicts a receiving mail server already computed, so downstream systems can read what was verified instead of repeating the checks. AdminKit's guide to SPF, DKIM, and DMARC explains the three checks this header reports the results of.
  • Backscatter (email) — Backscatter is the bounce traffic a mail server generates when it accepts a message and only later finds it can't be delivered, sending the bounce to whatever forged address the message claimed as sender -- landing in an innocent party's inbox. AdminKit's guide to email bounces covers spotting it.
  • Backup MX — A backup MX is a mail server listed in a domain's MX records with a higher preference number than the primary, so senders try it only when the lower-numbered hosts cannot be reached. AdminKit's MX lookup lists a domain's MX hosts in priority order and checks whether up to 5 of them resolve.
  • BIMI — BIMI (Brand Indicators for Message Identification) is a DNS TXT record that lets a domain show its verified logo next to its messages in supporting inboxes like Gmail, but only once DMARC is enforced at p=quarantine or p=reject. AdminKit's SPF, DKIM and DMARC guide covers that DMARC prerequisite before a domain adds BIMI.
  • Catch-all address — A catch-all address is a mail server setting that delivers messages sent to any address at a domain -- even ones never created -- to one inbox instead of bouncing them, which also makes the domain an easy target for spammers harvesting addresses. AdminKit's guide to bounces and backscatter explains how to avoid that cost.
  • DANE/TLSA — DANE (DNS-Based Authentication of Named Entities) uses a DNSSEC-signed TLSA record to publish exactly which TLS certificate a server should present, so a client can detect a forged or substituted one. AdminKit's STARTTLS guide covers how DANE and MTA-STS protect the TLS a mail server actually enforces.
  • DKIM — DKIM lets a sending domain cryptographically sign outgoing email with a private key, adding a header a receiver verifies against a public key published in DNS, confirming the message wasn't altered after signing. AdminKit's DKIM check tool checks a domain's DKIM record for the signing errors RFC 6376 compliance depends on.
  • DKIM selector — A DKIM selector is a short label in a message's DKIM-Signature header that tells a receiving server exactly which DNS TXT record holds the public key needed to verify it, letting one domain publish several keys at once. AdminKit's guide to DKIM selector mistakes covers the failures its DKIM check tool most often surfaces.
  • DMARC — DMARC is a DNS TXT record that tells receiving mail servers what to do when a message fails SPF and DKIM -- monitor, quarantine or reject -- and reports results back to the domain owner. AdminKit's DMARC check tool shows a domain's current policy and whether its alignment is set up correctly.
  • DMARC aggregate report (RUA) — A DMARC aggregate report (RUA) is the periodic XML summary mail receivers send to the address a domain's DMARC record names in its rua tag, listing SPF and DKIM results for mail claiming that domain, broken down by sending source. AdminKit's guide to reading these reports covers the staged rollout decisions they're meant to inform.
  • DMARC Failure Report (RUF) — A DMARC failure report (RUF) is a per-message report a receiver may send to the address in a domain's DMARC ruf tag when a message fails authentication, often with header fields and sometimes content, defined in RFC 9991. AdminKit's DMARC check reads a domain's published record, including whether it requests failure reports and where they go.
  • DSN (Delivery Status Notification) — A DSN (Delivery Status Notification) is the standardized report a mail server sends when it can't deliver a message, defined by RFC 3461 and RFC 3464. Its status code and failing recipient are machine-readable, separate from the bounce text a person reads. AdminKit's bounce-and-backscatter guide explains how a forged sender turns DSNs into a backscatter flood.
  • Envelope sender vs header From — An email carries two separate addresses: the envelope sender, used only for routing and bounces (RFC 5321), and the header From address a mail client actually displays (RFC 5322). SPF checks only the envelope sender, which is why a message can pass SPF while showing a forged header From. AdminKit's backscatter guide explains why this gap matters.
  • Forward-confirmed reverse DNS — Forward-confirmed reverse DNS (FCrDNS) checks that a sending IP's PTR hostname resolves forward back to the same IP, a basic anti-spoofing signal receiving mail servers use before accepting mail. RFC 1912 flags a PTR/A mismatch as a common DNS error FCrDNS catches. AdminKit's reverse DNS and DNS lookup tools together let you run both halves of the check manually.
  • Greylisting — Greylisting is a spam-reduction technique where a mail server temporarily rejects an unfamiliar sender with an SMTP 4xx code, then accepts the message once it retries, relying on RFC 5321's retry requirement. Spam infrastructure of the era often never retried. AdminKit's MX lookup tool shows which mail server handles a domain's inbound mail so a greylisting setup can be reviewed.
  • List-Unsubscribe header — The List-Unsubscribe header is an email header that lets a sender publish a mailto or HTTPS link so a mail client can unsubscribe a recipient without them opening the message, with RFC 8058 adding a one-click POST option. AdminKit's blacklist check shows how to spot the listing that skipping it can cause.
  • Message-ID Header — The Message-ID header is the unique identifier, written as <id-left@id-right>, that RFC 5322 section 3.6.4 says every message should carry. The host that creates it must make it unique, and replies refer back to it. AdminKit's email header analyzer reads the raw header block a Message-ID sits in, next to the Received chain.
  • MTA-STS — MTA-STS lets a domain publish a policy, via a DNS record plus an HTTPS-hosted file, requiring that incoming mail be delivered only over TLS with a valid, matching certificate, closing a gap where an attacker could force an unencrypted downgrade unnoticed. AdminKit's guide explains how it fits alongside SPF, DKIM and DMARC.
  • Null MX record — A null MX record, standardized in RFC 7505, is a single MX record pointing to the root domain that tells senders a domain explicitly accepts no email at all, instead of leaving mail handling undefined. AdminKit's MX lookup tool reports a null MX explicitly, rather than as a missing or broken record.
  • Open relay — An open relay is a mail server that accepts and forwards email from any sender to any recipient without verifying the sender is authorized, which spammers scan for and abuse until the server's IP lands on a blacklist. AdminKit's blacklist check page shows how to confirm whether an IP is listed on major blocklists.
  • Parked domain — A parked domain is a registered domain that runs no real service: at most a placeholder web page, and no email. AdminKit's SPF check, DMARC check and MX lookup show whether it still publishes the records that stop spoofing: SPF -all, DMARC p=reject and a null MX.
  • Received Header — The Received header is the trace field every SMTP server prepends to a message it accepts, recording the host it came from, the host that took it, the protocol and a timestamp, as RFC 5321 section 4.4 requires. AdminKit's email header analyzer reads the Received chain from pasted headers and computes the delay at each hop.
  • Return-Path Header — The Return-Path header is the trace field the final delivering mail server adds to record a message's envelope sender, the address from the SMTP MAIL FROM command where bounces are sent, as RFC 5321 section 4.4 describes. AdminKit's email header analyzer reads pasted headers so you can compare Return-Path with the visible From address.
  • SASL authentication — SASL, defined in RFC 4422, is a pluggable authentication framework that protocols like SMTP, IMAP, and LDAP use instead of each defining their own login mechanism; SMTP AUTH (RFC 4954) is its mail-specific extension. AdminKit's STARTTLS checker confirms a mail server encrypts the connection SASL credentials are expected to travel over.
  • SMTP (Simple Mail Transfer Protocol) — SMTP (RFC 5321) is the store-and-forward protocol mail servers use to relay email from a sender's outgoing server to a recipient's incoming one, with no built-in encryption or sender authentication of its own. AdminKit's STARTTLS checker verifies whether a mail server enforces the encryption extension plain SMTP never included.
  • SMTP Enhanced Status Code — An SMTP enhanced status code, defined in RFC 3463, is a three-part class.subject.detail code such as 5.1.1 that a mail server adds to its 3-digit reply, telling software exactly why a message succeeded, was deferred, or failed. AdminKit's SMTP status code decoder explains both the reply code and the enhanced code in a pasted bounce line.
  • SMTP HELO/EHLO — EHLO, the extended form of SMTP's opening HELO greeting introduced by RFC 1869 and carried in RFC 5321, asks a mail server which extensions -- STARTTLS, AUTH, SIZE and others -- it supports. AdminKit's MX lookup tool finds the mail servers a diagnostic EHLO command would actually be sent to.
  • SMTP Pipelining — SMTP pipelining is the PIPELINING service extension from RFC 2920: a server that advertises it in its EHLO reply lets the client send a group of commands, such as MAIL FROM and several RCPT TO, without waiting for each reply, and answers them in order. AdminKit's SMTP status code decoder explains each reply code those commands return.
  • SMTP REQUIRETLS — SMTP REQUIRETLS, defined in RFC 8689, lets a sender demand encrypted delivery for one message all the way to its destination, refusing to send rather than silently falling back to plaintext like ordinary STARTTLS. AdminKit's STARTTLS guide covers the related MTA-STS mechanism, which sets the same no-downgrade policy domain-wide instead.
  • SPF — SPF (Sender Policy Framework) is a DNS TXT record that lists which mail servers are authorized to send email claiming to be from a domain, checked against the IP that actually delivered a message. AdminKit's SPF Check tool checks a domain's SPF record and its DNS lookup count directly.
  • SPF void lookup — A void lookup, defined in RFC 7208 section 4.6.4, is an SPF DNS query that returns an empty answer or NXDOMAIN; the RFC recommends capping these at two, separate from SPF's overall 10-lookup limit. AdminKit's SPF guide covers both limits, including the stale includes that typically trigger a void lookup.
  • SRS (Sender Rewriting Scheme) — SRS (Sender Rewriting Scheme) fixes SPF failures caused by email forwarding by rewriting the envelope sender address at the forwarding server to one on the forwarder's own domain, so the forwarder's own SPF record is checked instead. AdminKit's guide explains how SRS keeps forwarded mail passing SPF.
  • STARTTLS — STARTTLS is a command that upgrades an initially plain-text SMTP, IMAP or POP3 connection to an encrypted TLS connection, but only if both the sending and receiving server support and accept it. AdminKit's SSL Check tool checks a mail server's TLS and certificate configuration, including STARTTLS support.
  • TLS-RPT — TLS-RPT, defined in RFC 8460, is a DNS TXT record telling other mail servers where to send reports summarizing TLS delivery failures, including ones tied to a domain's MTA-STS policy. AdminKit's email authentication guide covers how TLS-RPT pairs with MTA-STS and DMARC reporting.
  • VERP (Variable Envelope Return Path) — VERP (Variable Envelope Return Path) encodes each mailing-list subscriber's own address into the envelope sender of the copy they're sent, so a later bounce is self-identifying instead of generic. AdminKit's guide to email bounces and backscatter explains how the envelope sender normally routes a failed delivery back to its source.

Frequently asked questions

Why does an email pass SPF but still land in spam?

SPF only checks whether the sending server's IP is authorized for the envelope-from domain — it says nothing about DKIM signing, DMARC alignment, sender reputation or message content, all of which mailbox providers weigh separately. A message can pass SPF cleanly and still be filtered on any of those other signals.

What does 'DMARC alignment' mean, and why can SPF and DKIM both pass but DMARC still fail?

DMARC (RFC 7489) requires the domain behind SPF's envelope-from or DKIM's signing domain to match the visible From: header domain — not just that SPF or DKIM passed for some domain. A forwarded or third-party-sent message can pass SPF for the forwarder's domain and DKIM for a different signing domain, so neither one is 'aligned' with the From: header DMARC actually checks.

Do I need SPF, DKIM and DMARC, or is one enough?

Each protects a different failure mode: SPF (RFC 7208) authorizes sending IPs, DKIM (RFC 6376) proves the message wasn't altered in transit, and DMARC (RFC 7489) ties the two together and tells receivers what to do when they disagree. Publishing only one still leaves the others' gap open — most deliverability problems AdminKit's SPF, DKIM and DMARC checkers catch involve a domain that configured one record correctly and left another missing or misaligned.