Your DMARC policy is at p=reject, and suddenly messages to a mailing list or a forwarded address bounce. The list added a subject tag, the forwarder sent from its own IP address, and SPF and DKIM no longer pass at the final receiver. ARC (Authenticated Received Chain) exists for exactly this situation — but it only helps when the pieces around it are in place.
The ARC Checker looks at a domain from the outside: its DMARC policy, DKIM keys at common selector names, the mail provider behind its MX records, and what that provider documents about ARC. It tells you how ready the domain is, and what DNS cannot show.
What is ARC?
In simple terms
When a message passes through a mailing list, a forwarding service or a security gateway, that intermediary can record what it saw — "SPF and DKIM passed when I received this" — and sign that record. A later receiver that trusts the intermediary can use the recorded results even if the message no longer passes SPF or DKIM on arrival.
Technical background
ARC is defined in RFC 8617. Each intermediary adds an ARC set of three header fields: ARC-Authentication-Results (the results it observed), ARC-Message-Signature (a DKIM-like signature over the message at that point) and ARC-Seal (a signature over all ARC sets so far, with a cv= value saying whether the earlier chain was valid). There is no ARC DNS record: the sealer signs with its own domain and publishes its key like a DKIM key.
Why use an ARC readiness check?
ARC matters most for domains that enforce DMARC, because enforcement is what turns broken forwarding into rejected mail. The check shows whether your DMARC policy and DKIM keys give forwarded mail a fair chance, and whether your provider can seal and evaluate ARC at all — before users report bounced list mail.
Who should use it?
Email administrators moving DMARC towards p=reject, postmasters of organisations with many mailing lists or forwarding rules, MSPs reviewing customer domains, and anyone placing a security gateway in front of Microsoft 365 or Google Workspace.
How the ARC Checker works
NetTools queries public DNS: the MX records and SPF includes of the domain, its DMARC record (and the parent domain's, when the name has none), the authorisation records for external report addresses, and DKIM keys at a fixed list of common selectors. MX hosts and SPF includes are matched against a registry of mail providers whose ARC capabilities are taken from vendor documentation, each with a source and verification date. For the policy itself, the DMARC Checker and DKIM Checker go into more detail.
How to use the NetTools.tech ARC Checker
- Open the ARC Checker and enter the domain from your From: address.
- Optionally choose your mail provider if it is not detected automatically.
- Click Check ARC.
- Read the readiness summary and the recommendations, then the five sections: domain, DMARC, DKIM, provider capabilities and forwarding.
- Export the report as PDF, CSV or JSON, copy it as text, or print it.
Understanding the results
The overall status is Ready, Partially ready, Needs attention or Unknown — there is no score. Every check shows its status (PASS, WARNING, FAIL or UNKNOWN), the observed value, an explanation, why it matters and what to do. Each check is labelled as a DNS observation, provider information or an assessment, so documented capabilities are never mistaken for your configuration. A DKIM key found at a selector shows that the key exists — not that your mail is signed with it.
Example: Proofpoint in front of Microsoft 365
A domain's MX records point to Proofpoint and its SPF record includes Microsoft 365. The checker detects Proofpoint as the inbound gateway and Microsoft 365 as a sender, notes that Proofpoint's ARC sealing is configuration-dependent, and recommends adding Proofpoint as a trusted ARC sealer in Microsoft 365 after confirming the sealing domain from a received message. The result is "Partially ready" until those settings are confirmed.
Common use cases
- Preparing a move from p=none to p=quarantine or p=reject.
- Explaining why mailing-list or forwarded mail fails DMARC.
- Reviewing a domain behind a security gateway.
- Checking that DKIM keys exist before relying on forwarding.
Troubleshooting
DMARC record not found
Publish a TXT record at _dmarc.yourdomain with at least v=DMARC1 and p=none, plus a rua= report address, then work towards enforcement.
No DKIM keys at common selectors
Look up the s= value in a DKIM-Signature header of a message you sent and check it in the DKIM Checker.
Provider not identified
The MX hosts are not in the registry. Select your provider manually; the result marks it as your selection rather than DNS evidence.
Results marked Unknown
A DNS lookup timed out or returned SERVFAIL. Run the check again in a few minutes.
Common mistakes
- Publishing a TXT record called "ARC" — there is no such record.
- Treating a DKIM key in DNS as proof that mail is signed.
- Enforcing DMARC without checking list and forwarding traffic in the reports.
- Assuming ARC is active because the provider supports it.
- Forgetting to trust the gateway's ARC seal in the mailbox provider.
Limitations
The checker sees DNS only. It cannot see tenant settings, trusted-sealer lists or whether messages are actually signed and sealed. DKIM discovery is limited to common selector names. Provider capability information comes from public documentation and may change; each entry shows when it was last verified. For a real message, use the ARC Chain Analyzer.
Security & privacy
Only DNS lookups are made, through public resolvers, with a fixed selector list and rate limits. Results are cached in memory for five minutes and the domain is not stored.
Related tools
- ARC Chain Analyzer — validate the ARC headers of a real message.
- DMARC Checker — inspect a DMARC record in detail.
- DKIM Checker — check a key at any selector.
- SPF Checker — validate SPF and its lookups.
- Email Deliverability Checker — the full picture for a sending domain.
Summary
ARC helps forwarded mail survive DMARC enforcement, but it depends on intermediaries sealing and receivers trusting them. The NetTools.tech ARC Checker shows what your domain contributes — DMARC and DKIM — and what your provider documents, clearly separated from what DNS cannot prove.
Frequently asked questions
Do I need to publish an ARC DNS record?
No. ARC has no DNS record type of its own. Intermediaries sign ARC sets with their own domain and keys. Your domain needs a working DMARC policy and DKIM signatures, not an ARC record.
Does the ARC Checker show whether ARC is enabled for my organisation?
No. DNS cannot show tenant settings. The checker shows what DNS reveals and what each provider documents. To see ARC in action, look for ARC-Seal headers in received mail or use the ARC Chain Analyzer.
Why is my domain only “partially ready”?
Usually because DMARC is still p=none, no DKIM key was found at the common selector names, or the provider’s ARC support depends on configuration. The summary lists the reasons.
Why were no DKIM keys found although I use DKIM?
The checker only tries a short list of common selector names. Your provider may use another one. Find the s= value in the DKIM-Signature header of a message you sent and check it with the DKIM Checker.
Does ARC fix DMARC failures for forwarded mail?
Only when the receiving provider trusts the intermediary that sealed the message. ARC preserves earlier authentication results; it does not change DMARC or guarantee delivery.
What is the difference to the ARC Chain Analyzer?
The ARC Checker assesses a domain from DNS. The ARC Chain Analyzer validates the ARC headers of an actual message.