Email Sender Authentication (SPF, DKIM, DMARC) Rollout: Fewer Spoofed Emails, Better Delivery

Marketing & Sales

Email Sender Authentication (SPF, DKIM, DMARC) Rollout: Fewer Spoofed Emails, Better Delivery

Intermediate | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)

Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.

Roll out email sender authentication (SPF, DKIM, DMARC) by listing all senders, setting up SPF and DKIM, then tightening DMARC from none to quarantine to reject, so less real mail gets blocked. Companies that email newsletters or invoices can use it to cut spoofed mail and help messages reach partners. Senders are rarely just the office mailbox: mailing services, invoicing tools, and form auto-replies are often contracted by separate teams, so build a sender register from the DNS console and each service. Pitfalls include tightening before a mailing service is registered, jumping straight to reject, nobody reading aggregate reports, and leaving unused domains unprotected, so name a report reader and a register review date first. SPF and DKIM values differ by service, so check each service's latest guide. The whiteboard has 4 A4 pages (inventory, the three mechanisms, ordering, tightening and spoofing replies); the task board has 5 columns, 4 parent tasks, and 12 subtasks.

0 Likes 0 Copies Author: WeProcess
email authentication DMARC SPF DKIM email spoofing
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Read the whiteboard text as plain text

Email Authentication (SPF, DKIM, DMARC) Rollout Board

How to use (4 pages in all): ① Write the goal and list your senders (frames①–⑤) → ② Learn SPF, DKIM, and DMARC and set the work per sender (frames⑥–⑨) → ③ Check the pitfalls and set the order and the report reader (frames⑩–⑭) → ④ Tighten DMARC step by step and plan spoofing replies (frames⑮–⑰)

1/4 List all senders

① Goal and scope (start here)

  • Why you are rolling this out e.g. A partner reported a suspicious email in our name and said our invoices land in spam
  • Target domains e.g. The company domain and one domain from the old company name
  • Owner and timeline e.g. IT leads, with finance and marketing helping. Aim for reject within 3 months and extend if the reports show problems

② Sender register (start with the main 4, put the rest in ③ and ④)

Service name Owner SPF status DKIM status
Company mail e.g. Google Workspace e.g. IT team e.g. Yes (seen in the DNS console) e.g. Enabled (seen in the admin console)
Mailing service e.g. Newsletter service e.g. Marketing e.g. None e.g. Not set up
Invoice sending e.g. Invoicing service e.g. Finance e.g. Unknown, ask the vendor e.g. Unknown, ask the vendor
Contact form replies e.g. Website form auto-reply e.g. Web team e.g. None e.g. None

③ Sent from inside the company

  • e.g. Notification emails from attendance or approval systems
  • e.g. A multifunction printer that emails scans
  • Write the sender address and which device or service sends it

④ Sent from outside services

  • e.g. Invitation emails from a scheduling service
  • e.g. Application receipts from a recruiting site
  • Write the contracting team and who can access the admin console

⑤ Unused domains (pitfall: neglect)

  • e.g. An old company name domain that sends no mail
  • What happens: spoofers can use the domain to impersonate you, and recipients struggle to tell. How to check: the domain contract list and the DNS console
  • How to prevent: for domains that send no mail, publish SPF with no allowed senders and DMARC reject. Check the values in the latest guide from your registrar

2/4 Learn the three checks

⑥ SPF (list of allowed senders from ②)

  • What it checks: whether that sender may send mail for this domain
  • Where it is set: the DNS console for the domain. Keep one SPF record per domain
  • When adding an external service, add the value from its guide to the same record. Each addition adds DNS lookups, and SPF fails above the standard limit of 10, so count the current lookups before adding
  • Note: forwarded mail often fails SPF, so pair it with DKIM

⑦ DKIM (a digital signature per sender)

  • What it checks: whether the message was altered in transit, and which domain signed it
  • Where it is set: create the signature in the sending service console and publish it in DNS
  • The signature name (selector) differs by service
  • e.g. For a mailing service, turn on the custom domain signature

⑧ DMARC (what to do with mail that fails)

  • What it checks: whether the visible From domain matches the domain that passed SPF or DKIM
  • Where it is set: one record per domain in the DNS console
  • Tell receivers whether failing mail should only be monitored, sent to spam, or rejected
  • You can set an address for aggregate reports. Decide who reads them in ⑭

⑨ Work per sender (carry over the 4 rows of ②, add notes for senders in ③ and ④)

