Website errors · 12 min read

Only One Website Won’t Load

Use the exact browser error to choose a sensible next step. Compare the same URL in another session and on another connection, without resetting a network that otherwise works.

Choose the website symptom in the free connection troubleshooter to log whether the same page fails in another browser and on mobile data.

Is it down or just me? When every other website works, that is the right question. Stay with the affected site and the action that fails. A front page, login and checkout can rely on different services.

If a checkout keeps spinning, check order history and payment confirmation before submitting again. Stop rage-refreshing while the transaction state is unclear. For browsing, copy the official URL and the exact error underneath the browser's headline. “This site can't be reached” is a category; the smaller code is the useful part.

Match the error to the next step

What you seeDo this nextWhat the result means
DNS_PROBE_FINISHED_NXDOMAINCheck the domain spelling. Compare the same domain on another connection.The requested name could not be resolved in that attempt.
ERR_CONNECTION_TIMED_OUTTry that URL on the same device over a trusted alternative connection.The expected connection response did not arrive in time.
403 Forbidden / access deniedSave the reference or ray ID and contact the site's support.A server or intermediary refused the request.
429 / too many requestsStop repeated attempts. Follow the stated retry instruction or service guidance.A rate limit was applied to the request.
500, 502 or 503Check official service notices and retry according to the service's advice.A server or gateway reported an error; save the full message.
Certificate / privacy warningCheck the intended domain and device clock.The secure connection needs attention before proceeding.
Page frame opens, then a blank area or login loopCompare a private session and another browser.Investigate the account flow, saved data, extensions or page dependencies.
Laptop and desktop monitor on a tidy desk beside a window
A laptop and monitor at a workstation. Retest the failing sign-in or page action in the comparison browser. Photo: Norbert Levajsics, via Wikimedia Commons, CC0 1.0 Universal. Licensed illustrative photograph; not a WireTrace installation or test. Resized and converted to WebP; original photograph retained.

Works in incognito? Keep the investigation in that browser

Paste the same address into a private window. Complete the same sign-in if the broken action requires it. If that works, check recently changed extensions and the affected site's stored data in the normal profile.

Before clearing data, save work and note that the action can remove a basket or sign you out. Chrome's cache-and-cookie guidance explains the deletion controls. Use the site's own saved-data controls where possible instead of wiping unrelated sessions. Extensions explicitly allowed in private mode can still run there.

If a fresh session gets the public page but loops after the same account signs in, tell support that. “Works in incognito” is incomplete if you have not retried the broken step.

Same URL, same device, different connection

First compare another device on home Wi-Fi, with cellular data off on a phone. If only the laptop fails, follow the laptop checks. Otherwise keep the original device and use mobile data or a trusted hotspot for the next attempt.

If it works on mobile data but fails on every home device, keep the error from home. A 403 on that connection gives the website a useful access-policy case to investigate. A DNS error calls for checking the lookup path. Approved family filtering, router policy and a configured VPN can also change access.

For example, a shop that opens over home Wi-Fi but denies only the account page needs the account URL, refusal code and reference ID. Buying mesh equipment would change none of those details.

When a website checker says the site is up

A server-side checker tests from its own location, usually without your account. “Site is up” may mean a public page answered from there. It does not finish your checkout from your home connection.

Browser-based checkers have an additional limit. A CORS restriction can prevent a script reading another site's response even though the page opens in a normal tab. A checker should distinguish an unreadable response from a confirmed outage.

For readers building a checker: Fetch with no-cors returns an opaque response. JavaScript cannot inspect its HTTP status in the normal way; a script-visible status of zero is not an HTTP outage code. Likewise, a failed ping is not a completed web-page test.

Stop changing a working network without a lead

If a DNS change did nothing, record that result and restore the previous supported configuration. The browser's secure DNS may also differ from the system resolver. Give support that detail rather than collecting more unrelated settings changes.

A denied login or cookie loop is not a bandwidth problem to solve with a faster package. A new router or cable tester is an unlikely purchase when the rest of the network works and the failure follows one account or session. If several business users are blocked, ask the responsible administrator to inspect the precise lookup, policy or request failure.

