Network Tools
Test your connection speed, check your IP address, and analyze network performance.
When something goes wrong with a network — a deploy doesn't reach prod, a VPN misbehaves, Zoom stutters — the diagnostic loop almost always starts with "what's my IP", "is DNS pointing at the right place", or "what's my actual bandwidth right now". These tools answer those questions in seconds without installing software or creating an account. Speed Test uses incompressible random data so QoS-aware middleboxes can't inflate the numbers, IP Check returns your public IP plus ISP, country, and ASN (useful for verifying a VPN is actually terminating where you configured it), and DNS Lookup hits Google's public DNS servers for every record type — A, AAAA, CNAME, MX, TXT, NS, and SOA — which is faster than remembering `dig`'s flag arguments.
Internet Speed Test
Measure download speed, upload speed, and ping latency against a fast global network. Uses incompressible random data so QoS-aware middleboxes can't inflate the numbers — no ads, no signup.
IP Address Checker
Check your public IPv4 and IPv6 address with geolocation (country, city, timezone), ISP, ASN, and reverse DNS. Useful for verifying VPN termination and debugging connectivity.
DNS Lookup
Query live DNS records for any domain — A, AAAA, CNAME, MX, TXT, NS, SOA, CAA — with TTLs. Perfect for verifying deploys, SPF/DKIM/DMARC email records, and debugging propagation issues.
The Network Tools Guide
A typical "something is broken" workflow
Start with Speed Test to rule out local bandwidth issues. If download/upload numbers match your plan but calls still stutter, the problem is likely ping or jitter — check the latency figure, not just the throughput. If the speed test itself won't start, move up a layer: open IP Check to confirm you're reachable on a sensible public IP (and not, say, stuck behind a captive portal that's NAT'd you somewhere weird). If a deploy hasn't propagated, DNS Lookup lets you check the record type in question (A for IPv4, AAAA for IPv6, MX for email) with TTLs shown — a low TTL means the cache will refresh quickly, a high TTL means you may be waiting hours for a DNS change to go global.
Reading email-record types (SPF, DKIM, DMARC)
Email deliverability problems almost always trace back to DNS. Use DNS Lookup with the TXT record type to see your SPF entry (look for `v=spf1 include:...`), DMARC policy (record name `_dmarc.yourdomain.com` with `v=DMARC1`), and DKIM (usually at `default._domainkey.yourdomain.com` or whatever selector your provider uses). When switching ESP (from Mailchimp to Loops, for example), verify all three are updated before flipping production sends — a bad SPF or a stale DMARC `p=reject` policy can silently drop 100% of your transactional email.
Speed-test caveats
Browser-based speed tests measure from your browser to the nearest server, which underestimates raw line speed (TLS overhead, TCP slow-start, and browser connection limits all eat into the number). For a true "what's my line rate" measurement, use a wired connection, close other tabs, and run three tests to get a median. If your ISP guarantees "up to 1 Gbps" and you see 600-700 Mbps in a browser test, that's normal — the limit is your local Ethernet/Wi-Fi and the server's upload capacity, not your ISP. For persistent sub-par numbers across multiple tools and networks, the bottleneck is somewhere between your router and the ISP — worth a call.