CloudForge
Ask

Availability diagnostic tool

Azure Endpoint Health and HTTPS Checker

Enter a public Azure or internet endpoint to inspect its external response. The checker validates every destination and blocks private, local, metadata, and non-standard-port requests.

Free and guest-ready

No sign-in is required. Review every result before using it in a production environment.

Check a public endpoint

HTTP or HTTPS on standard ports only.

Private IP ranges, localhost, metadata services, embedded credentials, unsafe redirects, and non-standard ports are blocked.

External health result

Run a check to inspect status, timing, redirects, headers, and TLS.
HTTP status and response timing
Safe redirect-chain inspection
DNS address and selected headers
TLS certificate expiry information

What the endpoint health checker measures

The checker sends a short server-side request to a public HTTP or HTTPS URL and reports the status returned to CloudForge. It records response time, redirect steps, the resolved public IP address, selected diagnostic headers, and available TLS certificate dates for HTTPS endpoints.

This is an external observation from the CloudForge hosting location. It can confirm that an endpoint responds publicly, but it does not represent every user location, private network, DNS resolver, authentication flow, or application transaction.

Understanding HTTP and HTTPS results

A 2xx response normally indicates that the requested operation succeeded. A 3xx response redirects the client. A 4xx response indicates that the request was rejected or the resource was unavailable, while a 5xx response indicates a server or upstream failure. Authentication-protected endpoints can be healthy while returning 401 or 403 to an anonymous check.

Response time includes DNS, connection, TLS, and server response time as observed by this checker. Use Application Insights, Azure Monitor, Front Door metrics, Application Gateway logs, or another monitoring platform for continuous and geographically distributed measurements.

  • Compare the default Azure hostname with the custom domain.
  • Review every redirect for an unexpected host or protocol downgrade.
  • Track certificate expiry with monitored alerts rather than manual checks alone.
  • Treat anonymous 401 or 403 responses according to the endpoint's access design.

Security boundaries and limitations

CloudForge accepts only public HTTP and HTTPS destinations on standard ports. Localhost, private IP ranges, link-local addresses, cloud metadata addresses, embedded credentials, and unsafe redirect targets are blocked. These restrictions protect the service and are not configurable from the tool.

The checker does not bypass authentication, firewalls, WAF rules, private endpoints, client certificates, or network controls. Do not use it for load testing. A single successful request is useful evidence, not proof of ongoing availability.

Frequently asked questions

Can the checker test a private endpoint?

No. Private, loopback, link-local, and internal destinations are intentionally blocked.

Why does a healthy application return 401 or 403?

The checker is anonymous. An endpoint that requires authentication or restricts the CloudForge source network can correctly return 401 or 403.

Is this a replacement for Azure Monitor availability tests?

No. It is an on-demand diagnostic check. Use monitored, scheduled, and multi-location availability testing for production alerting.