DEV Community

Bryz︱🦾
Bryz︱🦾

Posted on

🌐 "This Website Is Broken!" Test an InPrivate Window Before You Escalate

#itsupport #windows #beginners #troubleshooting

"The website is down!" 😩 It's one of the most common help desk tickets out there. But a lot of the time the website is fine. The problem lives inside the user's browser.

Here's a quick routine that tells you in about two minutes whether it's the browser, the device, or something bigger. ⚡

🔍 Step 1: Try an InPrivate / Incognito window

A private window starts without the user's saved cookies and cache, and most extensions stay off by default.

  • Edge: Ctrl + Shift + N
  • Chrome: Ctrl + Shift + N
  • Firefox: Ctrl + Shift + P

You can also launch one from the Run box (Win + R):

msedge --inprivate https://example.com
chrome --incognito https://example.com
Enter fullscreen mode Exit fullscreen mode

✅ Site works in private mode? The problem is almost always cached data, a bad cookie, or an extension in the normal profile.

❌ Still broken? Skip to Step 3.

🍪 Step 2: Clear that site's data (not everything!)

Wiping the whole browser history signs the user out of everything, and they won't thank you for it. Target just the problem site:

  1. Click the padlock / site info icon next to the address bar.
  2. Open Cookies and site data (Edge) or Site settings (Chrome).
  3. Remove the data for that site, then reload with Ctrl + F5.

Still acting up? Check extensions:

edge://extensions
chrome://extensions
Enter fullscreen mode Exit fullscreen mode

Turn them off one at a time and retest. Ad blockers and old password managers are frequent culprits. 🧩

🖥️ Step 3: Widen the test

If private mode failed too, find out how far the problem reaches:

  • Try a different browser on the same PC.
  • Try the same site on another device (or a phone on cellular data).
  • Check name resolution and connectivity from PowerShell: 
Resolve-DnsName example.com
Test-NetConnection example.com -Port 443
Enter fullscreen mode Exit fullscreen mode

If DNS fails or port 443 can't connect, you're looking at a network, DNS, proxy, or VPN issue, not a browser one. 🌐

🎯 Why this matters

Those few tests tell you who should own the ticket:

Result Likely cause
Works in InPrivate Cache, cookies, or extension
Fails in every browser on one PC Device, proxy, or local network setting
Fails on every device Network, DNS, or the site itself

Write down what you tested in the ticket notes. If you need to escalate, the next tier won't have to start from zero. 📝

What's your first move when a user says a site won't load? Drop it in the comments 👇

Top comments (0)