Check My Network

The Scan tab runs a one-shot audit of your current network: gateway, WiFi environment, DNS, services, and (for Deep Scans) traceroute, security posture, firmware, and UPnP exposure. Results land in the Insights tab as a prioritized list.

How to run a scan

1. Click Scan in the left sidebar.
2. The card at the top shows the network you're about to scan: WiFi name (SSID), security, channel, plus the gateway vendor and model when known.
3. Choose Quick Scan or Deep Scan with the toggle. Deep Scan adds about 3 seconds and runs additional security and routing checks.
4. Click Start Scan (or Start Deep Scan). The disclaimer below the button is a reminder that you should only scan networks you're authorized to scan.

While the scan runs, you'll see a checklist that fills in as each step completes:

Quick Scan checks:

• Gateway detection
• WiFi environment analysis
• DNS health check
• Service endpoint probes

Deep Scan adds:

• Traceroute path analysis
• Security assessment
• Firmware version check
• UPnP/NAT-PMP audit

When the scan finishes, you'll see a green check, the network name, and a count of issues found. Click View Findings to jump to the Insights tab, or Scan Again to re-run.

Scan history

Below the controls, the Scan tab keeps a list of recent scans. Each row shows when the scan ran, whether it was Quick or Deep, how long it took, and how many issues turned up — broken down by critical (red), warning (yellow), and info (blue). Click a row with findings to jump straight to the Insights tab; Clear history at the bottom wipes the list.

The Insights tab

The Insights tab is where findings live. Each finding has:

• A severity (critical, warning, info)
• A scope — does it affect just this PC, the whole network, or one peer device?
• A short summary of what was detected
• A What to do section with specific remediation steps

The sidebar badge on the Insights tab shows the unresolved count, so you always know how many things are waiting on you.

You can archive a finding if it's not actionable (e.g., a deliberately old IoT device that can't go faster), accept it onto your TODO list, or mark fixed so the next scan validates that the fix actually worked.

Finding lifecycle (Archive / Accept / Mark Fixed) and the scope filter are part of the 1.2.x sprint. Some controls may land incrementally; the underlying findings always show.

What gets graded

After a scan, the Status tab also surfaces network fitness grades for common use cases:

Email & Browsing mostly needs steady download and tolerable latency. Marginal or worse usually means a saturated link.

Video Conferencing (Zoom, Teams, Meet) is the pickiest — needs decent speed both ways, low latency, low jitter, low packet loss, and good bufferbloat behavior. If your network has a weak spot, video calls usually expose it first.

Gaming cares about latency, jitter, and bufferbloat more than raw speed. A gigabit connection still gets Marginal if your router can't handle load.

Streaming mostly needs steady download. Ready means 4K with no buffering.

Each grade tells you which metric was the limiting factor, so you know what to fix.

Sharing a scan

After a scan, you can copy a summary or full results to your clipboard. This is handy when you call your ISP — instead of "my internet is slow," paste the report and they have something to dig into.

Per-scan export to JSON is on the Windows roadmap; today the Insights view supports text copy.

Good times to run a scan

• Before a big meeting or call
• When things feel slow and you want proof
• While talking to your ISP about a problem
• After you change WiFi settings, swap a router, or move your gear

A few tips

Close big downloads or streaming before the test. The probes measure what's available; other traffic eats into that.

Run scans at different times of day. Networks slow down during peak hours, especially in the evening.

If grades swing a lot between scans, that's a clue. It usually means congestion or an unstable connection rather than a single broken hop.