◈ netchecks.org

17 checks · no account · self-hosted

Test your network in one click

17 free network diagnostic tools in one dashboard.

FAQ

0 trackers · 14 languages · dark & light mode · self-hosted

← All articles

Network history

The Genesis of WiFi: From 2 Mbps to Multi-Gigabit, Generation by Generation

WiFi is the one piece of network infrastructure almost nobody thinks about until it stops working - which is exactly the sign of a technology that succeeded. It did not arrive fully formed: the wireless LAN standard went through nearly three decades of generational leaps, each one solving a specific, concrete limitation of the one before it, before it became fast and reliable enough to replace the Ethernet cable entirely for most devices.

Understanding that generational history is more than trivia - it explains why an older device on a network can drag down everyone else's speed, why 5 GHz and 2.4 GHz behave so differently, and why 'WiFi' as a marketing name only appeared years after the underlying standard did.

  1. 1985

    The ISM band is deregulated

    The US FCC opens the 2.4 GHz industrial/scientific/medical band for unlicensed use, the regulatory precondition that made consumer wireless networking possible at all.

  2. 1997

    802.11-1997, the original standard

    The IEEE ratifies the first WiFi standard: up to 2 Mbps, using either infrared or radio in the 2.4 GHz band - technically functional, but too slow and unreliable for real adoption.

  3. 1999

    802.11b and 802.11a

    802.11b reaches 11 Mbps on 2.4 GHz and becomes the first commercially successful version; 802.11a reaches 54 Mbps on the cleaner but shorter-range 5 GHz band the same year.

  4. 1999

    The Wi-Fi Alliance forms

    Equipment vendors create the Wi-Fi Alliance to certify interoperability and coin the consumer-friendly 'Wi-Fi' brand name for what had until then only been known by its IEEE number.

  5. 2003

    802.11g

    Brings 802.11a's 54 Mbps speed to the more common, longer-range 2.4 GHz band, while staying backward-compatible with 802.11b devices - the version that made home WiFi mainstream.

  6. 2003

    WPA replaces WEP

    Wi-Fi Protected Access is introduced after WEP's encryption is publicly broken, followed by the stronger WPA2 (with AES) in 2004.

  7. 2009

    802.11n (WiFi 4)

    Introduces MIMO (multiple antennas transmitting simultaneously) and dual-band 2.4/5 GHz operation, pushing real-world throughput past 100 Mbps for the first time.

  8. 2013

    802.11ac (WiFi 5)

    Moves exclusively to 5 GHz with wider channels and MU-MIMO, crossing the 1 Gbps threshold and finally rivaling wired Gigabit Ethernet.

  9. 2019

    802.11ax (WiFi 6)

    Adds OFDMA (splitting a channel efficiently among many simultaneous devices) and target wake time, designed specifically for dense environments with dozens of connected devices, not just raw speed.

  10. 2024

    802.11be (WiFi 7)

    Introduces the 6 GHz band alongside 2.4/5 GHz, 320 MHz channels, and multi-link operation (using several bands simultaneously for one connection), aiming past 40 Gbps theoretical throughput.

A slow, awkward start

The very first WiFi standard, ratified in 1997, is barely recognizable next to what runs in a modern router. Capped at 2 Mbps and split between an infrared option and an early 2.4 GHz radio option that few vendors implemented compatibly with each other, it was a proof of concept more than a product - genuinely usable wireless networking would need two more years and a second generation of hardware.

That second generation arrived in 1999 as a fork in the road: 802.11b, cheap and long-range on the crowded 2.4 GHz band at 11 Mbps, and 802.11a, faster at 54 Mbps but confined to the higher-frequency 5 GHz band with shorter range and higher cost. 802.11b's price advantage won the consumer market first, which is also why 2.4 GHz networks became so congested for the next two decades - every microwave oven, cordless phone, and Bluetooth device shares that same unlicensed band.

The generation that made WiFi normal

