Verify the DNS and hosting attachment for each name
Write down every hostname visitors use, including the root domain and any `www` or service subdomain. Check that each one resolves to the intended hosting destination and is attached to the project that contains the expected deployment. A DNS record can be valid yet point to a different project or an old destination.
Review the exact host configured in the hosting project and confirm whether both names are attached or whether one should redirect to the other. Check for conflicting or stale DNS records and make sure a change was made in the authoritative zone. Do not assume that attaching the root domain automatically configures every subdomain.
Test certificates and redirects independently
Open each hostname directly and check whether it presents the expected site and a valid secure connection. If one address fails while another works, inspect certificate coverage and redirect behavior for the failing name. A certificate or redirect issue can affect only one hostname even when the deployment itself is healthy.
After changing DNS or project attachment, allow cached answers to update and verify from another network. Keep a record of the intended canonical hostname and the redirect direction so the two names do not send visitors in a loop. If the issue persists, provide the exact hostname and observed response for each address when investigating.