Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist

Quick answer for cloudflare email dns

Inbound records do not replace outbound records. Outbound records do not move inbound mail.

Two SPF TXT at the same name fail. Cloudflare makes it easy to click add twice.

DKIM CNAME versus TXT: do what the dashboard says, once.

Routing’s MX and ours cannot share the zone “temporarily.”

Authoritative mail transport is still IETF RFC 5321 — Simple Mail Transfer Protocol. docs. tools. troubleshooting.

The real decision

People start at DMARC because it sounds advanced. They have leftover MX.

Decision: receiving only versus also sending.

Account access: who can add a second SPF.

A suite leftover checklist is the same leftover list.

When this path is enough

• You can staff exclusive MX and named aliases.
• You will keep Header From intact.
• You can probe from another mailbox.

When this is the wrong ticket

• History is empty and leftovers remain.
• You want an inbox placement SLA.
• You plan to rewrite visible From.

Technical mail flow

NS → TXT verify → aliases → MX exclusive → inbound probe → (paid) SPF/DKIM/DMARC → outbound probe.

Skip aliases and you HOLD or 550 the names you wanted.

Skip leftover delete and the checklist lies.

Self-send skips the list.

Step-by-step decision path

1. Inventory leftovers. Screenshot current MX, SPF, DKIM, NS.
2. Verify the domain. TXT as the dashboard states.
3. Create named aliases first. Do not cut MX onto empty maps.
4. Publish one MX set. Delete Google, Microsoft, registrar leftovers.
5. Prove from another mailbox. Unique subject. Header From intact.
6. Only then send-as if paid. Dashboard SPF/DKIM. Outbound probe.
7. Store the proof packet. MX, hop, headers, plan name.

Worked examples

Checklist printed. They still added a second SPF. Permerror. Deleted extra.

DKIM at apex. Fail. Moved to selector._domainkey.

Routing leftover after a trial. Split. Deleted.

DMARC p=reject with Google include leftover. Outbound pain. p=none until diet.

NS not Cloudflare. Checklist on the wrong panel. Fixed NS.

Failure modes and proof

MailerZ workflow and product boundary

Secuno LLC operates MailerZ. Site: mailerz.net. App: mail.mailerz.net. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not IMAP. Not an open relay.

What MailerZ does

• Accept MX for verified domains.
• Rewrite envelope MAIL FROM with SRS on the forward.
• Leave Header From and MIME intact.
• Hold unknowns on Free. Optional paid FORWARD.
• Paid SMTP from approved identities. Dashboard SPF, DKIM, and DMARC instructions.
• 550 for unauthorized From. Not an open relay.

What MailerZ does not do

• Guarantee Gmail Primary or any inbox placement rate.
• Host IMAP, webmail, or Calendar.
• Send-as on Free.
• SOC 2, ISO 27001, HIPAA, review counts, or an uptime SLA. Controls: Security and Trust Center.

Plans: pricing. Free $0, 1 domain, 3 aliases, 1 seat, 14-day store, send-as disabled, SMTP and API disabled. Solo $40/year, 3 domains, 15 aliases, 90-day, 1,000 outgoing, 5/hour. Starter $8 or $80, 5/50/5, 2,000, 10/hour. Business $19 or $190, 25/200/25, 4,000, 15/hour. Agency $39 or $390, 100/500/50, 8,000, 25/hour. Unlimited is $99/month or $990/year. Annual Starter, Business, and Agency include two months free versus monthly. Solo is yearly only.

Cost, alternatives, and trade-offs

Field notes

Related: /docs, /tools, /troubleshooting, /migration-planner.

Keep the checklist next to the ownership sheet.

Re-run after any teammate gets DNS.

Cloudflare blog posts go stale. Trust two resolvers.

Search demand for cloudflare email dns usually arrives as a screenshot, not a sentence. Ask for the received copy, the public MX set, and the plan name before you change a record. Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist is a workflow, not a checkbox.

Write a one-paragraph policy the team can reuse for cloudflare email dns. Name the hop (inbound versus outbound), the proof artifact, and the thing you will not do (dual MX, From rewrite, second SPF record). Put the paragraph in the ticket template.

Change control matters more than a clever record. One person owns DNS for this domain. Adding an include, a selector, or a backup MX requires a ticket. Most regressions in cloudflare email dns are Friday edits without a probe.

Self-send remains invalid for cloudflare email dns. Gmail can short-circuit. Outlook can look local. Use a mailbox on another provider and a unique subject. If the customer refuses, the ticket stays open.

Leftover MX masquerades as every authentication and spam incident. If history is empty, cloudflare email dns is the wrong title until two resolvers agree on one product. Delete aspmx, Microsoft, and registrar MX. Wait TTL.

