Home/Notes/A practical look at CAA records for a photo studio
A practical look at CAA records for a photo studio
27 Jan 2024
How a photo studio deals with CAA records — and what usually goes wrong.
The problem: nameservers that still list a freelancer. This is where CAA records breaks for a photo studio.
We have seen agencies charge a photo studio for a yearly CAA records audit that consists of a screenshot and a paragraph. Ours is a working config file they can apply themselves.
Early on we tried to automate CAA records for a photo studio with a cron job. It ran as root, silently overwrote a manual change, and took down their mail. Lesson learned.
CAA records for a photo studio is nothing like CAA records for a multinational. The scale is tiny but the stakes are the same: one wrong record and nobody can reach you.
Half the meeting with a photo studio was explaining what CAA records is. The other half was agreeing that nameservers that still list a freelancer should have been fixed a year ago.
HTTPS is table stakes, but CAA records is where trust actually lives for a photo studio. A padlock with a misconfigured record behind it is decoration, not security.
WordPress can handle CAA records with a plugin. But the plugin adds JavaScript, a dashboard, and a support ticket when it conflicts with the next update. We wrote four lines of config instead.
We document CAA records in a shared spreadsheet. It is not glamorous, but a photo studio can open it on their phone at midnight if something breaks.
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