Skip to content
nofeb

What is ARC?

Also called Authenticated Received Chain

ARC (Authenticated Received Chain) lets each server that handles a message record the SPF, DKIM and DMARC results it saw and sign that record. When a forwarder or mailing list modifies a message and breaks the original authentication, the final receiver can trust the earlier results if it trusts the signers in the chain.

Checked against the engine on .

How does ARC work?

Each hop adds three headers: ARC-Authentication-Results (what it saw), ARC-Message-Signature (a DKIM-like signature over the message) and ARC-Seal (a signature over the chain so far). A receiver validates the chain and then decides how much weight to give the recorded results.

ARC matters for mailing lists, forwarding services and security gateways, which routinely change subjects, add footers or rewrite links. Without ARC, a message from a domain with p=reject that passed through such a hop would fail DMARC at the end and be refused.

How does nofeb use ARC?

  • nofeb's MX verifies ARC chains on inbound mail. A message that fails DMARC under a reject policy is refused unless its ARC chain passes, so legitimate forwarded mail still reaches the agent.
  • The ARC result is part of every message's security verdict, beside SPF, DKIM and DMARC, and an inbound.pre_deliver hook can act on it.
  • Sender reputation and list membership as typed metadata beside these results.

Frequently asked questions

Does ARC replace DMARC?

No. ARC carries authentication results across hops that would otherwise break them; DMARC is still the policy a receiver applies, with ARC as evidence.

Who should add ARC headers?

Any intermediary that modifies mail it forwards: mailing lists, forwarding services and gateways. A receiver only needs to validate the chain.

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
Inbound mail server that checks mail at the door nofeb's own MX receives mail for the shared domain and your custom domains, with STARTTLS. It checks every recipient before accepting any data, verifies SPF, DKIM, ARC and DMARC, and scans for spam and viruses before it answers. Mail that fails a DMARC reject policy, carries a virus or is clearly spam is refused during delivery instead of bounced later; likely spam and DMARC-quarantined mail is filed into Junk. Every message carries a security verdict with its authentication, spam, virus and TLS results. Shipped
HTTPS hooks in the pipeline Signed HTTPS callouts that change what happens: create or reject an inbox for an unknown recipient, accept, reject or quarantine a message before delivery, and allow, deny or hold a send, each with a timeout and a fail-open or fail-closed mode. Shipped
Sender trust on every message Each inbound message is labelled trusted, known, unknown or suspicious, with the reasons: its authentication results, your sender lists, look-alike domains, display-name spoofing, and whether the inbox has corresponded with the sender before. Shipped