Send a report the site can investigate

  • The official domain and failing action: opening, signing in, downloading or paying.
  • The exact error, time and time zone, plus reference ID where shown.
  • Browser/version and whether the account was signed in.
  • Results in the private window, second device and alternative connection.
  • One change already tried and whether it helped.

Remove tokens and private query strings before sharing a URL publicly. After a correction, complete the original safe action. A page that was stuck on the loading screen after sign-in needs testing after sign-in again. If more sites start failing, switch to the wider browsing guide or troubleshooting hub. Our method notes explain what a WireTrace speed result can add to that report.

Keep your comparison record

Record restored, still failing or unable to test, then repeat the original task.

Download a blank record ↓Choose another symptom →

One failed website: errors, logins and checker results

Is it down or just me?

Check the official service status and compare the same URL on another connection. A public checker can add a different viewpoint, but it does not use your account or home route.

Why is a good speed test irrelevant to one failed login?

The speed service and login system are separate destinations and tasks. Follow the login error, session and account checks instead of using a throughput number as an all-clear.

The home page works but I am in a login loop. What next?

Retry that same account in a private session or another supported browser. If the loop follows the account, save the sign-in error and contact the service.

The checkout keeps spinning. Should I try again?

Check order history, confirmation email and payment status first. If the transaction state is unclear, contact the retailer before submitting another attempt.

It works in incognito. Is my extension definitely guilty?

Not yet. Private browsing also changes stored data and login state. Retry the same account action, then compare a relevant extension or that site's data one change at a time.

Should I clear all browsing data?

Start with the affected site's saved data where the browser allows it. Save local work and expect a new sign-in; unrelated sessions do not need deleting as a first step.

What does DNS_PROBE_FINISHED_NXDOMAIN mean?

The name could not be resolved for that request. Check the spelling and compare the same domain elsewhere. Note whether the browser uses secure DNS separately from the system.

What does ERR_CONNECTION_TIMED_OUT tell me?

The expected response did not arrive in time. Compare the same URL on another connection; the error does not name the failed router or service component.

What should I save with a 403 Forbidden error?

Keep the domain, time and displayed reference or ray ID. Give them to the website support team, along with whether another connection can reach the same account page.

What should I do with a 429 response?

Stop rapid retries and follow the page's retry instruction or official support guidance. Repeated refreshing can keep hitting the same limit.

Should I bypass a certificate warning?

Check the intended address and device clock first. If the warning remains, use the service or browser support route. A successful speed test does not validate that certificate.

Why is the site only broken on my laptop?

Compare another browser on that laptop, then its clock, VPN/proxy and relevant security settings. Confirm the successful phone was using the same Wi-Fi with mobile data off.

It works on mobile data. Does that prove the ISP blocked it?

No. The connection also changes routing, public address and potentially DNS or filtering. Keep the exact home-network error so the provider or site can investigate the right branch.

Can family filtering affect a single site?

Yes. Inspect the permitted filter or router policy with the account owner or administrator. A policy message is a stronger clue than guessing from a failed page alone.

Should I change DNS for every failed website?

No. Start with the actual error. A lookup failure, a 403 refusal and a login loop require different checks.

Why can a public DNS lookup disagree with my browser?

It may use another resolver, location or cached record. The browser can also have a separate secure-DNS setting. Keep those paths distinct when reporting results.

Can I type the site's IP instead of its domain?

That often changes the request and secure-hostname checks. Many sites share hosting and rely on the domain name, so use the official URL for a like-for-like browsing test.

Does a failed ping mean the website is down?

No. Ping and web requests use different protocols and can be handled differently. Test the official web address and preserve its actual browser error.

Why does a checker say site is up while I am blocked?

It may test a public page from a different location without your login. Give support your specific action and connection comparison rather than treating the two observations as identical.

Can CORS make a browser checker report a false outage?

Yes, if the checker treats an unreadable cross-origin response as a failed website. It should report the script's visibility limit separately from availability.

Does no-cors status zero mean the server returned an error?

No. An opaque Fetch response hides status and content from the script. Status zero in that situation is not a server's HTTP error response.