Free HOLD and missing aliases masquerade as outages. History shows the hold. Create the named local-part or accept that unknowns stay. Catch-all FORWARD is paid, optional, and a spam trade-off — not a debugger for cloudflare email dns.

Paid send-as is a different hop from inbound cloudflare email dns. Free cannot send. Unauthorized From is 550 / 550 5.7.1. Publishing prettier DNS will not authorize a From the product has not approved.

Destination filters still win after a clean hop. Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist does not include an inbox placement SLA, review counts, or a Primary guarantee. Say that once, early, so the customer stops buying a story you cannot ship.

Proof packet for cloudflare email dns: public MX from two resolvers, inbound received copy with Header From, Authentication-Results, outbound received copy if they send, plan name, and the SMTP line if anything refused. That packet ends folklore.

Retention is 14 days on Free and 90 on paid. Export headers while they live. cloudflare email dns arguments without artifacts become myths. The destination inbox is the archive, not the hop store.

Agencies should not blend clients in one cloudflare email dns thread. One domain, one matrix, one MX screenshot. Agency plan limits are 100 domains, 500 aliases, 50 seats, 8,000 outgoing, 25/hour — still not unlimited, still not an SLA.

Security hygiene: no SMTP passwords in the cloudflare email dns ticket, no message bodies in chat, no invented SOC 2. Controls live on the Security and Trust Center. Secrets rotate if they leaked.

Related operations stay on real routes: forwarding, send-as, troubleshooting, tools, delivery recovery, docs, pricing. Do not invent a pillar. If cloudflare email dns is actually leftover MX, say leftover MX.

Refresh cadence is at least quarterly, sooner after a domain transfer, panel change, ESP trial, or dashboard host change. Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist goes stale when the zone changes and the runbook does not.

If two products still share MX after you explained the coin flip, stop adding records. Exclusive MX is a hard stop. cloudflare email dns cannot be correct on a split path.

If Header From is already rewritten, stop tuning SPF for cloudflare email dns. Change the hop. MailerZ will not offer a From-replace control. Honest identity is the product.

If the customer wants a suite, sell the suite as Calendar and a hosted mailbox, not as a magic fix for cloudflare email dns. Workspace and Microsoft 365 are different architectures with their own filters and their own 550s.

Hourly and monthly send-as ceilings (disabled/1,000/2,000/4,000/8,000 outgoing; 5/10/15/25 per hour by plan) produce refuses that look like cloudflare email dns outages. Read counters before you republish DKIM.

Null MX plus a real MX is another lie. Remove the lone-dot refuse if you intend to receive. Empty inbound plus a pretty cloudflare email dns essay is still a refuse-all.

After you change anything, wait TTL, probe from another mailbox, and store the new received source next to the MX screenshot. Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist is done when proof exists, not when the panel is green.

Field story 1 for cloudflare email dns: Checklist printed. They still added a second SPF. Permerror. Deleted extra. Keep that story in the runbook so the next person does not reopen Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist from zero.

Field story 2 for cloudflare email dns: DKIM at apex. Fail. Moved to selector._domainkey. Keep that story in the runbook so the next person does not reopen Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist from zero.

Field story 3 for cloudflare email dns: Routing leftover after a trial. Split. Deleted. Keep that story in the runbook so the next person does not reopen Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist from zero.

Field story 4 for cloudflare email dns: DMARC p=reject with Google include leftover. Outbound pain. p=none until diet. Keep that story in the runbook so the next person does not reopen Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist from zero.

Field story 5 for cloudflare email dns: NS not Cloudflare. Checklist on the wrong panel. Fixed NS. Keep that story in the runbook so the next person does not reopen Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist from zero.

For cloudflare email dns, symptom “Empty history” usually means Leftover or cached MX. Isolate it with Two resolvers. Do not stack a second change until that proof exists.

For cloudflare email dns, symptom “Unknowns missing” usually means Free HOLD. Isolate it with History hold. Do not stack a second change until that proof exists.

For cloudflare email dns, symptom “Header From rewritten” usually means Wrong hop. Isolate it with Received From. Do not stack a second change until that proof exists.

For cloudflare email dns, symptom “SMTP 550 send-as” usually means Free or unauthorized From. Isolate it with History line. Do not stack a second change until that proof exists.

For cloudflare email dns, symptom “spf=fail hop two” usually means Naive envelope. Isolate it with Return-Path. Do not stack a second change until that proof exists.

For cloudflare email dns, symptom “Still spam after clean hop” usually means Destination filters. Isolate it with Not an SLA. Do not stack a second change until that proof exists.

For cloudflare email dns, symptom “Self-send clean” usually means Short-circuit. Isolate it with Other mailbox. Do not stack a second change until that proof exists.

For cloudflare email dns, symptom “Wrong DNS panel” usually means NS ≠ registrar UI. Isolate it with NS lookup. Do not stack a second change until that proof exists.

Setup step “Inventory leftovers.” for cloudflare email dns: Screenshot current MX, SPF, DKIM, NS. Skip it and Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Verify the domain.” for cloudflare email dns: TXT as the dashboard states. Skip it and Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Create named aliases first.” for cloudflare email dns: Do not cut MX onto empty maps. Skip it and Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Publish one MX set.” for cloudflare email dns: Delete Google, Microsoft, registrar leftovers. Skip it and Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Prove from another mailbox.” for cloudflare email dns: Unique subject. Header From intact. Skip it and Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Only then send-as if paid.” for cloudflare email dns: Dashboard SPF/DKIM. Outbound probe. Skip it and Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Store the proof packet.” for cloudflare email dns: MX, hop, headers, plan name. Skip it and Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist turns into a second ticket next week. Do the step, store the artifact, then continue.

Trade-off on cloudflare email dns: choosing Exclusive MX + named aliases gets you Debuggable path and gives up You must delete leftovers. Write that exchange on the quote so nobody pretends it is free.

Trade-off on cloudflare email dns: choosing Dual MX backup gets you Feels safe and gives up Coin-flip misses. Write that exchange on the quote so nobody pretends it is free.

Trade-off on cloudflare email dns: choosing From rewrite gets you Cosmetic SPF and gives up Trust and DKIM. Write that exchange on the quote so nobody pretends it is free.

Trade-off on cloudflare email dns: choosing Suite seats gets you Hosted mailbox and gives up Per-user price. Write that exchange on the quote so nobody pretends it is free.

Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist is enough when You can staff exclusive MX and named aliases. If that condition is false, stop implementing cloudflare email dns and reopen the decision.

Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist is enough when You will keep Header From intact. If that condition is false, stop implementing cloudflare email dns and reopen the decision.

Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist is enough when You can probe from another mailbox. If that condition is false, stop implementing cloudflare email dns and reopen the decision.

Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist is the wrong ticket when History is empty and leftovers remain. Name the correct system instead of forcing cloudflare email dns to cover it.

Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist is the wrong ticket when You want an inbox placement SLA. Name the correct system instead of forcing cloudflare email dns to cover it.

Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist is the wrong ticket when You plan to rewrite visible From. Name the correct system instead of forcing cloudflare email dns to cover it.

Write cloudflare email dns in the subject line of the ticket and the layer in the first sentence. If the layer is leftover MX, say leftover MX. If the layer is HOLD, say HOLD. If the layer is a destination 550, paste the text. Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist stays short when the first sentence is honest.

Keep a standing calendar note for cloudflare email dns: monthly external probe, leftover MX lookup, and a glance at send-as counters if you are paid. Five minutes. The outage you avoid is the Friday dual-MX restore.

When two vendors disagree about cloudflare email dns, believe artifacts: two resolvers, one received copy, one history row. Do not believe the prettier admin center. Registrar dots lie. Composer UIs lie. Self-send lies.

Teach the next hire the MailerZ split before they touch cloudflare email dns: envelope may change, Header From must not, Free cannot send, unknowns HOLD, leftover MX is a hard stop, no inbox SLA, no SOC 2 sticker. That speech prevents a class of tickets.

If cloudflare email dns appears in an RFP, answer with published caps and hop evidence. Decline inbox-rate clauses. Decline fake certifications. Point at pricing and the Security and Trust Center. Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist is not a place to invent enterprise theater.

Export while the 14- or 90-day window still has the cloudflare email dns hop. Future-you will not remember the SMTP sentence. The destination mailbox remains the archive. We will not grow the store because a blog asked.

Do not bundle unrelated edits with cloudflare email dns. Rotating SMTP while republishing MX while enabling FORWARD is how you lose the ability to name the failure. One change, one probe, one stored copy.

If you need a suite, buy a suite for Calendar and a hosted mailbox. If you need a hop, buy a hop. Cloudflare Email DNS: MX, SPF, DKIM and DMARC Checklist does not become Exchange because a quote stacked seats next to aliases.

FAQ

Key takeaways

• Exclusive MX is a hard stop.
• Header From stays the original sender.
• SRS is envelope-only.
• Free holds unknowns and cannot send-as.
• 550 means read the text.
• Self-send lies.
• No inbox SLA.
• 14- or 90-day store is not an archive.
• MailerZ is not IMAP.
• No SOC 2, ISO, or HIPAA claims.

Conclusion and next action

Order is the checklist. NS, names, exclusive MX, then send records.

Next action: print the order, tick boxes with resolver output, not UI dots.

Review quarterly, or sooner if DNS hosts or dashboard instructions change. Author: MailerZ editorial, Secuno LLC.