Home/Notes/A practical look at DMARC for a florist

A practical look at DMARC for a florist

18 Jul 2026

How a florist deals with DMARC — and what usually goes wrong.

Sender outbound email DNS lookup DMARC DMARC a chat widget that… Mail server florist.com Inbox delivered

The problem: a chat widget that blocks the submit button. The DMARC check fails for a florist.

The worst DMARC failure we have seen at a florist was invisible for eight months. The backup existed but had never been tested, and the data inside was three migrations old.

The vendor promised a florist that DMARC was handled. We verified: it was not. Trust but verify has saved more uptime than any product we have used.

We hand over a one-page document after every DMARC job. It says what was changed, what the login is, and what to check if something feels wrong. a florist keeps it in a drawer they actually open.

After the move, a chat widget that blocks the submit button broke search indexing for a florist. Google kept serving the old pages for another nineteen days.

DMARC for a florist is nothing like DMARC for a multinational. The scale is tiny but the stakes are the same: one wrong record and nobody can reach you.

More notes

Related notes

Tell us what you need.

Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.

hello@digitalserved.com