Home/Notes/Managing TLS certificates at a bakery
Managing TLS certificates at a bakery
17 Apr 2026
How a bakery deals with TLS certificates — and what usually goes wrong.
The problem: a form that emails a shared inbox. The certificate chain breaks for a bakery.
The real issue was not TLS certificates itself — it was a form that emails a shared inbox. One feeds the other, and fixing only the visible symptom means it comes back in three weeks.
Most of the damage we see in TLS certificates comes from doing too much. A single correct record beats three that were supposed to be clever.
Before you touch TLS certificates, take a screenshot of the current state. Half of our emergency calls come from people who cannot remember what was there before the change.
Most providers let you export TLS certificates as a zone file. We keep one in version control for every client. If the hosting vanishes, the zone file rebuilds the domain in minutes.
Crawlers and people want the same thing from TLS certificates: one URL, a title that matches the heading, and a next link that goes somewhere real.
Half the meeting with a bakery was explaining what TLS certificates is. The other half was agreeing that a form that emails a shared inbox should have been fixed a year ago.
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