Name the symptom without naming the cause
You open a service and the page does not load. That observation alone does not establish a stolen password, a virus on the laptop or an attack on the host. Write down the address, the approximate time and the message shown. Avoid entering credentials into a replacement page suggested by an unsolicited message. A useful first record says what failed and what still worked; it does not turn an unexplained symptom into a confident diagnosis.
Check the service through a known route
Use a saved, trusted address to reach the provider’s status information or support instructions. If practical, check whether the same public page fails on another connection. Record the result without repeatedly refreshing a failing service. A public outage report can support an explanation, but its absence does not prove that your device is at fault. If other services work normally, that is another observation to pass to support, not a reason to install an unfamiliar repair tool.
Handle account concerns separately
Unexpected account changes or a login notification you cannot explain deserve attention through the service’s official account-recovery process. OWASP’s guidance for developers describes reset tokens that expire and can be used only once; as a user, treat such recovery messages as sensitive and do not forward them casually. An unavailable website and a compromised account can occur independently. Keep the account-recovery steps separate from the availability investigation so that one problem does not obscure the other.
Know which layer a protection service covers
For a website owner, traffic-related availability may lead to a discussion of website DDoS protection, such as the services described by KoDDoS. That is a hosting and network decision, distinct from protecting a personal device or recovering an account. Ask the host what evidence it needs before deciding on a response. Buying a new antivirus subscription will not by itself resolve an overloaded public service, and adding network protection does not replace sensible account controls.
Send a small, useful incident report
Include the affected public address, time and time zone, visible error and checks already completed. Do not attach passwords, recovery codes or a full browser export. If a screenshot contains account or personal information, redact what support does not need. Keep the case reference and the provider’s next requested action. When access returns, repeat the original task and note the result; a page loading again is useful evidence, but it does not explain the original cause.
Put it into practice
| Observation | Useful next step |
|---|---|
| Public page does not load | Record the error and check the official service-status route. |
| Unexpected account change | Use the official account-security or recovery process. |
| Device reports a threat | Follow the installed security product’s documented instructions. |
More than one issue can exist at once. These are reporting categories, not diagnoses.
Sources & further reading
Examples and worksheets on this page are illustrative. Documentation links were checked in November 2026; follow the relevant product’s current instructions.
