Home/Notes/TLS certificates for a small hotel
TLS certificates for a small hotel
28 Aug 2026
How a small hotel deals with TLS certificates — and what usually goes wrong.
The problem: an SPF record overwritten during a DNS edit. The certificate chain breaks for a small hotel.
We moved TLS certificates for a small hotel to a provider that supports DNSSEC. It added five minutes to the migration and closed a class of attacks they did not even know about.
A static site for a small hotel does not need a CDN, a build pipeline, or a container. It needs correct TLS certificates and a host that stays online.
The real issue was not TLS certificates itself — it was an SPF record overwritten during a DNS edit. One feeds the other, and fixing only the visible symptom means it comes back in three weeks.
A friend of the owner at a small hotel had set up TLS certificates years ago. When we audited, the config still pointed at a server they stopped paying for in 2024.
We told a small hotel that an SPF record overwritten during a DNS edit was a ticking clock. They agreed to fix it the same week — which is rare. Most clients wait until it actually detonates.
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