SPF work DKIM work Guide location and deadline
Company mail e.g. Keep the current record e.g. Keep it enabled e.g. Admin console help, confirmed
Mailing service e.g. Check the service guide and decide whether to add it e.g. Turn on the custom domain signature e.g. Mailing service guide, by week 2
Invoice sending e.g. Ask the vendor for its senders, then add e.g. Ask the vendor whether it can sign e.g. Ask the vendor, week 1
Contact form replies e.g. Add the sending server e.g. Create a signature in the server console e.g. Hosting company guide, by week 3

3/4 Set the tightening order

⑩ Pitfall: forgotten senders (from the table in ⑨)

  • What happens: e.g. A mailing service is missing from the register, so the newsletter lands in spam after tightening
  • How to check: e.g. Show the register in ② to finance, sales, and web staff and ask what is missing
  • How to prevent: e.g. Make it a rule to add a new service to the register before using it
  • e.g. If a report shows a sender not in the register, ask the owner

⑪ Pitfall: jumping straight to reject

  • What happens: e.g. Legitimate mail with a missing setting is rejected by receivers, and you notice late
  • How to check: e.g. In the DNS console, see whether DMARC starts at monitoring only (none)
  • How to prevent: e.g. Go through the 3 stages in ⑮ in order and read the reports at each stage before moving on
  • e.g. Decide the rollback steps and who makes the call beforehand

⑫ Pitfall: nobody reads the reports

  • What happens: e.g. Blocked mail and senders missing from the register go unnoticed, so you cannot decide to tighten
  • How to check: e.g. Check the report address in DMARC and the date it was last read
  • How to prevent: e.g. Name a reader and a day in ⑭
  • e.g. If the volume is high, consider a service that summarizes reports

⑬ Rank ⑤ and the pitfalls ⑩–⑫ (impact vs. readiness)

Vertical axis: Impact (higher = bigger) / Horizontal axis: Readiness (further right = more ready)

  • Act first High impact, not ready yet. e.g. Forgotten senders (the invoicing service was not in the register)
  • Check at each stage High impact but prepared. e.g. Jumping to reject (rollback steps and decision maker are set)
  • Assign an owner and close it Low impact, not ready yet. e.g. Unread reports (an address exists but nobody reads them)
  • Keep as is Low impact and prepared. e.g. Unused domains (the step in ⑤ is already set)

⑭ Who reads the aggregate reports

  • Owner: ____ e.g. IT team. When away, the marketing owner
  • How often e.g. 15 minutes every Monday morning
  • What to look for e.g. Senders not in the register, legitimate mail that fails, and unfamiliar mail sent in your name

4/4 Tighten step by step

⑮ DMARC stages (when ⑬ is ready, the owner in ⑭ advances using the reports)

  1. none monitor only e.g. Receive reports and check for senders missing from the register in ②. Do not change how mail is handled
  2. quarantine to spam folder e.g. Ask receivers to send failing mail to spam. Check that no legitimate mail lands there
  3. reject block e.g. Ask receivers to refuse failing mail, once the only failures in the reports are spoofing

⑯ Timing, checks, and decision per stage

Timing What to check Decision (advance, wait, roll back)
none (monitor) e.g. Month 1. Read reports weekly e.g. Whether every sender in the reports is in the register ② e.g. Advance once every sender in the register passes DMARC (aligned with the From domain)
quarantine e.g. Month 2 e.g. Whether anyone says legitimate mail landed in spam e.g. If so, go back to monitoring and fix the sender at fault
reject e.g. From month 3 e.g. Whether the only failures are spoofing e.g. If legitimate mail fails, go back one stage
After tightening e.g. Monthly e.g. Whether any new service is planned e.g. When adding one, add it to the register and finish the work in ⑨ before use

⑰ Responding to spoofing reports

  • Receive e.g. When a partner reports a suspicious email in your name, the intake owner: ____ takes the details
  • Verify e.g. Ask for the date, subject, and sender, then check the register in ② and the reports that the owner in ⑭ reads to see if it is one of your senders. Tell them not to click links in the email
  • Notify e.g. If it is spoofing, post a notice on your website warning people and showing the correct sender address

Task board contents

Unchecked 16 items

List all senders

On whiteboard page 1, write the goal and list every sender that uses your domain in a register. Gaps in the register will block legitimate mail once DMARC tightens, so start here. Press Ctrl+F (⌘F on Mac) and type "3/4" to jump to page 3.

Check DNS records

Open the DNS console at your domain registrar and check for an SPF record starting with "v=spf1" and a DMARC record named "_dmarc". Write yes or no in the SPF status column of frame ②, and note whether a DMARC record exists in the domain note of frame ①. You only look, so change nothing.

Ask who sends mail

