Website is not loading
Separate DNS, server, IPv4/IPv6 and application failures.
Run the focused checkWebsite & Domain Troubleshooting Tools
Find out why your website or email is not working
Enter one domain. HostWithShery checks the public DNS, website, HTTPS, redirects and business-email configuration, connects the evidence, and puts the most useful next action first.
FreeNo accountPrivate temporary reportsFacts separated from likely causes
Start from the symptom
What are you trying to fix?
Choose the problem you can actually see. You do not need to know whether DNS, SSL or the server is responsible yet.
Business email stopped
Check mail routing and authentication without changing working web records.
Run the focused checkSSL or secure-connection error
Check certificate trust, expiry, hostname coverage and HTTPS behavior.
Run the focused checkRedirect or wrong destination
Follow every hop and find where scheme, hostname or destination changes.
Run the focused checkDiagnosis, not data dumping
The result should tell you what matters before showing raw records.
1Observe the public configuration
DNS, HTTP, TLS, mail and crawler checks collect independent evidence without requiring account access.
2Connect related failures
A working A record does not cancel a broken AAAA record, and a valid certificate does not cancel a redirect loop. Related signals are interpreted together.
3Change the smallest proven layer
The report links to the relevant provider or repair path and tells you how to verify the same evidence after the change.
Core diagnostic areas
View all areas →Use a focused tool when you already know the layer
DNS
Records, nameservers, propagation, DNSSEC, CAA and IPv6.
SSL & HTTPS
Certificate validity, expiry, hostname coverage and mixed content.
Business email
MX routing, SPF, DKIM, DMARC and transport policy.
HTTP & redirects
Status codes, redirect chains, headers and bulk URL checks.
Hosting signals
Public network, CDN, ASN, CMS and domain registration evidence.
Crawler access
robots.txt, sitemap and canonical accessibility checks.
Exact browser, runtime and proxy errors
All error guides →Use the message you see as the starting point
NSURLErrorCannotFindHost (-1003)Apple networking could not resolve the hostname in the requested URL. The failure occurs before an HTTP response can be received, so start with the exact hostname and its DNS path.Diagnose this error →EAI_NONAME / getaddrinfo Hostname ErrorThe operating-system name-resolution call could not translate the supplied node or hostname into an address. In Node.js this can surface through dns.lookup() or APIs that use the system getaddrinfo path.Diagnose this error →NS_ERROR_UNKNOWN_HOSTFirefox networking reports NS_ERROR_UNKNOWN_HOST when lookup of the hostname fails. Treat it as a name-resolution symptom first, not as an SSL, redirect or application-response error.Diagnose this error →DNS_PROBE_FINISHED_NXDOMAINThe browser could not obtain a DNS answer for the requested hostname.Diagnose this error →ERR_TOO_MANY_REDIRECTSThe browser detected a redirect loop and stopped following the chain.Diagnose this error →Cloudflare Error 522Cloudflare timed out while trying to communicate with the origin server.Diagnose this error →
Symptom-first repair guides
Browse all guides →Start with what changed, not a guessed technical layer
Nameserver moves, migrations, root/www mismatches, mail failures and indexing problems each have a different evidence path.
Website stopped working after DNS changeA DNS change can send visitors to the wrong server, remove a required record or expose a broken IPv6 endpoint.Open repair guide →Website works for me but not othersDifferent DNS caches, IPv4/IPv6 paths or regional routing can make the same domain behave differently for different visitors.Open repair guide →Website works but email does notThe website can be healthy while MX, SPF, DKIM or mail-host resolution is missing or wrong.Open repair guide →Sitemap submitted but pages are not indexedA successful XML sitemap helps search engines discover preferred URLs, but sitemap submission does not guarantee crawling or indexing. First confirm that important pages are internally linked, crawlable, self-canonical and return useful indexable content.Open repair guide →Website works without www but not with wwwThe www hostname usually has a missing/wrong DNS record, is not attached to the hosting platform, or is not covered by the certificate.Open repair guide →New website not showing after migrationA hosting migration can be complete while public DNS still points to the previous server.Open repair guide →
Provider-specific repair paths
Browse provider guides →The same technical failure can require different control-panel steps.
Not sure where to start?
Check my websiteUse the complete health check.
It is the fastest path when the symptom is unclear because it checks website, DNS, HTTPS, redirects and business email together.