Network Tools
Network tools focus on path health, host reachability, and registration context. They are optimized for outage triage where you need quick evidence before changing policy or escalation paths.
When to use this category
- A service endpoint appears reachable from one location but not another.
- You need registry and assignment context for a domain, ASN, or address.
- TCP path behavior is uncertain and requires hop-level visibility.
What you get from these pages
- Connectivity evidence with timestamps for incident timelines.
- Path-level hints to isolate firewall, routing, or upstream breakpoints.
- Clean transitions into DNS, TLS, and mail-layer diagnostics.
Operator tips
- Validate TCP reachability before assuming application-level defects.
- Use traceroute snapshots before and after policy changes to detect route drift.
- Correlate path anomalies with deployment windows and provider advisories.
Tools in this category
Frequently asked questions
Why does ping succeed while application traffic fails?
Transport-level reachability can remain healthy while TLS, HTTP, or auth layers fail.
Is traceroute always symmetric?
No. Forward and return paths may differ, especially across transit providers.
Can RDAP data be stale?
Yes. Registration details can lag operational reality in fast-changing environments.
Should I block paths immediately on first anomaly?
Gather repeatable evidence first to avoid introducing unnecessary traffic impact.
What category should follow network checks?
Usually web/TLS or email checks, depending on the affected service layer.