Website Not Loading? Diagnose DNS, HTTPS and HTTP
A practical guide to understanding the evidence before changing your domain configuration.
1. Start with the exact symptom
Does the hostname fail to resolve, does the connection time out, or does the server return a 4xx/5xx response? These are different problems. Test the exact address, including whether it starts with www.
2. Verify public DNS
Check A/AAAA and CNAME records and whether answers match the intended hosting provider. Missing records or incorrect addresses can prevent connections. A record existing does not prove the website is healthy.
3. Inspect HTTPS separately from HTTP
A successful HTTPS response and an HTTP timeout can coexist. HTTP might be intentionally disabled. A 301/302 is a redirect, not proof that the final page works; follow and check its final destination.
4. Check from another network
A single probe can be blocked by geography, bot mitigation or routing. Compare an independent browser or monitoring location and your hosting logs.
5. Make and verify one change at a time
Confirm ownership and the intended configuration first. Recheck after a change, keeping DNS TTL and cache effects in mind.
Scope: public checks only. This guide does not establish email delivery, end-to-end uptime or complete security.