The network tools Apple stopped shipping, on every Apple device you own

Work in this order: name, then reachability, then path, then reputation. Most incidents die at step one. Packet loss. Loss on a ping only means something if it is consistent and if the destination cares about ICMP. A router dropping 3% of echo requests while forwarding your TCP traffic at line rate is doing its job — ICMP is handled by the control plane and is the first thing rate-limited under load. What matters is loss that tracks your actual symptom, and jitter: probes at 40, 41, 39, 210, 42 ms are worse news than ten steady probes at 180 ms. Remember which engine you are on, too. A TCP-connect ping reports total failure only when the probe is silently dropped — a host behind a firewall that discards traffic to port 80 reads as 100% loss even though it answers ICMP. A host with nothing listening but no firewall replies with a RST, which SSHive correctly counts as reachable and marks 'port closed'. Un ping TCP n'annonce 100 % de perte que si la sonde est jetée en silence : un hôte derrière un pare-feu qui bloque le port 80 apparaît à 100 % de perte alors qu'il répond en ICMP. Un hôte sans service mais sans filtrage renvoie un RST, que SSHive compte correctement comme joignable en indiquant « port fermé ». Three asterisks in a traceroute. A starred hop in the middle of an otherwise complete trace is almost never the fault. It means that router chose not to send an ICMP time-exceeded reply, or rate-limited it. A real break looks different: every hop from N onward is stars and the destination never answers. Same logic for latency — one hop at 180 ms followed by a hop at 30 ms is not a slow hop, it is a router deprioritising your probe. Only latency that rises and stays risen through the final hop is a path problem. WHOIS status codes. clientTransferProhibited is healthy: your registrar has locked the domain against unauthorised transfer. serverHold is the emergency — the registry has pulled the domain from the zone, so it will not resolve at all. redemptionPeriod and pendingDelete mean it already expired. MX priority is a preference, not a quality score: lowest number tried first, equal numbers round-robin. DNSBL hits are not equal. Read the return code (desktop also shows the TXT reason; mobile shows the code alone). A Spamhaus PBL entry only says "this IP is a dynamic range that should not send mail directly" — expected on a home line. UCEPROTECT level 2 — queried on iPhone and iPad only — lists a whole allocation because a neighbour spammed, and most receivers ignore it; a lone level-2 hit beside otherwise clean rows is usually noise.