Vérification d’accessibilité d’URL

Vérifier l’accessibilité d’un site ou d’une API depuis plusieurs régions

Service serveur requisChecks originate from remote regions. Limit: 10 per IP per day.
Chargement de l’outil…

À propos de Vérification d’accessibilité d’URL

Vérifier l’accessibilité d’un site ou d’une API depuis plusieurs régions

A useful availability check distinguishes a completed HTTP response from a timeout, DNS failure, TLS problem, redirect issue, or regional routing failure. The probe location, request method, cache state, and network conditions all affect the measurement.

Comment utiliser cet outil développeur

  1. Enter the final HTTPS or HTTP URL you want to test and choose the region group that matches the audience or incident you are investigating.
  2. Run the check and wait for the regional samples to complete. Review status codes, redirect information, response time, and the share of successful samples together.
  3. Compare regions and repeat the check when the result is surprising. A single timeout is evidence of a failed probe, not proof that every visitor is affected.
  4. Use the result with DNS, CDN, load-balancer, and application logs to identify whether the issue is global, regional, or specific to one network path.

Confidentialité et traitement des données

The URL and selected check settings are sent to this site's server so remote probes can request the target. The target site receives the probe request from the selected service region and may record it under its own policies. Do not submit private admin URLs, signed links, internal hostnames, or URLs containing access tokens.

Outils développeur associés

Questions fréquentes

Does a successful HTTP response prove the site is healthy?

No. It proves that the selected probe completed its request and received a response. It does not cover every page, user flow, region, device, or backend dependency.

Why can one region fail while another succeeds?

Regional DNS answers, CDN routing, peering, firewall rules, rate limits, and network congestion can differ. Compare the timing and error stage before changing the origin configuration.

Does the checker crawl the website?

No. It requests the URL you provide and reports the response observed by the selected probes. It does not audit links, accessibility, content, or application security.