How does SPF work?
SPF checks the envelope sender, not the From: address a person sees. That is why SPF on its own does not stop spoofing of the visible sender: DMARC adds the rule that the SPF-checked domain must align with the From: domain.
A record starts with v=spf1, lists mechanisms such as include:, ip4: or mx, and ends with an all qualifier: ~all (softfail) or -all (fail). A name may hold only one SPF record, and evaluation may perform at most ten DNS lookups; past that the result is a permanent error.
Bounces are sent to the envelope sender, so the domain used there needs an MX record that can accept them. Using a dedicated subdomain for it, such as bounce.example.com, keeps SPF for your sending service separate from whatever SPF already protects the root domain.
bounce.example.com. TXT "v=spf1 include:<value from your sender> ~all" How does nofeb use SPF?
- When you add a domain, nofeb uses a custom MAIL FROM subdomain (
bounce.) and returns its MX and SPF records, so SPF passes and aligns with your From: domain for DMARC without touching the SPF record on the root domain. - nofeb's own MX checks SPF on every message it receives and stores the result in the message's security verdict.
Frequently asked questions
Can a domain have two SPF records?
No. Two v=spf1 records at one name make SPF fail with a permanent error. Merge the mechanisms into one record. When nofeb publishes records through a DNS host's API and finds a second SPF record at the same name, it skips it and tells you instead of creating the conflict.
Should I use ~all or -all?
~all (softfail) asks receivers to treat unlisted senders as suspicious; -all asks them to reject. With DMARC in place, most senders publish ~all and let the DMARC policy decide.
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 |