We compile a summary document specifically covering your hosting and infrastructure — provider, plan, key settings, DNS configuration — a focused reference for exactly this one area, distinct from the broader technical architecture document that covers your whole system.
Hosting & infrastructure summary document
A focused summary of your hosting and DNS setup, distinct from the broader architecture document.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to your hosting control panel and DNS management
- Confirmation of any specific hosting details you already know need documenting
- Your preferred document format
This or something else?
| You want a focused summary document specifically covering hosting and infrastructure | This fix covers it |
| You want the broader technical architecture documented, not just hosting | Technical architecture document, a wider-scope, related document |
| You want DNS records specifically audited for accuracy, not just documented | DNS record audit & correction, in the Hosting & Infrastructure bucket, a diagnostic fix rather than documentation |
| You want this as part of a full developer onboarding bundle | Onboarding pack for incoming developer |
What we do
- Review your hosting provider, plan, and key configuration settings
- Document your current DNS configuration
- Note any hosting-specific quirks or limitations worth flagging
- Compile into a clear, focused summary document
- Review for accuracy
What is included
- A focused hosting and infrastructure summary document
- Documented DNS configuration
- Notes on hosting-specific quirks or limitations
- An accuracy review
Not included
- Broader technical architecture documentation beyond hosting specifically — a separate, wider document
- Auditing DNS records for correctness — a separate, diagnostic fix
- Fixing any hosting issue identified while documenting
- Ongoing updates as your hosting configuration changes
Questions about this fix
Why would I need this as well as the architecture document?
The architecture document covers your broader system at a higher level; this stays narrowly on hosting and DNS specifically, which is often the part you actually need in hand during a migration or a support call with your host.
Will this flag if my DNS records have an error?
Not as its primary purpose — this documents what's currently configured; a dedicated DNS audit specifically looks for actual errors or discrepancies.
Is this useful if I'm considering switching hosts?
Yes, having your current hosting details clearly documented makes evaluating and planning a potential migration considerably easier.
Does this include my hosting account credentials?
Only if you specifically want them included — we'd confirm your preference, since credential handling is a separate consideration from general documentation.
Would this need revisiting if I switch hosts later?
Yes — a migration to a new host would make the details in this document outdated, so it's worth revisiting once the move is complete rather than relying on the old version.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.