Email authentication sounds settled: set up SPF, enable DKIM, move DMARC to reject, and your domain should be protected. But AWS is drawing attention to a problem that breaks that simple story. In a replay attack, a legitimate email your business already sent can be resent unchanged by someone else to new recipients, and it may still pass DKIM and DMARC. That matters well beyond IT. For brands, creators, ecommerce teams, and anyone sending newsletters, receipts, invoices, or campaign emails, the risk is reputational. The attacker cannot rewrite your message, according to the AWS explanation, but they can reuse your signed email and benefit from your domain’s trust. In practical terms, a real customer message can become bait delivered to people you never intended to contact. The business takeaway is clear: email authentication is still essential, but it does not cover every kind of abuse. Teams that rely on email for marketing, support, and audience relationships need to understand where the gaps are, what monitoring actually helps, and why routine DKIM rotation by itself is not a full answer.

What to know

  • A DKIM replay attack can reuse a real email your domain signed and send it to unintended recipients without changing the message.
  • Because DKIM can still pass during a replay, DMARC can also pass even when SPF fails.
  • Rotating DKIM keys is not enough if the old public key remains published in DNS.
  • Unknown IPs with DKIM pass are not automatically spoofing; they may be legitimate relays, replay abuse, or another anomaly.
  • AWS recommends building message-level evidence before treating unusual DMARC activity as confirmed replay.
  • For marketing and brand teams, the main risk is abuse of domain reputation and audience trust, not message forgery.

What AWS is warning about

AWS describes a scenario many domain owners would find confusing: DMARC reports show messages authenticating as your domain from IP addresses you do not recognize, even after you rotate your DKIM key and even if your DMARC policy is already set to reject.

The core reason is that DKIM checks whether signed parts of a message stayed unchanged between sender and receiver. If someone gets a copy of a legitimate email your organization already sent and resends it without altering it, the DKIM signature may still validate. Since DMARC only requires either SPF or DKIM to pass with alignment, the message can still be treated as authenticated.

AWS says this is not traditional spoofing. It is the reuse of a message you genuinely signed. That distinction matters because the response is different. A strict DMARC policy helps with unauthenticated forgery, but not with a message that already carries a valid aligned DKIM signature from your domain.

  • AWS frames replay as abuse of your domain’s reputation and delivery trust.
  • The attacker’s advantage is not editing your content but redistributing a real signed message.
  • A reject policy does not stop replay if DKIM still passes.

Why this matters for marketers, creators, and customer-facing teams

If your business sends order confirmations, support replies, newsletters, membership emails, or invoices, those messages are often trusted by recipients and mailbox providers because they come from your real domain. AWS notes that a replayed message can benefit from that trust and reach people you never contacted.

For marketing teams, that creates several downstream problems. First is brand confusion: recipients may associate unwanted email with your business even if your systems were not used to send it. Second is trust erosion: when people receive unexpected but authenticated messages from your domain, it becomes harder to maintain confidence in your email program. Third is measurement confusion: you may see signs of delivery activity in aggregate reports that do not match your actual campaign sends.

This also matters operationally. Teams often assume that if DMARC is on and DKIM was rotated, the remaining risk is low. AWS’s post shows that assumption can leave a blind spot. If you run content calendars, automations, or promotional email workflows, domain trust is part of your marketing infrastructure. Protecting it deserves the same attention as publishing and engagement workflows.

  • Authenticated abuse can still harm sender reputation and audience confidence.
  • Unexpected DMARC activity can create confusion for campaign reporting and email operations.
  • Brand and lifecycle marketing teams should treat email authentication as an ongoing monitoring task, not a one-time setup.

Put the idea into practice with PostPilot Daily’s content planner and publishing workspace.

Replay, spoofing, or a legitimate relay? Don’t guess

One of the most useful points in the AWS guidance is that an unfamiliar source IP with DKIM pass has multiple possible explanations. It could be a legitimate relay such as a mailing list, a forwarding rule, or a security gateway. It could be replay abuse. Or it could be ordinary spoofing, which AWS says usually shows up with DKIM failing rather than passing.

AWS recommends starting with DMARC aggregate reports, which can show source IP address, volume, and SPF and DKIM outcomes. That can reveal an anomaly, but AWS is explicit that aggregate counts alone do not prove replay. To confirm replay, you need message-level evidence showing that a message you sent matched one that reached recipients you did not address.

That recommendation matters for lean teams because it argues against overreacting. Removing keys or making DNS changes before understanding the cause could disrupt legitimate flows. A better approach is to treat strange activity as an anomaly first, then investigate whether it reflects an authorized relay, normal forwarding behavior, or a confirmed replay event.

  • DKIM pass from an unknown IP is not enough by itself to confirm replay.
  • Legitimate relays can preserve valid DKIM signatures as part of normal email behavior.
  • AWS advises building message-level evidence before making major remediation moves.

Why DKIM key rotation alone falls short

The headline lesson from AWS is simple: rotation and removal are different actions. Rotating a DKIM key means new mail starts using a new key and selector. But if the old public key remains available in DNS, previously signed messages can still be verified against it.

