squirrelscan
GitHub

Home page fails to load: DNS, TLS, connection, timeout and 5xx

When the URL you audit does not load at all, squirrel reports it as a finding with the cause instead of only failing the run.

What this rule is for

If the home page does not load, nothing else about the site matters yet: visitors, search engines and AI agents all fail at the same point. Before this rule, an audit that could not fetch the site ended as a failed run with a reason, and nothing appeared in the findings. Anything that works from findings, such as alerts, diffs and the issue list, never saw “the site is down”. This rule turns the crawler’s record of why the entry URL failed into one finding.

What squirrel checks

The rule is site-wide. It fires when the crawl recorded a failure fetching the audited URL (the seed) and the failure is one of:

  • DNS: the domain name did not resolve.
  • TLS: the TLS connection failed, for example an expired or mismatched certificate.
  • Connection: the connection was refused or dropped.
  • Timeout: the server did not answer in time, even on the second, longer attempt.
  • 5xx: the server answered with a server error.

It does not fire when the home page loaded, and it does not report a 4xx answer, a robots.txt refusal, a redirect problem or a bot wall: those are answers, often a policy, and the report covers them separately. A failure fetching only a sitemap is not the home page and is ignored. The check is home-page-unreachable with status fail, and its message names the host and the cause.

The check passes only when this audit fetched the home page (the audited URL, or where it redirected) and it loaded. When the audit has no result for the home page either way, the check is skipped as not checked, with the reason entry-not-fetched, and a finding from an earlier audit stays open. That happens when the home page was not among the pages fetched (a partial re-audit, or squirrel analyze on stored data without the crawl’s record of failures), when it answered with an error status but no failure was recorded, and when the failure was of a kind squirrel could not classify.

How to fix it

Check the cause named in the finding, then run the audit again.

  • DNS: confirm the domain’s records and nameservers.
  • TLS: check the certificate’s expiry, chain and hostname.
  • Connection or timeout: check the server, firewall and CDN origin.
  • 5xx: read the origin’s error logs.
Rule IDcrawl/home-page-unreachable
CategoryCrawlability
ScopeSite-wide
Severityerror
Weight10/10

Enable / disable

Disable this rule

[rules]
disable = ["crawl/home-page-unreachable"]

Disable all Crawlability rules

[rules]
disable = ["crawl/*"]

Enable only this rule

[rules]
enable = ["crawl/home-page-unreachable"]

enable replaces the default ["*"], so this is the only rule selected. Leave disable out: a rule that matches any disable pattern is skipped even when enable names it. Only an enabled setting under a rule’s own [rule_options] table overrides both lists.

Check names by outcome

Each check name this rule can emit, by what it means to a tool comparing two audits. A problem check is a finding. A clean check says the rule ran over what it covers and found nothing; it clears the problem checks listed beside it, so a finding is fixed when the rule ran over the same scope and a clean check took its place. A not checked check says the rule did not evaluate, and never clears a finding.

Check nameOutcomeClears
home-page-unreachableProblem
home-page-unreachableCleanhome-page-unreachable
home-page-unreachableNot checked

References

Check your site

Run squirrel audit https://example.com. When the home page fails to load, the Crawlability section names the cause. Signed-out local audits need no account and cost nothing. Signed-in audits spend credits.

Type to search…

↑↓ navigate↵ openesc close