iCloud Mail header-smuggling flaws let users forge any @icloud.com sender past DMARC
SEC Consult's Timo Longin found two iCloud Mail flaws letting any signed-in user send SPF-, DKIM- and DMARC-passing mail as any @icloud.com address. A filter that read only those verdicts could not tell the forgeries from mail the real address owner sent.
Reality
- Evidence40
- Adoption
- Not scored
- Hype gap+5
- Incentives
- Not scored
- Confidence45
buildOne report1 publisher DMARC fails mail that passes SPF and DKIM under the wrong domain
Transactional mail can pass SPF and DKIM and still fail DMARC when neither aligns with the visible From domain, a dev.to Node.js guide shows. Because forwarding breaks SPF, the author treats aligned DKIM as the path to protect.
Reality
- Evidence45
- Adoption
- Not scored
- Hype gap+15
- Incentives35
- Confidence50
buildOne report1 publisher Forwarding support mail under its own DKIM key let every spam pitch into CogniPrep's inbox
CogniPrep's support forwarder sent inbound mail onward under its own DKIM key, so 100% of mail to its catch-all address, junk included, reached the inbox. Teams relaying mail under their own domain blind the receiving filter the same way and must score it themselves.
Reality
- Evidence45
- Adoption5
- Hype gap0
- Incentives
- Not scored
- Confidence50
buildOne report1 publisher Per-tenant SPF, DKIM and DMARC checks give each publisher domain its own rollback point
Publishers onboarding custom domains should confine wildcard DNS to routing and verify three mail records per tenant, a dev.to guide argues. That costs extra writes and waiting, and it gives every customer its own rollback boundary and audit trail.
Reality
- Evidence45
- Adoption
- Not scored
- Hype gap0
- Incentives
- Not scored
- Confidence50
buildOne report1 publisher HMAC-signed links handle one-click unsubscribe in a 1,258-line self-hosted newsletter server
Mrsaynothing.dev's author runs a newsletter on 1,258 self-written lines of TypeScript, Svelte and SQL built around RFC 8058's one-click unsubscribe headers. Signed links cover the compliance, while aligned DKIM, the cost of skipping a paid relay, is still missing.
Reality
- Evidence45
- Adoption5
- Hype gap+10
- Incentives30
- Confidence50
The request came from an unauthorized account on a real government domain, and Revolut acted on it. The company calls the number of affected customers limited, and it declined to say how many or name the agency.
Perspective Coverage
5 publishers
- Builder
- Builder 23%
- Operator
- Operator 55%
- Investor
- Investor 22%
Reality
- Evidence68
- Adoption
- Not scored
- Hype gap+10
- Incentives55
- Confidence66
buildOne report1 publisher Five fields in the aggregate XML decide when DMARC can leave p=none
Publishing p=none starts an XML report feed and enforces nothing. A practitioner sequence for getting a domain to p=reject turns on an owned sender inventory, aligned DKIM and a written condition for each step.
Reality
- Evidence62
- Adoption
- Not scored
- Hype gap+10
- Incentives20
- Confidence55
buildOne report1 publisher A bounce-safe welcome path makes the outbox message ID the transport idempotency key
A dev.to post argues that the email API versus SMTP question follows from where suppression lookups, message IDs and delivery-event state live, and its Go sketch leaves the transport as the only interface the decision touches.
Reality
- Evidence48
- Adoption
- Not scored
- Hype gap+5
- Incentives20
- Confidence60
buildOne report1 publisher Deleting pct=25 from a DMARC record quadruples the mail your policy touches
RFC 9989 removed the pct tag on 19 May 2026, and a record still carrying pct=25 describes a staged rollout that conforming receivers no longer honour. The replacement, t=y, gives one testing step and no percentages.
Reality
- Evidence64
- Adoption
- Not scored
- Hype gap+18
- Incentives22
- Confidence58
buildOne report1 publisher Suppressing on the three-digit code converts a policy refusal into a dead address
In four codebases a dev.to author found bounce handlers that read 5.x.x and stopped, so a receiver's verdict on the sending domain got written down as a dead mailbox. The RFC 3463 subject digit separates the two.
Reality
- Evidence55
- Adoption
- Not scored
- Hype gap+12
- Incentives40
- Confidence57
buildOne report1 publisher Counting the full SPF include tree nightly catches the vendor include that breaks your record
The DNS and header half of deliverability is a pure function of your own configuration, so a scheduled job can assert it; inbox placement is a measurement you put on a dashboard with a date on it.
Reality
- Evidence52
- Adoption
- Not scored
- Hype gap+10
- Incentives55
- Confidence55
buildOne report1 publisher Receivers blend marketing and password reset mail into one history for the From: domain
A dev.to walkthrough splits outbound mail by risk profile. Whether that split changes anything for receivers comes down to one tag: sp= on the organizational domain. Subdomains still need their own SPF and DKIM either way.
Reality
- Evidence58
- Adoption
- Not scored
- Hype gap+12
- Incentives60
- Confidence55
buildOne report1 publisher Querying the zone's own nameservers removes one of seven DNS false alarms
The author of DNS Notify lists seven kinds of change alert that mean nothing, and only the first is cured by changing where the query goes. The other six get fixed after the answer arrives.
Reality
- Evidence58
- Adoption
- Not scored
- Hype gap+12
- Incentives78
- Confidence62
buildOne report1 publisher Two authentication passes on unrelated domains still fail DMARC alignment
A dev.to walkthrough traces a newsletter whose SPF and DKIM both pass for example.net while the visible From reads editorial.example. The evidence that settles it sits in the receiver's Authentication-Results header.
Reality
- Evidence58
- Adoption
- Not scored
- Hype gap+8
- Incentives25
- Confidence55
Revolut handed identity files and Bitcoin histories to an email that passed SPF, DKIM and DMARC
The request arrived from what looked like a government agency's domain, cleared all three email authentication checks, and Revolut's compliance team processed it. Notifications to affected customers began on September 11.
Reality
- Evidence35
- Adoption30
- Hype gap+25
- Incentives60
- Confidence45
buildOne report1 publisher Two records for one DNS entry turn a verified badge into a drift check
A dev.to onboarding design keeps the SPF, DKIM and DMARC values you generated in one row and the answers a resolver returned in another. Its comparator is a single stripped string match, so an SPF value the customer appended to lands in drifted.
Reality
- Evidence45
- Adoption
- Not scored
- Hype gap+15
- Incentives20
- Confidence60
buildOne report1 publisher Microsoft flags 1 million-plus AI-crafted scam emails seeking nearly $50,000 ACH transfers, success unconfirmed
Microsoft Security Research reported over a million emails pairing fake ServiceNow invoices with forged forward threads. No malware ran, so the investigation lives in mail headers and accounting records.
Reality
- Evidence45
- Adoption30
- Hype gap−10
- Incentives65
- Confidence55
Direct Send carried 29,785 spoofed internal emails past the mail gateway in two months
KnowBe4's Threat Lab logged the messages across July and August 2026. None of them needed a stolen password to look like mail from HR or accounting, and a single send addressed 900 recipients. The report landed September 10.
Reality
- Evidence57
- Adoption54
- Hype gap+14
- Incentives68
- Confidence56
buildOne report1 publisher A lapsed Carnival promo domain routed authenticated booking mail into a cloaked malware network
A genuine Carnival booking confirmation passed SPF, DKIM and DMARC and pointed at a promotional domain the company had let lapse. Someone re-registered it, wired it into a cloaking network, and the link kept routing for 74 days.
Reality
- Evidence62
- Adoption42
- Hype gap−12
- Incentives30
- Confidence57
Trezor's spoofed alert reused the language of the $112.7m Coldcard exploit
The email telling Trezor owners their recovery phrases might lack entropy came from a real trezor.io address and passed DKIM, SPF and DMARC, and it described a defect close to the one that took 1,778.84 BTC from Coldcard users.
Reality
- Evidence42
- Adoption55
- Hype gap+22
- Incentives58
- Confidence45