Why am I stuck on the loading screen after the page header?

A script, content service or account request may be failing. Compare a private session, then another browser, and note exactly which stage stops.

Why does a VPN make the site work?

It can change the public address, route and lookup or filtering context. Record that difference and ask the site or network administrator to inspect the specific failure.

Should I switch off antivirus or a work firewall?

Use the product's or administrator's supported troubleshooting process. Keep required work controls in place and supply the URL, error and comparison results.

Would a new router help an access denied login?

Start with the website's reference ID and account support. A refusal limited to one login is not a reason by itself to replace otherwise working network hardware.

The official status page shows no incident. What now?

Report your account, region or route-specific symptom to support. A clear general page does not inspect every user transaction.

My DNS change did nothing. What next?

Restore the previous supported setting if appropriate, note the unchanged error and return to the browser/device/connection result. Avoid adding another unrelated change without a new clue.

How do I confirm the single-site problem is fixed?

Try another browser or connection only as a comparison; finish by repeating the original action in the original setup. Check payment status before any repeat purchase.

Person holding a smartphone beside an open laptop at a wooden desk
A phone beside a laptop. Switching device and connection together changes two parts of the test. Photo: Alejandro Escamilla, via Wikimedia Commons, CC0 1.0 Universal. Licensed illustrative photograph; not a WireTrace installation or test. Resized and cropped for a landscape layout; original photograph retained.

Questions before you change anything

Why will only one website not load on my connection?

Compare the same URL, another browser, another device and a permitted alternative connection. Keep the exact error. One failing service with other sites working is a different starting point from a total outage.

How do I tell a website outage from my own network fault?

Check the publisher’s service-status page and compare a mobile-data test. Note time of failure and regional differences. A third-party outage checker is supporting context, not proof of the cause on your path.

Should I clear all cookies and saved passwords?

Start with a private window or clean browser profile. Check extension behaviour and site-specific data before a broad reset. Avoid deleting unrelated saved information when a narrower comparison can answer the question.

Why does the site work through a VPN but not directly?

The VPN can change DNS resolver, public address, network route and content-filter policy. That difference narrows the investigation; it does not identify which change made the site work. Use only an approved VPN.

Will a new router or cable tester fix one broken website?

First record name-resolution errors, certificate errors, HTTP status and browser network failures. Follow the branch shown by the evidence. Physical equipment is unlikely to be the first useful purchase for an isolated service problem.

Community scenarios behind these checks

Questions and source links reviewed 21 November 2026. The answers apply the limits described in this guide; they are not a test of your equipment.

Sources and scope

Photographs illustrate the context. Credits and the licence for each image appear in its caption. Our evidence policy · Commercial disclosure

Reader questions that informed this update: Reddit: reader discussion. Individual reports help identify questions; answers above use the technical references in this guide. One Reddit original post was deleted; only its displayed title and replies were available.

Details worth checking

What details distinguish a timeout from a certificate error or missing pictures?

Keep the exact hostname and error text. A timeout means an operation did not finish in time; it is not a diagnosis of DNS. A TLS certificate warning needs its own investigation and should not be bypassed. If text loads but images do not, record which part fails and compare the same page in another browser: its image host or a filtering rule may differ from the main page.

Explain your own result

Replace the brackets with observations you actually made. Leave unknowns as “not checked”. This draft is written for this guide; it is not a quotation or an automatic diagnosis.

Only [public URL/action] fails with [exact error]. Other sites work. Private window [result], same account in another browser [result], same device on a second connection [result]. Help me choose the site, account, browser or network support route. Do not treat the home page loading as proof the failed action works.

Copying stays on your device. Remove passwords, account numbers and private network details before sharing.

Reader questions that informed this update: Reddit: reader discussion. Individual reports help identify questions; answers above use the technical references in this guide. One Reddit original post was deleted; only its displayed title and replies were available.

Would a physical tool help here? Optional · commercial links

Commercial relationship: WireTrace UK is associated with Payverza, the seller. Advice uses listed capabilities, not independent product tests. An unsuitable task gets no product recommendation. How we work.