Expected result documented and verified from the affected user path.
Pass / fail / blockedTroubleshooting guide
Domain still shows the old website
The cause is usually authority, record mismatch, proxy cache, application redirect or local cache—not a mysterious universal propagation timer.
4 diagnostic facts3 controlled stages4 acceptance checks1 primary references
Diagnose before changing
- 01Query delegated nameservers
- 02Query authoritative A/AAAA/CNAME
- 03Compare root and www
- 04Check CDN proxy and redirects
- 01
Locate the wrong answer
Test the authoritative server, public resolvers and the affected device separately.
- 02
Remove conflicts carefully
Correct only records proven wrong; an old AAAA can send IPv6 users elsewhere.
- 03
Verify application identity
Check canonical URL, WordPress home/site URL, redirects and virtual-host domain mapping.
Acceptance gate
Prove the result
Record timestamp, tester and evidence for every check before closing the incident or change.
Expected result documented and verified from the affected user path.
Pass / fail / blockedExpected result documented and verified from the affected user path.
Pass / fail / blockedExpected result documented and verified from the affected user path.
Pass / fail / blockedPrimary references