Separating a DNS failure from an application error
Record where a request failed before describing it as a website application error. A request that never obtained an HTTP response needs a different investigation from one that received an error page.
Keep the failure stage visible
Save the exact URL, time, error text and whether any HTTP status or response body was received. Compare a second controlled request and note the network context. Avoid converting every tool failure into an invented500 status. If a tool reports a name-resolution problem, preserve that wording rather than replacing it with a general site-down label.
Hand off the right evidence
Ask the responsible operator to check the relevant domain configuration and service availability using the recorded time and hostname. If an HTTP response is available on a later attempt, keep it as a separate observation. Do not infer that Google experienced the same failure merely because your local request did. Verify the intended page after the underlying issue is addressed.
Source guidance
Use the website analyzer to collect a starting set of observations, then verify the specific evidence described above.Frequently Asked Questions
What if one tool fails and another succeeds?
Keep both results and their conditions. The discrepancy narrows the investigation; it does not by itself identify which network component caused the problem.
What should the handoff record include?
Include the exact URL, observation time, request conditions, captured result and intended behavior. Keep a separate after-change observation so the repair can be checked against the original defect.