The Methodology of Network Hub

A professional-grade Synthetic Monitoring tool designed for Real-User Measurement (RUM) and Application Layer analysis.

Zero Proxy

The monitoring is performed directly from your hardware, eliminating server-side bias.

Privacy First

No data is sent to external servers. Your host list and history stay in your browser's LocalStorage.

L7 Analysis

Focuses on Application Layer health rather than simple ICMP network pings.

Deep Dive: How it Works

Most network tools use ICMP (Internet Control Message Protocol). While ICMP is great for checking if hardware is active, it fails to diagnose if the web service (Nginx, Apache, IIS) is actually responding to requests.

The "Experience Loop"

Our tool uses the JavaScript fetch() API to simulate a real browser request. The latency you see includes:

DNS Resolution: Converting domain names to IP addresses.
Handshake Latency: The time required to establish a secure TCP/TLS connection.
Server Processing: The time the remote CPU takes to generate a response (TTFB).

Standard Ping vs. Network Hub

In a standard CMD terminal, a ping might show 15ms. In Network Hub, you might see 120ms. This discrepancy exists because a standard ping only measures the round-trip of a tiny 32-byte packet at the kernel level, whereas Network Hub measures the complete application readiness.

Protocol Restrictions (HTTP vs HTTPS)

Due to modern browser security policies (Mixed Content Blocking), the environment in which you run this tool matters significantly.

The HTTPS Barrier

If you access this dashboard via https://yourdomain.com, your browser strictly forbids requests to http:// (insecure) addresses or raw IP addresses without SSL.

Symptoms: Nodes will instantly show as Offline or Insecure/Blocked in the history hint.

How to Monitor HTTP or Local Devices?

To monitor local IP addresses (like 192.168.1.1), printers, or internal dev servers without SSL, you have two professional options:

Local Deployment (Recommended): Download the tool as a standalone HTML file and run it from your computer. Browsers treat file:/// access with fewer protocol restrictions.
Non-SSL Hosting: Host the dashboard on a simple http:// (non-encrypted) server. This allows the browser to "ping" both HTTP and HTTPS targets.

Status & Error Dictionary

Visual	Technical Code	Detailed Interpretation
Online	`OK`	Successful response. The service is up and serving data.
Offline	`Timed Out`	No response within 4000ms. Usually indicates a dropped packet, dead server, or a strict firewall.
Warning	`Reached`	The server responded, but the request was unsuccessful (e.g., 404, 403, or 500 errors). The host is alive, but the app has issues.
Offline	`Refused`	The remote host actively rejected the connection. Often caused by CORS policies or the target port being closed.
Offline	`Blocked`	Browser security blocked the request (Mixed Content or Ad-blocker interference).
Pending	`Pending`	The check is currently in queue or waiting for its turn in the execution cycle.

Offline Enterprise Access

Need to monitor a Local Area Network (LAN) or use the tool without a web server? Download the main dashboard as a single portable file.

This will download the index.php content as an offline-ready HTML file.

Frequently Asked Questions

Why does it say "Detecting DNS"?

The system queries a public EDNS resolver to identify which DNS server your browser is currently using. This helps diagnose if your ISP is hijacking your traffic or if you are properly routed through your preferred DNS (like 1.1.1.1).

How accurate is the Sparkline?

The sparkline records the last 60 checks. It is highly accurate for spotting "Micro-outages" — moments where a server stays online but experiences massive lag spikes for a few seconds.

Can I import my server list on another PC?

Yes. Use the Export button in the settings menu to save a .json backup, then use Import on the new machine. All names, URLs, and descriptions will be restored.