Foire Aux Questions

MTR (My Traceroute) is an advanced tool that combines the functionality of Traceroute and Ping. While Traceroute shows the path traffic takes to reach a destination, MTR continuously sends packets to every router (hop) along that path to collect statistics about latency and packet loss at each stage. This makes it invaluable for identifying exactly where a network slowdown is occurring. For example, if you notice 10% packet loss, MTR can show you if the loss starts at your home router, inside your ISP’s network, or at the destination data center’s edge router. This level of detail allows system administrators to provide concrete evidence when reporting issues to service providers. Our global MTR tool lets you run these tests from various continents to see how different internet backbones handle traffic to your server.

A DNS lookup is the process of translating human-readable domain names into machine-readable IP addresses. Our global DNS propagation checker queries authoritative nameservers and various recursive resolvers across different geographic regions to verify if your DNS records are updated everywhere. It supports all critical record types, including A (IPv4), AAAA (IPv6), MX (Mail Exchange), CNAME (Canonical Name), and TXT (Text records for security like SPF and DKIM). When you migrate a website or change email providers, DNS changes can take hours or even days to fully propagate due to TTL (Time to Live) settings. By using our worldwide lookup tool, you can see in real-time which countries still see the old records and which have already switched to the new ones, allowing you to confirm a successful deployment and minimize downtime.

TCP and UDP port checks are critical for diagnosing firewall configurations and ensuring that specific services are accessible to the public. TCP (Transmission Control Protocol) is used for reliable communication in services like web (80/443), SSH (22), and databases (3306), while UDP (User Datagram Protocol) is preferred for speed in services like DNS (53), VOIP, and many online games. Often, a server might be online and "pingable," but a specific service like a web server might be unreachable because port 443 is blocked by a firewall or not listening. Our port checker tests connectivity from multiple global regions to verify that your firewall rules are correctly allowing legitimate traffic without exposing sensitive ports to the entire internet. This helps prevent security gaps while ensuring service continuity for your global users.

A professional SSL/TLS check verifies the digital identity of your website and ensures that all data transmitted between the server and the browser is encrypted and secure. It checks the certificate validity, expiration date, and whether it is trusted by major browsers. More importantly, it inspects the "Chain of Trust" to ensure that intermediate certificates are correctly installed, preventing "Untrusted Connection" warnings on some devices. In addition to basic validity, our tool analyzes supported protocols (like TLS 1.2 and 1.3) and cipher suites to detect weak encryption that might be vulnerable to attacks. Since many websites use CDNs, a certificate might look valid in your region but be expired on an edge server in another country. A global SSL check ensures consistency across all edge nodes, protecting your brand reputation and user trust worldwide.

IP Address information provides detailed metadata about any endpoint connected to the internet. This includes the geographic location (country, city, and coordinates), the Internet Service Provider (ISP), and the Autonomous System Number (ASN). Knowing the ASN is particularly useful for identifying the owner of a network block, such as Amazon AWS, Google Cloud, or a specific local telecom provider. Our IP Info tool also helps in security auditing by identifying known VPN, Proxy, or Tor exit nodes, which are often used to mask malicious activity. For network administrators, comparing results from multiple providers helps verify the accuracy of geolocation databases, which is essential for content delivery, localized pricing, and regional compliance. Whether you are identifying a suspicious visitor or verifying your own server's network identity, our global lookup provides the precision data you need.

A Ping check is an essential network diagnostic tool that measures network latency, also known as Round Trip Time (RTT). It operates by sending ICMP (Internet Control Message Protocol) echo request packets to a specific target host or IP address and waiting for an echo reply. This process helps determine if a server is reachable across the network and how fast it can respond to requests. By testing from multiple global locations, you can identify regional routing issues, backbone congestion, or local ISP outages that might affect only a subset of your users. Consistent monitoring with ping helps maintain high availability and provides data for troubleshooting intermittent connectivity drops.

An HTTP status check goes beyond simple connectivity tests by performing a real web request to verify the availability and performance of a specific URL. Our tool simulates a visitor's browser from multiple global locations to ensure that your web server returns the expected response code, such as "200 OK". It also captures redirect chains (301/302), missing pages (404), or server-side crashes (500 Internal Server Error). Beyond just the status code, our HTTP check measures the Time to First Byte (TTFB) and total response time. This is crucial for SEO and user retention, as slow-loading pages often lead to higher bounce rates. Monitoring HTTP status from worldwide locations helps detect CDN misconfigurations, regional geoblocking, and localized outages that simple uptime monitors might miss.

Interpreting ping results requires looking at both latency (ms) and packet loss (%). Generally, a response under 50ms is considered excellent, making it ideal for real-time applications like VOIP or gaming. Responses between 50ms and 150ms are acceptable for general web browsing, while anything over 150ms indicates a noticeable delay that could impact user experience. Packet loss is even more critical; any significant percentage of lost packets suggests serious network congestion, faulty hardware along the path, or aggressive firewall filtering. Jitter, or the variation in latency between consecutive pings, is another sign of an unstable connection. If you see high latency from only one region, it's likely a local routing or provider issue, whereas global high latency might indicate server-side performance bottlenecks.

When our checker detects an error, the specific HTTP status code provides the first clue for troubleshooting. A 403 Forbidden error often points to server-side security rules or a WAF (Web Application Firewall) blocking our diagnostic nodes. A 404 Not Found indicates that the URL path is incorrect or the resource has been moved without a proper redirect. 5xx level errors generally indicate server-side issues. For example, a 502 Bad Gateway or 504 Gateway Timeout often means the reverse proxy (like Nginx or Cloudflare) cannot communicate with the upstream application server. If you see high response times from only specific regions, check your CDN configuration and regional server performance to identify localized latency issues.

What is a Ping check?

Ping is a basic diagnostic tool that tests if a specific host (IP or domain) is reachable across the network. It measures the round-trip time (latency) for messages sent from our global nodes to your destination.

How to interpret latency results?

Latency is measured in milliseconds (ms). Lower is better. 0-50ms is excellent, 50-150ms is good, and over 200ms might be noticeable for real-time applications like gaming or VoIP.

What does "Request Timed Out" mean?

This usually means the destination server is either down, or it is configured to ignore ICMP (Ping) requests for security reasons.

What does the HTTP check verify?

The HTTP check verifies that it can reach your web server and receive a valid response. It checks the HTTP status code (e.g., 200 OK), download speed, and response headers.

What are common status codes?

• 200 OK: Success.
• 301/302: Redirection.
• 404: Page not found.
• 500/503: Server error.

What is DNS Propagation?

When you update your DNS records, it takes time for the changes to spread across the internet. This tool helps you see the current records as seen from different global locations.

Why do I see different results from different nodes?

This is common during propagation. Different DNS resolvers across the globe may have cached older information.