Home/Notes/How a restaurant should handle CAA records
How a restaurant should handle CAA records
5 Apr 2025
How a restaurant 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 restaurant.
Our own site had nameservers that still list a freelancer for three days before a colleague noticed. We added it to the pre-launch checklist the same afternoon.
We got a call from a restaurant on a Friday. Their CAA records had expired overnight, and the booking page was returning errors to every visitor.
We rotate API keys for CAA records annually. a restaurant did not see the point until we showed them the access log: the old key had been used from an IP in a country nobody on their team has visited.
A phishing page copying a restaurant appeared last year. The only reason their customers could tell it apart was that CAA records was set up correctly on the real site.
We check CAA records for a restaurant once a quarter. It takes five minutes and has caught two problems in the past year. Both would have caused downtime within a week.
A free certificate and a correct CAA records record will do more for a restaurant than a redesign that ships with nameservers that still list a freelancer still in place.
After fixing CAA records, we added a monitoring alert. If the record changes or the certificate approaches expiry, both we and a restaurant get an email. No surprises.
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