The reasons may vary: regional ISP blocks, routing issues, CDN restrictions, IP address blocking. Use different check types (HTTP, Ping) for accurate diagnostics.

• HTTP/HTTPS — checks whether the web server responds, returns the response code, latency, IP address and redirects. Suitable for websites, APIs and web applications.
• Ping (ICMP) — sends a packet to the specified host and measures response time. Shows whether the server is reachable at the network level, but does not guarantee the web service is working — many servers block ICMP.
• TCP Port — checks whether a specific port is open on the server (e.g. 443, 25, 3306). Allows you to verify availability not only of websites, but also mail servers, databases and other services.
• DNS — checks whether the domain name resolves to an IP address. If DNS does not respond, the site will be unavailable even if the server is working. Returns DNS records and resolution time.

The check results include:

• HTTP response code — whether the server responds and how;
• response time (latency) — how many milliseconds it took the server to respond from each location;
• resource IP address — which address was resolved for the domain at a specific point in the world.

Under developoment is redirect chain display — if the server redirects the request, the service will show the full path.

The site may be unavailable only in certain regions or countries, while responding normally from other points.

A normal response has a code in the 2xx range:

• 200 OK — page loaded successfully;
• 201 Created — resource created (relevant for APIs);
• 204 No Content — request completed, response body is empty.

3xx codes are also not errors — they are redirects:

• 301 Moved Permanently — permanent page move to a new address;
• 302 Found — temporary redirect.

Problem codes fall in the 4xx and 5xx ranges:

• 400 Bad Request — malformed request to the server;
• 401 Unauthorized — authentication required;
• 403 Forbidden — access to the resource is denied;
• 404 Not Found — page not found;
• 429 Too Many Requests — server is blocking requests due to rate limit exceeded;
• 500 Internal Server Error — internal server error;
• 502 Bad Gateway — server received an invalid response from an upstream server;
• 503 Service Unavailable — server is overloaded or under maintenance;
• 504 Gateway Timeout — server did not receive a timely response from upstream.

A missing response (timeout) also indicates the resource is unavailable.

Ping sends ICMP packets to the specified host from multiple locations and measures response time. The check results show:

• packet result — how many packets reached the server and came back (e.g. 3/3 means all three packets received a reply);
• RTT min/max/avg — minimum, maximum and average response time in milliseconds from each city;
• IP address — which address corresponds to the domain at that point.

If a city shows an empty result — the server is not responding to ICMP requests from that location. This may indicate either real unavailability or Ping being blocked at the firewall level.

The TCP check establishes a connection to the specified server port from different locations. Unlike Ping, it checks not just host reachability but the availability of a specific service. The results show:

• connection time per port — how many milliseconds it took to establish a TCP connection to given port from each city;
• IP address — the address resolved for the domain at that point;
• port availability — if the port is closed or blocked, the connection will not be established and the result will be empty.

The TCP port check is useful when a site does not open but Ping succeeds — this means the server is running but the web service is unavailable.

The DNS check requests domain name resolution to an IP address from different cities and countries using selected DNS servers. You can choose public resolvers — Cloudflare, Google, Yandex — or specify your own. The results show:

• IP addresses the domain resolves to (including IPv4 and IPv6) from each point and through each DNS server;
• resolution time — how many milliseconds the DNS server took to respond from that location;
• summary statistics — total check time, number of points and countries covered.

The DNS check helps identify whether a domain is blocked at the DNS level by a specific ISP, whether DNS record changes have propagated correctly after a site migration, and whether different resolvers return the same IP across different regions.

Enter the website address and run a check from different countries, cities and providers. If the website opens from some locations but does not respond from others, this may indicate regional blocking, provider filtering, a DNS, CDN or routing issue. For more accurate diagnostics, use an HTTP check, Ping, a DNS check and a port check.

Check results are guaranteed to be available via link for 2 days. After that, they are stored for as long as the service capacity allows. Old data is deleted automatically once the storage limit is exceeded. Save the link if you need to share the results with colleagues.

Yes, use the provider filter in the interface. Checks are available via MTS, Megafon, Beeline, Rostelecom and other operators across different cities.

GEOPinger supports HTTP/HTTPS checks (including redirects and SSL validation), ICMP Ping, TCP port scanning and DNS resolution through various servers. All checks are performed in parallel from 40+ locations.

Yes, GEOPinger performs only standard network requests and does not collect confidential data. All checks are logged minimally and used solely for displaying results.