# Custom domain connection worksheet

Use this worksheet to connect one client hostname to one identified website release. Replace every example with values shown by the actual hosting platform and authoritative DNS provider.

## 1. Connection brief

- Client:
- Website/project/space:
- Release or snapshot identifier:
- Current staging URL:
- Requested public hostname:
- Canonical public origin, including `https://`:
- Alternate hostname that should redirect to the canonical origin:
- Is this a new public launch or a move from an established public hostname?
- Planned change window:
- Agency change owner:
- Client approver:
- Rollback decision owner:

## 2. Ownership and access

| Area | Provider or account | Named owner | Renewal/billing owner | Change access confirmed? |
|---|---|---|---|---|
| Domain registration |  |  |  |  |
| Authoritative DNS |  |  |  |  |
| Website platform |  |  |  |  |
| Search Console |  |  |  |  |
| Analytics |  |  |  |  |
| OAuth or external integrations |  |  |  |  |

Do not record passwords, recovery codes, tokens, or secret values here.

## 3. Before-state DNS inventory

- Authoritative nameservers observed:
- DNS dashboard to be changed:
- Inventory captured at:
- Evidence location:

| Type | Host/name | Purpose | Current value recorded securely? | Preserve, replace, or investigate |
|---|---|---|---|---|
| A/AAAA/CNAME |  | Existing website route |  |  |
| MX |  | Mail delivery |  | Preserve unless mail owner approves a change |
| TXT |  | Verification, SPF, or other service |  | Investigate before changing |
| CNAME/TXT |  | DKIM or service verification |  | Investigate before changing |
| CAA |  | Certificate authority policy |  | Investigate before changing |
| Other |  |  |  |  |

## 4. Platform-provided record set

Copy these values from the current domain setup screen. Do not substitute a record from a tutorial or another project.

| Purpose | Type | Host/name exactly as provider expects it | Target/value | TTL | Proxy setting if applicable | Status |
|---|---|---|---|---|---|---|
| Ownership verification |  |  |  |  |  |  |
| Website route |  |  |  |  |  |  |
| Alternate hostname |  |  |  |  |  |  |
| Other |  |  |  |  |  |  |

Conflicting records reviewed:

- [ ] Same hostname and record purpose identified
- [ ] Unrelated mail and verification records preserved
- [ ] Full hostname versus short host entry checked
- [ ] Proxy setting follows the platform's current instruction
- [ ] Saved record values compared character for character with the platform screen

## 5. Verification log

| Stage | Evidence | Status | Checked by | Time | Retest trigger |
|---|---|---|---|---|---|
| Exact hostname added to website platform |  |  |  |  | Hostname edit |
| Ownership record visible in authoritative DNS |  |  |  |  | DNS edit |
| Route record visible in authoritative DNS |  |  |  |  | DNS edit |
| Platform reports ownership verified |  |  |  |  | Verification record edit |
| Platform reports route active |  |  |  |  | Route edit |
| TLS certificate is valid for the hostname |  |  |  |  | Certificate or DNS change |
| Canonical and alternate hostname behavior is correct |  |  |  |  | Redirect/config change |

## 6. Live acceptance tests

- [ ] Open the canonical `https://` homepage in a fresh browser session.
- [ ] Confirm the expected website and release loaded, not a default page or another project.
- [ ] Confirm there is no certificate warning and the certificate covers the hostname.
- [ ] Test both apex and `www` behavior if both are in scope.
- [ ] Follow primary navigation and open representative deep links.
- [ ] Submit one clearly labeled test through each business-critical form and confirm its approved destination.
- [ ] Check mobile and desktop layouts.
- [ ] Confirm internal links, canonical tags, sitemap URLs, social metadata, and generated links use the intended origin.
- [ ] Confirm OAuth callbacks, cookie scope, webhook allowlists, and external return URLs if the application uses them.
- [ ] Check analytics in the intended production property without treating one observed event as universal proof.
- [ ] Record the final ship, hold, or rollback decision with owner and time.

## 7. Migration branch, only when public URLs change

- Old public origin:
- New public origin:
- URL map location:
- Redirect owner:

- [ ] Each important old URL maps to a relevant new URL.
- [ ] Server-side permanent redirects are configured where appropriate.
- [ ] Redirect chains and loops are tested.
- [ ] Internal links and self-referencing canonicals use the new origin.
- [ ] Robots rules and migration-only `noindex` directives are reviewed.
- [ ] The sitemap uses the new canonical URLs.
- [ ] Old and new properties are verified in Search Console where applicable.
- [ ] Search Console Change of Address is evaluated only for an actual domain or subdomain move.
- [ ] Monitoring covers both old and new origins after launch.

## 8. Rollback and handoff

Rollback trigger:

Rollback action:

DNS values or route to restore:

Evidence to preserve before rollback:

Client handoff record:

- Domain registrant remains:
- Registrar renewal owner:
- DNS change authority:
- Website platform owner:
- Support contact:
- Emergency escalation contact:
- Date temporary access will be removed:
- Location of the completed connection record:

## Final decision

- Decision: Ship / Hold / Roll back
- Decision owner:
- Time:
- Known non-blocking items, owners, and due dates:
- Next production review:
