How does DKIM work?
A DKIM-Signature header names the signing domain (d=) and the selector (s=). The receiver fetches s._domainkey.d from DNS and verifies the signature. A pass proves the signing domain vouched for this exact content; it says nothing about the visible From: unless DMARC alignment holds.
Many sending services publish keys through CNAME records that point at keys they rotate themselves, so the customer adds the CNAMEs once and rotation needs no DNS change. On hosts with a proxy, such as Cloudflare, those CNAMEs must not be proxied, or the lookup returns an address instead of the key.
Forwarding preserves DKIM as long as the forwarder does not modify the signed parts. Mailing lists that add footers or rewrite subjects break it, which is the problem ARC addresses.
token1._domainkey.example.com. CNAME <target from nofeb>
token2._domainkey.example.com. CNAME <target from nofeb>
token3._domainkey.example.com. CNAME <target from nofeb> How does nofeb use DKIM?
- Adding a domain returns three DKIM CNAMEs. Mail from your inboxes is DKIM-signed for your domain, and nofeb rotates the keys behind the CNAMEs.
- nofeb's live check flags a proxied Cloudflare CNAME by name, and when nofeb publishes through the Cloudflare API it always creates the CNAMEs unproxied.
- Inbound, nofeb's MX verifies DKIM signatures and records the result per message.
Frequently asked questions
Why does my DKIM record fail on Cloudflare?
Usually because the CNAME is proxied (orange cloud). A proxied CNAME is flattened to Cloudflare's addresses, so the receiver never finds the key. Set it to DNS only.
Does DKIM stop spoofing?
Not alone. DKIM proves which domain signed a message; DMARC requires that domain to match the visible From: domain and tells receivers what to do when it does not.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| Custom domains | Add a domain and nofeb returns its DKIM, custom MAIL FROM and DMARC records, plus an inbound MX if you want nofeb to receive its mail, checks them, and emits domain.verified when they pass. | Shipped |
| DNS setup made easy | nofeb detects who hosts your domain's DNS and gives you the shortest path for that host. It can publish the records through the Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun or Gandi API with a token used for that one call and never stored, and it never deletes a record. Every other host gets step-by-step instructions in its own terms, plus zone-file, Route 53 and Terraform exports. A live check shows each record's status, what was found and the likely mistake. Pointing your MX at nofeb is a separate choice, so publishing sending records never moves your mail. | Shipped |
| 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 |