According to AWS, that means every email signed with the old key can remain replayable for as long as that DNS record exists. The commonly missed step is deleting the old public key from DNS after allowing enough time for in-flight legitimate email to arrive.

This is especially important during a confirmed active replay. In AWS’s framing, removing the old key is what closes the validation window for messages signed with it. For businesses that assumed rotation alone solved the problem, that is the major operational insight.

  • Rotation changes the key used for new email.
  • Removal deletes the old public key so older signed copies can no longer verify.
  • Leaving old records published can extend replay exposure.

What changes depending on your DKIM setup

AWS distinguishes between two Amazon SES approaches: Bring Your Own DKIM and Easy DKIM. With Bring Your Own DKIM, you generate the key pair and publish the public key yourself, which means you can rotate and remove keys on your own schedule, including during an incident.

With Easy DKIM, AWS says SES manages the underlying key material for you through DNS CNAME records that point to AWS-hosted keys. In that setup, there is not an on-demand option to immediately delete a specific key in the same way. AWS says teams using Easy DKIM during a confirmed replay are more dependent on early detection, on duplicate-message throttling already applied by receivers, and on longer-term protocol improvements such as the emerging DKIM2 effort.

For non-technical teams, the lesson is not that one method is universally better. It is that your response flexibility depends on how your email authentication is managed. Marketing leaders and operators should know which model their organization uses so they understand what incident response is realistically possible.

  • BYODKIM offers direct control over key rotation and removal.
  • Easy DKIM centralizes key management through AWS-managed infrastructure.
  • Your email setup affects how quickly you can respond during a replay incident.

The practical playbook AWS points to

AWS says the first step is not emergency DNS cleanup. It is enforcement and monitoring. If your domain is still at DMARC p=none, you are only monitoring. AWS recommends completing sender inventory, aligning legitimate senders with SPF and DKIM, and then advancing policy from none to quarantine to reject, reviewing reports at each stage.

Once enforcement is in place, AWS recommends improving detection. The post describes using Amazon SES configuration sets and event destinations to stream per-message events such as sends, deliveries, bounces, and complaints, then comparing that activity with what DMARC aggregate reports show receivers accepted under your domain.

That comparison is the key analytical move. If DMARC reports show DKIM-passing volume from IP addresses outside your SPF record that exceeds what your SES delivery events show for the same From domain and time period, AWS says that gap becomes a signal worth investigating. For teams building repeatable workflows, this is a reminder that security visibility belongs in the same operational stack as publishing and audience engagement. Readers who want tighter processes can also explore PostPilot Daily’s content planning, publishing, or engagement tools alongside their email operations.

  • Move DMARC toward enforcement if you are still only monitoring.
  • Keep an inventory of every legitimate sender, relay, and service touching your domain.
  • Correlate sending logs with DMARC reports to spot authenticated activity you did not originate.

Recommendations for small teams

Recommendation: treat email authentication as a brand protection workflow, not just an IT checklist. If your business depends on newsletters, receipts, or customer messaging, domain trust is part of your marketing asset base.

Recommendation: document who can send on behalf of your domain. AWS also mentions SES sending authorization to restrict which AWS principals can use a verified identity. That does not stop external replay, but it can reduce other sending risks inside your environment.

Recommendation: build a lightweight review rhythm. Even if a security team owns DNS, marketing and lifecycle teams should know what normal volume looks like, which tools send with the brand domain, and when unexpected DMARC patterns deserve escalation. That cross-functional awareness can shorten response time when trust issues show up in the inbox.

  • Know your DMARC policy stage and legitimate sender inventory.
  • Understand whether your organization uses BYODKIM or Easy DKIM.
  • Escalate unexplained DKIM-passing traffic rather than assuming it is harmless or just spoofing.

Source and further reading

Beyond DKIM key rotation: understanding email replay attacks ↗AWS Security Blog index listing publication date for the replay-attacks post ↗Original Content Rewards ↗

Frequently asked questions

What is a DKIM replay attack?

Based on AWS’s explanation, it is when someone obtains a copy of a legitimate email your domain signed and resends it unchanged to other recipients. Because the message is unchanged, the original DKIM signature may still validate.

Why doesn’t DMARC reject replayed email?

DMARC can pass if either SPF or DKIM passes with alignment. In a replay attack, SPF may fail because the sending IP is not yours, but DKIM can still pass, so DMARC can pass too.

Does rotating DKIM keys fix the issue?

Not by itself. AWS says rotating to a new key does not stop replay of messages signed with the old key if the old public key is still published in DNS.

How can a team tell replay from legitimate forwarding or relaying?

AWS says DMARC aggregate reports can show anomalies, but they cannot prove replay on their own. Confirmation requires message-level evidence matching a real message you sent to one that reached unintended recipients.

What should businesses do first?

AWS recommends confirming DMARC enforcement, inventorying legitimate senders and relays, and improving monitoring before making major DNS changes. For confirmed replay involving an old DKIM key, removing the old public key from DNS is the cleanup step AWS says is often missed.

JOIN THE CONVERSATION

Comments

0
Be constructive and stay on topic.

No comments yet. Start the conversation.