Copyable client message
Hi [client name], before we make website or launch changes, please confirm who controls the domain, DNS, hosting, CDN, and email records.
We need registrar access or an invited user role, hosting access, DNS provider details, backup information, CDN access if used, and approval for any launch-related record changes.
Request checklist
| Area | Ask for |
|---|---|
| Domain | Registrar, domain name, renewal owner, invite process |
| DNS | DNS host, records owner, approval for changes |
| Hosting | Provider, control panel, SSH/SFTP if needed, staging |
| CDN | Cloudflare or CDN access, cache rules, SSL settings |
| MX provider, email records, sender authentication notes | |
| Backups | Backup location, restore process, launch rollback owner |
Ownership notes
The client should usually keep ownership of the domain. Ask for delegated access or a guided change process instead of asking them to transfer ownership casually.
Portal upgrade
Kicklayer keeps access requests attached to the project, so the launch checklist does not depend on finding one old email with the registrar details.
Client-ready request
A version you can paste into an email, Slack thread, or Kicklayer portal.
Hi [client name], please send the domain and hosting details for this project: registrar name, hosting provider, DNS owner, current website URL, staging or production access, SSL/CDN details, backup process, and who can approve DNS or launch changes.
How to structure the request
Break the ask into fields a client can answer cleanly, rather than a single vague upload request.
Registrar
Required access
Identify where the domain is registered and who can approve DNS changes.
Hosting
Required access
Request hosting panel, SFTP, database, staging, or collaborator access as needed.
DNS records
Required text
Collect important records for website, email, verification, CDN, and redirects.
Backups
Required text
Ask how backups work, where they are stored, and who can restore them.
Launch approval
Required approval
Name the person authorized to approve DNS, SSL, CDN, and go-live changes.
Client request breakdown
These are the asks that make the request specific enough for the client to complete without a follow-up loop.
Domain
Confirm registrar, domain owner, and DNS manager.
Registrar, DNS, and hosting may be three different services.
Hosting
Share hosting panel, SFTP, database, staging, and backup details.
Launch and troubleshooting often need more than CMS access.
Identify email records and services that must not be disrupted.
DNS mistakes can break client email.
Security
Confirm SSL, CDN, firewall, and access restrictions.
Security layers can block deployment or verification.
Launch
Set launch window, rollback plan, and approval owner.
DNS changes should have timing and accountability.
Make the request easier to complete
Small wording choices change whether a client sends useful material or another incomplete reply.
Do
- Ask who owns DNS before requesting changes.
- Document email-related records before launch work.
- Confirm backups and rollback process.
- Separate registrar access from hosting access.
Avoid
- Assume the hosting provider controls DNS.
- Change records without knowing email dependencies.
- Request shared owner passwords when collaborator access exists.
- Launch without a named approver and rollback path.
When the checklist becomes a portal
The same request becomes more reliable when every field has an owner, a status, and a place to submit it.
Domain, hosting, DNS, backup, and launch approval requests stay connected.
Clients can see which access details are still missing before go-live.
Your team has one place to review launch-critical infrastructure details.
Practical questions
What is the difference between domain and hosting access?
Domain access controls registration and often DNS. Hosting access controls website files, database, backups, and server settings. They may be separate accounts.
Should I ask for DNS records?
Yes, especially before launch or migration. Email, verification, CDN, and app records can be easy to break accidentally.
What should be confirmed before launch?
Confirm DNS owner, hosting access, backups, SSL, CDN, email records, launch window, rollback process, and final approval owner.