# Parking-page repair worksheet (English, editable)

Use one copy per failing hostname. Record observations before changing nameservers, DNS records or site assignments. The website owner and DNS owner should approve the specific change.

Before sharing this worksheet or screenshots, remove ticket or access tokens from URL query strings and redact attendee details. Keep the hostname and route needed for diagnosis.

| Evidence | Observed value / link / time | Owner or next check |
| --- | --- | --- |
| Exact failing URL (including `www` or subdomain) |  |  |
| Network/device and time zone |  |  |
| Final URL after any redirect |  |  |
| Visible default-page title/branding and screenshot |  |  |
| Does apex work? Does `www` work? |  |  |
| Last approved DNS, domain or hosting change |  |  |
| Registrar nameservers currently delegated |  |  |
| Intended authoritative zone nameservers |  |  |
| Authoritative answer for exact hostname and record type |  |  |
| Expected target from **this site's** hosting dashboard |  |  |
| Unexpected parking, wildcard or former-host record? |  |  |
| Exact hostname assigned to intended published site? |  |  |
| Host verification/conflict status |  |  |
| Approved single change and previous value |  |  |
| Rollback owner and condition |  |  |

## Visitor release check

| Published check | URL, result and time | Reviewer |
| --- | --- | --- |
| Exact HTTPS URL in a fresh browser |  |  |
| Same URL from a second network |  |  |
| Apex and `www` separately |  |  |
| Event date and venue readable as text |  |  |
| Ticket/registration destination reached |  |  |
| Temporary attendee route still needed? |  |  |

Do not equate a correct DNS answer with a working ticket journey. If one network still sees an old page, compare its DNS answer and the **previous** TTL before changing anything else. Keep mail and unrelated verification records outside the repair unless their owner confirms a separate issue.