Ask finance, sales, marketing, and web staff which services send from your domain, and write them in the register in frame ② and in frames ③ and ④. Done when no team has more to add.

Find idle domains

Check the list of contracted domains and write the ones that send no mail in frame ⑤, including old company names and campaign domains. Done when all are listed.

Learn the 3 checks

On whiteboard page 2, learn what SPF, DKIM, and DMARC each check and where they are set, then write the work needed for each sender listed in the page 1 register. Once the work is set, you can move through it one item at a time in the Configuring column.

Read SPF and DKIM

Read frames ⑥ and ⑦ to learn what SPF and DKIM check and where they are set. Done when no unfamiliar term remains.

Read about DMARC

Read frame ⑧ to see how DMARC compares the SPF and DKIM results with the sender domain, and confirm where aggregate reports go.

Map work per sender

In the table in frame ⑨, write the SPF and DKIM work for each sender from ②, with the guide location and deadline. For senders in ③ and ④, add sticky notes under the table with the same three points. Done when every sender in the register is covered.

Order the rollout

On whiteboard page 3, check the pitfalls, rank them by impact and readiness, and decide the order of action. Decide who reads the DMARC aggregate reports here too, because without a reader, blocked mail goes unnoticed once you tighten.

Note the pitfalls

In frames ⑩ to ⑫, write what would happen at your company, how to check, and one step to prevent it. Done when all three pitfalls have an example of your own.

Rank by impact/prep

In the four quadrants of frame ⑬, place the pitfalls from ⑤ and ⑩ to ⑫, then decide the order of action starting with the top-left quadrant.

Pick report reader

In frame ⑭, write who reads the aggregate reports, on which day, and what to look for. Done when that person agrees.

Tighten gradually

On whiteboard page 4, build the table for tightening DMARC from monitoring to spam folder to reject, and decide how to handle spoofing reports. Keep reading reports in the Monitoring column, and move the task to Fully tightened once you reach reject.

Start with none

In the none (monitor) row of frames ⑮ and ⑯, write when you start and what to check, then publish a monitoring-only DMARC record in the DNS console. Check the values in the latest guide from your DNS provider.

Decide to advance

Following the decision column in frame ⑯, decide from the reports whether to advance, wait, or roll back. Add the date and reason to the table.

Plan spoof replies

In frame ⑰, write how to receive, verify, and announce when a partner reports spoofing in your name. Done when the intake person is named.

Taking inventory 0 items

Configuring 0 items

Monitoring 0 items

Fully tightened 0 items

← Back to templates

Preview mode Email Sender Authentication (SPF, DKIM, DMARC) Rollout: Fewer Spoofed Emails, Better Delivery

Whiteboard preview

