Powered by SnapDock Rendering

StaxPing — Output Reference

← Back to StaxPing Index

Output Reference

StaxPing produces clean, aligned, and predictable output across all supported platforms.
This page provides examples of each module’s output, including combined diagnostics, error messages, and fallback behavior.

DNS Output

Example:

=== DNS ===============================
  IPv4:        ["142.251.221.78"]
  IPv6:        ["2404:6800:4006:801::200e"]
  Lookup:      10061 ms

Characteristics:

  • IPv4 and IPv6 results are shown separately
  • Lookup time is always included
  • Multiple records are displayed as arrays
  • Clean alignment for readability

Ping Output

Example:

=== Ping ==============================
  Sent:        4
  Received:    4
  Loss:        0.0%
  Min:         38.26 ms
  Avg:         46.93 ms
  Max:         54.72 ms

Characteristics:

  • Consistent ordering of fields
  • Latency values always shown with two decimals
  • Packet loss displayed as a percentage
  • No ambiguous symbols or shorthand

HTTP Output

Example:

=== HTTP ==============================
  Status:      200
  Time:        821 ms
  Final URL:   https://www.google.com/

Characteristics:

  • Status code only (no body parsing)
  • Response time in milliseconds
  • Final URL shown after redirects
  • Clear error messages for timeouts or failures

Traceroute Output

Example:

=== Traceroute ========================
   1  192.168.0.1      1.94 ms
   2  58.162.26.10     40.11 ms
   3  203.50.61.1      39.11 ms
   4  203.50.61.0      35.74 ms
   5  203.50.13.157    50.94 ms
   6  203.50.11.173    52.11 ms
   7  72.14.212.22     54.21 ms
   8  192.178.97.155   55.90 ms
   9  142.251.252.203  57.20 ms
  10  142.251.221.78   46.19 ms

Characteristics:

  • Hop numbers are aligned
  • IP addresses are left‑aligned
  • Latency is right‑aligned for readability
  • Missing hops or timeouts are handled cleanly

Combined Output

Example:

========================================
  StaxPing v0.1.0 — Network Diagnostics
  Target: google.com
========================================

=== DNS ===============================
  IPv4:        ["142.251.221.78"]
  IPv6:        ["2404:6800:4006:801::200e"]
  Lookup:      10061 ms

=== Ping ==============================
  Sent:        4
  Received:    4
  Loss:        0.0%
  Min:         38.26 ms
  Avg:         46.93 ms
  Max:         54.72 ms

=== HTTP ==============================
  Status:      200
  Time:        821 ms
  Final URL:   https://www.google.com/

=== Traceroute ========================
   1  192.168.0.1      1.94 ms
   2  58.162.26.10     40.11 ms
   3  203.50.61.1      39.11 ms
   4  203.50.61.0      35.74 ms
   5  203.50.13.157    50.94 ms
   6  203.50.11.173    52.11 ms
   7  72.14.212.22     54.21 ms
   8  192.178.97.155   55.90 ms
   9  142.251.252.203  57.20 ms
  10  142.251.221.78   46.19 ms

Characteristics:

  • Consistent section headers
  • Predictable ordering
  • No color codes or terminal‑dependent formatting
  • Works identically across Linux and Windows

Error Messages

StaxPing uses clear, human‑readable error messages.

Examples:

DNS lookup failed: no records found

ICMP unavailable: insufficient permissions

HTTP request failed: timeout reached

Traceroute not supported on this platform

Characteristics:

  • No cryptic codes
  • No stack traces
  • No platform‑specific jargon

Fallback Messages

When a module is unsupported or unavailable, StaxPing reports it cleanly without interrupting other diagnostics.

Examples:

Traceroute unavailable: skipping

ICMP not permitted: ping test disabled

HTTP check skipped: outbound requests blocked

Fallback behavior ensures StaxPing remains predictable even in restricted environments.

StaxPing’s output is designed to be readable, consistent, and stable across all supported platforms, making it suitable for both human use and automation.