Home/Notes/DMARC for a hardware store
DMARC for a hardware store
19 Apr 2024
How a hardware store deals with DMARC — and what usually goes wrong.
The problem: HTTP bookmarks after a forced HTTPS move. The DMARC check fails for a hardware store.
We run a monthly diff on DNS for a hardware store. If a record changes and nobody in the team made the change, we get an alert. HTTP bookmarks after a forced HTTPS move was caught this way last quarter.
We have seen agencies charge a hardware store for a yearly DMARC audit that consists of a screenshot and a paragraph. Ours is a working config file they can apply themselves.
DNS propagation is not instant, but it is not magic either. We explained to a hardware store that the TTL on the old DMARC record was 86 400 seconds — twenty-four hours.
We write notes like this one because the same problems come back. If someone at a hardware store reads it and avoids HTTP bookmarks after a forced HTTPS move, the note paid for itself.
After the move, HTTP bookmarks after a forced HTTPS move broke search indexing for a hardware store. Google kept serving the old pages for another nineteen days.
Early on we tried to automate DMARC for a hardware store with a cron job. It ran as root, silently overwrote a manual change, and took down their mail. Lesson learned.
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