Online website availability check

Website blocking, UX, DNS, Ping and TCP port checks from different countries

geopinger@check :~$ ./check

Diagnostics at every network layer

Four independent checks — from web server response to domain name resolution.
They run in parallel from all nodes.

Ping (ICMP)

Host response time from different networks: min / avg / max RTT and packet loss. Shows network availability and route quality.

ping23 ms·0% loss

HTTP / HTTPS

A real request to the site from each location: response code, response time, IP, and redirects. Reveals ISP blocking and CDN or certificate issues.

GET /200 OK142 ms

TCP port

Whether the server accepts connections on a port — 80, 443, 22, 3306, and others. Suitable for websites, email, databases, and APIs; detects firewall blocking.

:443open18 ms

DNS

Resolution via Cloudflare, Google, Yandex, or your own server. Compares responses across countries — GeoDNS, record inconsistencies, DNS blocking.

A →5.255.255.5

Deeper than network availability

Two advanced checks show not just whether the server responds, but whether a real user can actually see the site.

DPI check BETA

A layer-by-layer connection trace across the stack — from DNS to HTTP. It shows exactly at which level access breaks, and distinguishes a real service outage from ISP-side blocking.

detects
DPI filterTLS / SNI blockTCP drop DNS spoofingRST injection
DNSOK · 12ms
TCPOK · 34ms
TLS·SNIRST ✕
HTTP

UX check BETA

AI opens the site in a real browser, waits for it to fully load, and evaluates the page as a real user would see it — with metrics and a screenshot in the report.

analyzes
console errorsCAPTCHA / anti-botblank screen screenshotLCP / TTFB
https://example.com
verdictsite is accessible
HTTP200 OK
contentrendered
LCP1.2 s
console0 errors
CAPTCHAnot found

GEOPINGER monitoring network

Real nodes in ISP networks — not datacenter IPs, but real consumer internet connections. Our key metrics:

90monitoring nodesDistributed worldwide
14countries and regionsCIS, Europe, Asia, America
6types of checksHTTP · Ping · TCP · DNS · DPI · UX
~10secaverage checkResult almost instantly

Checking from 52 cities worldwide

Real ISP networks in 14 countries — Russia, CIS, Europe, Asia, America, and Africa.

Russia34
Kazakhstan5
United States2
Armenia1
Brazil1
Belarus1
China1
Germany1
India1
Kyrgyzstan1
The Netherlands1
Tajikistan1
Uzbekistan1
South Africa1

Frequently asked questions

Как читать результаты, какие бывают проверки и что означают HTTP-коды ответов.

Why is the site unavailable from some cities?

The reasons may vary: regional ISP blocks, routing problems, CDN restrictions, or IP-based blocking. Use different types of checks (HTTP, Ping) for accurate diagnostics.

What types of checks are available?

  • HTTP/HTTPS - checks whether the web server responds, returning 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 the response time. It 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 on the server is open (for example, 443, 25, 3306). It helps verify the availability not only of websites, but also of 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. It returns DNS records and the name resolution time
  • UX - checks the site's functionality at the application level. An AI agent opens the page in a real browser, evaluates loading, visible content, console errors, network issues, possible blocks, CAPTCHA, and generates a structured report.

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 the server needed to respond from each location
  • Resource IP address — which address was resolved for the domain in that specific part of the world
  • Redirect chain — if the server redirects the request, the service will show the entire path
  • Availability from different locations — the site may be unavailable only in certain regions or countries, while responding normally from other locations

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 redirect to a new page address
  • 302 Found - temporary redirect

Which HTTP codes indicate a problem?

Problem codes are in the 4xx and 5xx ranges:
  • 400 Bad Request - invalid request to the server
  • 401 Unauthorized - authorization required
  • 403 Forbidden - access to the resource is forbidden
  • 404 Not Found - page not found
  • 429 Too Many Requests - the server is blocking requests due to the rate limit being exceeded
  • 500 Internal Server Error - internal server error
  • 502 Bad Gateway - the server received an invalid response from the upstream node
  • 503 Service Unavailable - the server is overloaded or undergoing maintenance
  • 504 Gateway Timeout - the server did not receive a timely response from upstream
A missing response (timeout) also means the resource is unavailable.

What does the Ping check show?

Ping sends ICMP packets to the specified host from multiple locations and measures the response time. Based on the results, you can see:
  • Packet result — how many packets reached the server and came back (for example, 3/3 means all three packets received a response)
  • 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 location
If a city shows no result, the server is not responding to ICMP requests from that location. This may mean either an actual outage or Ping being blocked at the firewall level.

What does a port check show?

A TCP port check establishes a connection to the specified server port from different locations. Unlike Ping, it checks not just whether the host is reachable, but whether a specific service is working. Based on the results, you can see:
  • Connection time for each 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 location
  • Whether the port is available — if the port is closed or blocked, the connection will not be established and the result will be empty
A TCP port check is useful when the website does not open but Ping works — this means the server is up, but the web service is unavailable.

What does a DNS check show?

A DNS check requests resolution of a domain name to an IP address from different cities and countries through selected DNS servers. You can choose public resolvers — Cloudflare, Google, Yandex — or specify your own addresses. Based on the results, you can see:
  • The IP addresses the domain resolves to — including IPv4 and IPv6 — from each location and through each DNS server
  • Resolution time — how many milliseconds it took the DNS server to return a response from that location
  • Summary statistics — the total check time, the number of locations, and the countries covered
A DNS check helps determine whether a domain is blocked at the DNS level by a specific provider, whether DNS record changes propagated correctly after a site migration, and whether different resolvers return the same IP in different regions.

What does a website UX check show?

A UX check shows whether a real user can open and use the website. GEOPinger launches the page in a browser, waits for it to load, and analyzes visible content, JavaScript, network requests, possible blocking, CAPTCHA, cookie banners, and errors. The report shows an overall conclusion, user impact, confidence level, load time, LCP, page size, check details, and screenshots.

How is a UX check different from HTTP, Ping, DNS, and port checks?

HTTP, Ping, DNS, and TCP port checks verify network and server availability: whether the server responds, whether the port is open, whether the domain resolves, and whether the host is reachable. A UX check goes further: it opens the site in a browser like a user would and determines whether the page actually loads, whether the main content is visible, and whether there are any errors that prevent the site from being used.

How to check if a website is blocked?

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

How long are check results stored?

The check results are guaranteed to be available via the link for 2 days. After that, we will keep them for as long as our resources allow. Old data will be deleted automatically once the configured 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 in 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 sensitive data. All checks are logged minimally and used only to display the results.
Work in progress