How to check website availability from other countries?

Enter the website URL in the check field, select the test type (HTTP, Ping, TCP, or DNS), and press Enter. GEOPinger will check availability from 80+ locations in Russia, CIS countries, and worldwide in 10 seconds.

Why is the site unavailable from some cities?

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

What types of checks are available?

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.

What does the website availability check show?

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; redirect chain — if the server redirects the request, the service will show the full path; availability from different locations — the site may be unavailable only in certain regions or countries, while responding normally from other points.

Which HTTP codes indicate the site is working correctly?

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.

Which HTTP codes indicate a problem?

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.

What does the Ping check show?

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.

What does the TCP port check show?

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 port 443 (HTTPS) and port 80 (HTTP) 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.

What does a DNS check show?

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.

How to check if a website is blocked?

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.

How long are check results stored?

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.

Can I select specific providers for the check?

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

What protocols are supported?

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.

Is it safe to use the service?

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

Website availability, DNS, port and UX checks from different countries

What the Ping check shows

ICMP Ping checks whether a host responds to network ping requests — a fast way to see whether a server, router, CDN edge, or public IP address is reachable from the selected locations.

Detects

server unavailability packet loss high latency regional issues routing issues ICMP blocking

Measured at each location

response status round-trip time min / avg / max packet loss

This is what the check result looks like

Russia5 / 6

City Result RTT min/max/avg IP

Moscow 3 / 3 18 / 24 / 21 ms 5.255.255.5

Saint Petersburg 3 / 3 16 / 22 / 19 ms 5.255.255.5

Novosibirsk Timeout 5.255.255.6

Ekaterinburg 3 / 3 30 / 40 / 35 ms 5.255.255.5

Kazan 3 / 3 22 / 29 / 25 ms 5.255.255.5

Vladivostok 2 / 3 18 / 24 / 21 ms 5.255.255.6

How to read the result

If the target responds, the host is reachable over ICMP from this location.

No response does not always mean the server is unavailable: many providers, firewalls, cloud platforms, and corporate networks block ICMP by default. In that case, compare the result with an HTTP, TCP, or DNS check.

What the HTTP check shows

Whether a website, API, or web application opens from different locations around the world and whether the server responds correctly — in other words, what a real user actually sees.

Detects

website / API unavailability HTTP errors TLS / HTTPS errors slow backend CDN / proxy issues

Measured at each location

response code response time timeouts

Work in progress

redirect issues redirects and final URL TLS handshake response headers

This is what the check result looks like

Russia4 / 6

City Result Latency IP

Moscow 200 128 ms 5.255.255.5

Saint Petersburg 200 134 ms 5.255.255.5

Novosibirsk 404 5.255.255.6

Ekaterinburg 200 159 ms 5.255.255.5

Kazan 200 147 ms 5.255.255.5

Vladivostok Timeout 5.255.255.6

Server response codes

Success 200 · 201 · 204

Redirect 301 · 302

Client error 400 · 401 · 403 · 404 · 429

Server error 500 · 502 · 503 · 504

What the TCP check shows

A TCP check shows whether a specific port is open and reachable from the selected locations — that is, whether the service accepts connections. Suitable for web servers, APIs, databases, VPN, mail, SSH, and custom ports.

Detects

closed port service not running timeout firewall blocking regional filtering

Measured at each location

connection success connection time

Work in progress

connection refused connection reset

This is what the check result looks like

Russia5 / 6

City Port 443 Port 80 IP

Moscow 15 ms 13 ms 5.255.255.5

Saint Petersburg 28 ms 32 ms 5.255.255.5

Novosibirsk Timeout 100 ms 5.255.255.6

Ekaterinburg 65 ms 58 ms 5.255.255.5

Kazan 42 ms 39 ms 5.255.255.5

Vladivostok 222 ms 234 ms 5.255.255.6

How to read the result

28 ms — The TCP connection was established within the reported time, and the port accepts connections.
Timeout — no response was received in time.
Reset — the connection was interrupted or actively closed.

If TCP does not work but DNS does, the issue may be related to a firewall, a closed port, routing, a server failure, or regional filtering.

What the DNS check shows

A DNS check shows whether a domain name resolves correctly from different locations. DNS is the first step before a website, API, or mail service becomes accessible to the user.

Detects

DNS failures incorrect records regional differences slow resolution configuration errors CDN routing split-horizon DNS

Shown by location

resolved IPs DNS response time resolution errors

Work in progress

TTL record value authoritative NS

This is what the check result looks like

Russia5 / 6

City 8.8.8.8 8.8.4.4

Moscow 12 ms