noshost
HTTP5 min read· Updated

Investigate a 403, 404, 502 or 504 website response

Record the exact URL, status and time before changing anything. A successful connection can still return an error page, and a firewall can reject a checker while allowing a browser.

Read the response for the affected URLCapture its final status and headers before deciding what to change.
Open HTTP Status Checker
On this page

    1. Follow the request

    Run HTTP Status Checker, then Redirect Checker if the URL moves. Check the final URL rather than assuming the first address served the error. HTTP Header Viewer helps identify the responding server or CDN, although headers alone do not prove who caused the failure.

    2. Match the status to a useful investigation

    • 403: review access rules, authentication and bot protection. Compare the same request in your browser and in server logs.
    • 404: confirm the path and routing. Redirect a genuinely moved page to its replacement; do not send every missing path to Home.
    • 502: inspect the gateway's upstream connection and application service. A gateway error is not proof of a DNS fault.
    • 504: compare gateway timeout settings with application and database timings. Avoid simply raising timeouts before finding the slow operation.

    3. Compare scope and time

    A result from NosHost describes our server's request. Try the exact hostname from another connection and compare the measurement time. Check DNS and TLS when no HTTP response arrives. Use cache headers to investigate stale responses.

    Confirm the repair

    After a targeted change, repeat the same URL and check the application in a browser. Keep the prior configuration so a failed change can be rolled back.

    Sources

    Reviewed by NosHost on 26 October 2026. HTTP response status reference · Cloudflare 524 guidance.

    Use the linked tools to confirm each change, then repeat the original test. Review server or DNS changes before applying them to a live site.

    Spotted something out of date? Email [email protected].

    More guides

    Technical SEO5 min read

    Crawling versus indexing

    Check response directives and discovery, then consult the search engine’s recorded indexing reason.

    Email5 min read

    Set up email DNS

    Separate receiving records from sending authentication and verify every legitimate sender.

    Network5 min read

    Why a port check says closed

    Trace the connection path without disabling the firewall or treating a TCP result as a UDP test.

    Redirects7 min read

    Fix ERR_TOO_MANY_REDIRECTS

    The usual causes are a CDN in Flexible SSL mode, a wrong site address in your CMS or two rules that disagree about www.

    Email9 min read

    Emails going to spam

    Read receiving-server headers, check authentication and alignment, then investigate reputation and recipient signals.

    DNS6 min read

    DNS change not showing up

    Compare authoritative records and resolver caches to investigate a DNS change that has not appeared.

    Server config6 min read

    Cron job not running

    Check paths, environment variables, permissions, logging and time zones in a cron job that is not running.

    ↑ ↓ moveEnter openEsc close

    Expanded view