Home/Notes/A practical look at HTTP to HTTPS for an accountant
A practical look at HTTP to HTTPS for an accountant
10 Jul 2026
How an accountant deals with HTTP to HTTPS — and what usually goes wrong.
The problem: a lastmod stamp that never changes. The certificate chain breaks for an accountant.
Launch day for an accountant is usually light. Week three is when leftover tags, fonts, and staging URLs show up. a lastmod stamp that never changes is the usual passenger.
Nobody at an accountant could remember who had configured HTTP to HTTPS. The credentials were in a text file inside a folder called OLD STUFF on a shared drive.
A friend of the owner at an accountant had set up HTTP to HTTPS years ago. When we audited, the config still pointed at a server they stopped paying for in 2024.
We underestimated how long HTTP to HTTPS migration would take for an accountant. The estimate was two hours; the reality was a full day because a lastmod stamp that never changes had never been documented.
Big agencies solve HTTP to HTTPS with a team. We solve it with a checklist and a dig command. The result is the same; the invoice is shorter.
Related work on this site follows the same principle: one job, a real inbox, no theatre. an accountant did not need four analytics dashboards to know that Tuesdays are slow.
When an accountant asked for a quote on HTTP to HTTPS, we sent a one-paragraph email instead of a slide deck. They signed the same day.
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