802.11g, standardized in 2003, is arguably the single most consequential release in WiFi's history: it brought 802.11a's 54 Mbps speed onto the more practical 2.4 GHz band, while remaining backward-compatible with the already-installed base of 802.11b devices. That combination of speed, range, and compatibility is what took wireless networking from a business novelty to a default feature of every home router sold from that point forward.

Security caught up the same year. The original WEP encryption scheme had been publicly and thoroughly broken by cryptographers, so the Wi-Fi Alliance rushed out WPA as an interim fix, followed a year later by WPA2 with proper AES encryption - the baseline every legitimate network still uses today, ahead of WPA3's further hardening in 2018.

2.4 GHz offers longer range but only a few non-overlapping channels shared with many other devices; 5 GHz and 6 GHz trade range for far more clean spectrum and dramatically higher throughput.

From one speed to many devices: 802.11n, ac, and ax

802.11n in 2009 is where WiFi stopped being a single radio talking to a single other radio and started being a genuinely multi-antenna system: MIMO (Multiple Input, Multiple Output) uses several antennas to send and receive multiple data streams simultaneously over the same channel, and dual-band operation let a router serve both 2.4 and 5 GHz networks at once for the first time.

802.11ac in 2013 pushed that further with wider 80/160 MHz channels and MU-MIMO (serving several client devices' separate data streams truly simultaneously instead of only one at a time), crossing the symbolic 1 Gbps mark and making WiFi genuinely competitive with wired Gigabit Ethernet for the first time.

802.11ax (WiFi 6) in 2019 is a deliberate change in priorities: instead of chasing peak theoretical speed, it targets the real bottleneck of a modern home or office - dozens of simultaneously connected phones, laptops, and IoT devices. OFDMA slices a channel efficiently between many low-bandwidth devices at once instead of making them each wait their turn, and Target Wake Time lets battery-powered devices negotiate exactly when to check in, extending battery life significantly.

Peak theoretical throughput by generation - each jump reflects a specific technical addition (MIMO, wider channels, MU-MIMO, OFDMA), not simply 'a faster radio'.

Where WiFi 7 takes it next

802.11be (WiFi 7), finalized in 2024, adds an entirely new band - 6 GHz, opened for unlicensed use in most regions only a few years earlier - on top of the existing 2.4 and 5 GHz bands, plus far wider 320 MHz channels. Its most novel feature is Multi-Link Operation: a single device can now use more than one band simultaneously for one connection, dynamically shifting traffic to whichever band has the least congestion at that instant, something no previous generation could do.

Each generation's story is the same pattern repeating: solve interoperability first (802.11-1997), then cost and range (b), then mainstream speed and compatibility (g), then genuine multi-antenna throughput (n, ac), then density and efficiency for dozens of devices (ax), then multi-band flexibility (be). None of it was a single breakthrough - it was three decades of incremental engineering against real, measurable bottlenecks.

The takeaway

The practical takeaway for anyone running a network today: a WiFi network's real-world speed is set by its oldest connected device far more than by its newest router, since older generations force the whole network to fall back to slower, more compatible modes in mixed environments. Understanding which generation a device speaks - and which band it's actually using - explains most of the 'why is my WiFi slow' questions this toolkit's Speed Test and My IP tools get asked to help answer.

← All articles

My IP Check

Your public IP address and network location, detected automatically.

Loads automatically when you open NetChecks — no input needed. Use the Refresh button to re-check after switching networks or reconnecting your VPN.

Your browser

All-in-One Scan

Runs every relevant check against one IP or hostname in a single pass: DNS, whois, ping, traceroute, a well-known-ports scan (1-1024), HTTP headers and the SSL certificate.

Enter a domain or IP address and run it to check DNS, whois, ping, traceroute, common ports, HTTP headers, and the SSL certificate all at once.

Most checks run in parallel - typically finishes in about 30 seconds, longer if the target is slow or unreachable.

The port scan step only runs once the consent checkbox above is checked - every other check runs regardless.

Ping

Send ICMP echo requests to a host to check reachability and latency.

Enter a hostname or IP address and press Ping to send ICMP echo requests and measure round-trip latency.

You Host ICMP Echo Request (type 8) ICMP Echo Reply (type 0) measures: RTT · TTL · packet loss

      

Learn more about Ping

What it is

Ping sends ICMP Echo Request packets to a host and measures how long it takes for ICMP Echo Reply packets to come back. It is the most basic network connectivity test there is: it answers exactly one question, "is this machine reachable, and how quickly?" The ICMP protocol (RFC 792) was designed back in 1981 specifically to carry control and diagnostic messages over IP networks, outside of any application traffic - Ping is its best-known and most universally available implementation, present on virtually every operating system and network device since their earliest versions.

How it works

Every ICMP packet carries a TTL (Time To Live) field decremented by one at each router it crosses; if it hits zero before reaching the target, the packet is dropped and an error is sent back to the sender. The round-trip time (RTT) measured in milliseconds reflects the cumulative network latency over the entire round trip, not just the last leg near the target - a point that is often misunderstood, since slow ping results can have their root cause anywhere along the path, not necessarily near the server being tested. A ping typically sends several packets in a row rather than just one, which lets you tell a one-off latency spike apart from a recurring problem and calculate a packet loss rate over the sample.

Reading the results

A stable, low RTT - a few milliseconds on a local network, 10 to 50 ms for a destination within the same country, and noticeably more for an intercontinental link - indicates a healthy connection. Even a small amount of packet loss (above 1-2%) is particularly damaging for latency-sensitive uses like VoIP or interactive remote sessions, where every dropped packet shows up as a glitch or audible cutout. Highly variable latency from one packet to the next (jitter) is often more of a problem for these same use cases than latency that is high but perfectly stable. "Request timed out" means no reply arrived within the allotted time - the host could genuinely be down, a firewall could be silently blocking ICMP, or a route could be broken somewhere along the path; "Destination unreachable" is different and more informative: an intermediate router explicitly sent back a message saying it could not forward the packet, which helps narrow down where the problem actually sits.

Common mistakes

The most common misreading is concluding a host is "down" the moment a ping fails, when in fact a great many servers and devices - especially behind a properly hardened firewall, or hosted with major cloud providers - deliberately block inbound ICMP as a matter of policy while being fully operational and reachable on their actual services (HTTP, a database, and so on). A missing ping reply is therefore only meaningful evidence of downtime when combined with other signals, such as the application itself also failing to respond. Conversely, a successful ping is no guarantee whatsoever that the application service hosted on that machine is working correctly - these are two entirely independent layers of the network stack.

When to use it

The first thing to check before escalating a ticket: does the machine respond at all, before digging any further? Confirming connectivity after a firewall rule or routing table change, to make sure the change did not break access. Establishing a baseline latency measurement before a VoIP rollout or a carrier link failover, so there is an objective point of comparison if call quality complaints come in later. A lightweight, low-overhead periodic health check for an MSP monitoring several client sites in parallel, always as a complement to - never a replacement for - deeper application-level monitoring.

Traceroute

Trace the network path (hop by hop) to a destination host.

Enter a hostname or IP address and run it to see every network hop between this server and the destination, with latency per hop.

You TTL=1 TTL=2 TTL=3 Host each hop replies "ICMP Time Exceeded" until TTL reaches the host

      

DNS Lookup (Nslookup)

Query DNS records: A, AAAA, MX, TXT, NS, CNAME, SOA, PTR, SRV, CAA.

Enter a domain, choose a record type (A, AAAA, MX, TXT, NS, CNAME, SOA, PTR, SRV, or CAA), then look it up.

You Root .com Auth NS ① query root ② referral → TLD ③ referral → auth NS ④ answer

      

Whois

Look up registration information for a domain or IP address.

Enter a domain or IP address to look up its registration details — registrar, owner organization, and important dates.

You Registry RDAP / :43 query: domain / IP reply: registrar, dates, name servers

      

Blacklist Check

Check whether an IP address or domain is listed on public spam/abuse blocklists (DNSBL).

Enter an IPv4 address or domain and run it to check 7 public DNSBL/RBL blocklists at once - each shows as listed, not listed, or check failed.

You zen.spamhaus.org spamcop.net sorbs.net +4 more reverse-IP DNS query to each DNSBL zone, in parallel

      

TCP Port Scan

Check whether TCP ports are open on a host or IP: common ports, a custom list, or the full 1-65535 range.

Enter a host or IP, pick common ports, a custom list, or the full range, then scan to see which TCP ports respond.

You 22 open 443 open 3389 closed 8080 closed SYN → SYN-ACK = open · SYN → RST = closed

        
      

HTTP Header Inspector

Fetch the HTTP response status and headers for a URL.

Enter a URL to fetch its HTTP response status code and every response header the server sends back.

You Server GET / HTTP/1.1 200 OK + headers Content-Type · Strict-Transport-Security · X-Frame-Options …

      

SSL / TLS Certificate Checker

Inspect a host's TLS certificate: issuer, validity dates, and days remaining.

Enter a hostname to inspect its TLS certificate — issuer, validity dates, and days remaining before it expires.

You Host ClientHello → ← ServerHello + Certificate + Finished Root CA Intermediate Leaf (site) certificate chain of trust · validity dates checked

      

Geo-IP Lookup

Look up the geographic location and network info for an IP address. Leave empty to look up your own public IP.

Enter any IP address, or leave it empty to look up your own, to see its approximate location and network/ISP info.

IP address Geo / RIR database City · Country ASN · Org

Subnet / CIDR Calculator

Computed entirely in your browser — no data sent to the server.

Enter an IP address and CIDR prefix (e.g. 192.168.1.0/24) to instantly compute the network range, broadcast address, and usable host count.

network bits (prefix) host bits /24 example — split moves with your prefix

      

Speed Test

Basic download/upload throughput test against this server (accuracy depends on the server's own uplink).

Press Start to measure download and upload throughput against this server. Accuracy depends on this server's own connection.

You Server ↓ download ↑ upload throughput (Mbps)

      

Country Code Dictionary

ISO 3166-1 alpha-2 country codes — searched entirely in your browser.

Search or browse the list of ISO 3166-1 alpha-2 country codes, looked up entirely in your browser.

CountryISO Code

Phone Dialing Code Dictionary

International calling codes by country — searched entirely in your browser.

Search or browse international calling codes by country, looked up entirely in your browser.

CountryDial Code

World Clock

Pick a time zone to see the current time — drag the globe to spin it.

Pick a time zone from the list, or drag the globe, to see the current time there.

Your time
--:--:--
—

—

Selected time
--:--:--
—
— UTC±00:00
Difference vs. you —

—

Drag to rotate the globe.

French Mobile Network Status

Mobile antenna sites down or under maintenance in France, by operator (Orange, Free, SFR, Bouygues Telecom), from ARCEP's public data. Snapshot updated once a day by ARCEP - not a minute-by-minute feed.

Browse mobile antenna and fibre outage data by French operator — no input needed, updated automatically from ARCEP's public data.

Source: ARCEP, "Sites indisponibles" dataset, published under Licence Ouverte / Etalab 2.0 - commercial reuse explicitly allowed, unlike the IODA/CAIDA data this tab used before. The Normal/Watch/Alert badge is an in-house estimate (today's outage count vs. the median of prior days), not an official ARCEP classification. Source links below.

Most affected departments

Number of sites currently down or under maintenance, by department. Click an operator above to filter.

Data: Arcep — Sites indisponibles · Official network status map


Fixed Network (Fibre)

Fibre (FTTH) network quality by operator: reported-outage rate and connection-failure rate, from ARCEP's public data. Monthly indicators, 6-month rolling average - not a live feed like the mobile section.

Source: ARCEP, "Qualité des réseaux en fibre optique" dataset, published under Licence Ouverte / Etalab 2.0 - commercial reuse explicitly allowed. Source links below.

By operator (parent group)

Averages over the last 6 available months, per infrastructure-operator parent group.

Data: Arcep — Qualité des réseaux en fibre optique