① Goal and scope (start here) ② Sender register (start with the mai... ③ Sent from inside the company ④ Sent from outside services ⑤ Unused domains (pitfall: neglect) ⑥ SPF (list of allowed senders from ②) ⑦ DKIM (a digital signature per sender) ⑧ DMARC (what to do with mail that fa... ⑨ Work per sender (carry over the 4 r... ⑩ Pitfall: forgotten senders (from th... ⑪ Pitfall: jumping straight to reject ⑫ Pitfall: nobody reads the reports ⑬ Rank ⑤ and the pitfalls ⑩–⑫ (impact... Act first Check at each stage Assign an owner and close it Keep as is ⑭ Who reads the aggregate reports ⑯ Timing, checks, and decision per stage ⑰ Responding to spoofing reports Email Authenticat... How to use (4 pag... Goal and target s... Mechanisms and de... Pitfalls and bloc... Findings and next... 1/4 List all senders Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Learn the three c... ↙ 3/4 Why you are rolling this oute.g. A partner reported a suspicious email in our name and said our invoices land in spam Target domainse.g. The company domain and one domain from the old company name Owner and timelinee.g. IT leads, with finance and marketing helping. Aim for reject within 3 months and extend if the reports show problems Service name Owner SPF status DKIM status Company mail e.g. Google Workspace e.g. IT team e.g. Yes (seen in the DNS console) e.g. Enabled (seen in the admin console) Mailing service e.g. Newsletter service e.g. Marketing e.g. None e.g. Not set up Invoice sending e.g. Invoicing service e.g. Finance e.g. Unknown, ask the vendor e.g. Unknown, ask the vendor Contact form replies e.g. Website form auto-reply e.g. Web team e.g. None e.g. None e.g. Notification emails from attendance or approval systems e.g. A multifunction printer that emails scans Write the sender address and which device or service sends it e.g. Invitation emails from a scheduling service e.g. Application receipts from a recruiting site Write the contracting team and who can access the admin console e.g. An old company name domain that sends no mail What happens: spoofers can use the domain to impersonate you, and recipients struggle to tell. How to check: the domain contract list and the DNS console How to prevent: for domains that send no mail, publish SPF with no allowed senders and DMARC reject. Check the values in the latest guide from your registrar What it checks: whether that sender may send mail for this domain Where it is set: the DNS console for the domain. Keep one SPF record per domain When adding an external service, add the value from its guide to the same record. Each addition adds DNS lookups, and SPF fails above the standard limit of 10, so count the current look… Note: forwarded mail often fails SPF, so pair it with DKIM What it checks: whether the message was altered in transit, and which domain signed it Where it is set: create the signature in the sending service console and publish it in DNS The signature name (selector) differs by service e.g. For a mailing service, turn on the custom domain signature What it checks: whether the visible From domain matches the domain that passed SPF or DKIM Where it is set: one record per domain in the DNS console Tell receivers whether failing mail should only be monitored, sent to spam, or rejected You can set an address for aggregate reports. Decide who reads them in ⑭ SPF work DKIM work Guide location an... Company mail e.g. Keep the current record e.g. Keep it enabled e.g. Admin console help, confirmed Mailing service e.g. Check the service guide and decide whether to add it e.g. Turn on the custom domain signature e.g. Mailing service guide, by week 2 Invoice sending e.g. Ask the vendor for its senders, then add e.g. Ask the vendor whether it can sign e.g. Ask the vendor, week 1 Contact form replies e.g. Add the sending server e.g. Create a signature in the server console e.g. Hosting company guide, by week 3 3/4 Set the tightenin... → 4/4 4/4 Tighten step by step What happens: e.g. A mailing service is missing from the register, so the newsletter lands in spam after tightening How to check: e.g. Show the register in ② to finance, sales, and web staff and ask what is missing How to prevent: e.g. Make it a rule to add a new service to the register before using it e.g. If a report shows a sender not in the register, ask the owner What happens: e.g. Legitimate mail with a missing setting is rejected by receivers, and you notice late How to check: e.g. In the DNS console, see whether DMARC starts at monitoring only (none) How to prevent: e.g. Go through the 3 stages in ⑮ in order and read the reports at each stage before moving on e.g. Decide the rollback steps and who makes the call beforehand What happens: e.g. Blocked mail and senders missing from the register go unnoticed, so you cannot decide to tighten How to check: e.g. Check the report address in DMARC and the date it was last read How to prevent: e.g. Name a reader and a day in ⑭ e.g. If the volume is high, consider a service that summarizes reports Vertical axis: Im... High impact, not ready yet. e.g. Forgotten senders (the invoicing service was not in the register) High impact but prepared. e.g. Jumping to reject (rollback steps and decision maker are set) Low impact, not ready yet. e.g. Unread reports (an address exists but nobody reads them) Low impact and prepared. e.g. Unused domains (the step in ⑤ is already set) Owner: ____e.g. IT team. When away, the marketing owner How oftene.g. 15 minutes every Monday morning What to look fore.g. Senders not in the register, legitimate mail that fails, and unfamiliar mail sent in your name ⑮ DMARC stages (w... nonemonitor only e.g. Receive reports and check for senders missing from the register in ②. Do not change how mail is handled quarantineto spam folder e.g. Ask receivers to send failing mail to spam. Check that no legitimate mail lands there rejectblock e.g. Ask receivers to refuse failing mail, once the only failures in the reports are spoofing Timing What to check Decision (advance... none (monitor) e.g. Month 1. Read reports weekly e.g. Whether every sender in the reports is in the register ② e.g. Advance once every sender in the register passes DMARC (aligned with the From domain) quarantine e.g. Month 2 e.g. Whether anyone says legitimate mail landed in spam e.g. If so, go back to monitoring and fix the sender at fault reject e.g. From month 3 e.g. Whether the only failures are spoofing e.g. If legitimate mail fails, go back one stage After tightening e.g. Monthly e.g. Whether any new service is planned e.g. When adding one, add it to the register and finish the work in ⑨ before use Receivee.g. When a partner reports a suspicious email in your name, the intake owner: ____ takes the details Verifye.g. Ask for the date, subject, and sender, then check the register in ② and the reports that the owner in ⑭ reads to see if it is one of your senders. Tell them not to click links in the email Notifye.g. If it is spoofing, post a notice on your website warning people and showing the correct sender address → 2/4 Learn the three c... ↙ 3/4 Set the tightenin... → 4/4 Tighten step by step
100%

Drag to move, scroll to zoom