Table of Contents
Telenegar Ping Check Tool
The Telenegar Ping Check Tool is a network connectivity diagnostic utility designed to measure reachability, round-trip packet latency, and packet loss from remote probe vantage points to any target IPv4/IPv6 address or domain hostname.
It supports both standard ICMP Ping protocol testing and TCP Ping testing (useful when ICMP echo requests are filtered by firewalls or when shell/raw-socket access is restricted on probe nodes).
Tool Features & Parameters
The Ping Check interface provides customized parameters to test reachability across different transport modes and probes:
| Parameter | Description | Options / Examples |
|---|---|---|
| Target Host / IP | The domain name, hostname, or IP address to test for reachability. | e.g., s231.mehost.co, 192.0.2.1 |
| PACKET COUNT | The number of echo request packets sent during the check. | Options: 4 packets, 8 packets, 10 packets |
| TCP PORT | The specific TCP service port used when performing a TCP Ping (e.g., HTTP/HTTPS, SSH). | Default: 443 (HTTPS), 80 (HTTP), 22 (SSH), 25 (SMTP) |
| PROBE | The geographical probe vantage point and protocol type executing the ping test. | Categorized into ICMP Ping and TCP Ping (no shell access) probes. |
Probe Types & Protocols
- ICMP Ping Probes: Uses raw ICMP Echo Request/Reply packets (`ping`). Provides true network-layer latency and packet loss metrics.
- *Example:*
Tehran, Iran — Atrin Information & Communications Technology Company
- TCP Ping Probes: Uses TCP `SYN` handshakes to measure response times to a specific TCP port (`TCP Ping`). Used when probes lack raw socket/shell permissions or when targets block ICMP traffic.
- *Example:*
Falkenstein, Germany — Hetzner Online GmbH
<note warning> Probes operating in TCP Ping mode test whether a specific TCP port responds rather than sending raw ICMP echo requests. While useful for verifying port-level reachability, latency values reflect the TCP three-way handshake time rather than ICMP echo response time. </note>
How to Perform a Ping Check
# **Enter Target Host Name or IP:** Type the domain or IP into the input field (e.g., ''s231.mehost.co''). # **Select Packet Count:** Choose the number of probe packets to send from the **PACKET COUNT** dropdown menu (e.g., ''4 packets''). # **Set TCP Port (If Applicable):** If using a TCP Ping probe, specify the target TCP port in the **TCP PORT** field (e.g., ''443'' for web servers, ''25'' or ''587'' for mail servers). # **Select Probe Location & Protocol:** Open the **PROBE** dropdown menu and select an active probe under either **ICMP Ping** or **TCP Ping (no shell access)**. # **Execute Test:** Click the blue **Ping** button to initiate packet transmission and view min/avg/max latency (ms) and packet loss percentage.
Key Use Cases & Diagnostics
1. Reachability & Packet Loss Detection
Determine whether a host or server is online and responding from domestic or international vantage points. A 100% packet loss indicates an offline host, network outage, or strict firewall blocking.
2. Firewall & ICMP Filter Troubleshooting
If a server fails an ICMP Ping but passes a TCP Ping on port `443` or `80`, the host is online and functioning, but its edge firewall is dropping ICMP echo requests.
3. Mail & Web Service Connectivity Verification
Test TCP reachability on service-specific ports to verify edge firewalls are open:
- Port `443` / `80` — Web server reachability (audit further with Telenegar Site Check Tool).
- Port `25` / `587` / `993` — Mail server reachability (audit further with Telenegar Mail Check Tool).
4. Latency Analysis (Domestic vs. International)
Compare round-trip times (RTT) across European and Iranian probes to evaluate route latency, BGP routing paths, and network degradation.
Related Documentation & Tools
- Telenegar Site Check Tool — Test website HTTP/HTTPS availability, redirects, and SSL certificates.
- Telenegar DNS Check Tool — Query DNS record resolution, propagation, and DNSSEC validation.
- Telenegar Mail Check Tool — Diagnostic tool for email security, SPF, DKIM, and DMARC checks.
- Cybersecurity Best Practices — Infrastructure hardening and firewall rule guidelines.
- Reverse DNS (PTR) — Match server IP addresses to hostnames.
