DNS & network
Resolve public addresses, confirm authoritative nameservers, identify the network owner, and test TCP 443.
Trace a public website request from DNS to the application. Netest checks each critical layer and highlights exactly where the connection breaks.
DNSResolvedTCP / TLSConnectedHTTP503 responseLikely problem: application
Use a domain or complete HTTP/HTTPS URL. Netest safely follows redirects and checks the public endpoint.
Private, local, loopback, multicast, and reserved destinations are blocked.
Run a check to see DNS, network, TLS, HTTP, redirects, and security-header results in one report.
From the Netest server to your application
A website can disappear for very different reasons. DNS may point nowhere, port 443 may be blocked, a certificate may be invalid, or a healthy network may lead to an application returning a 503. This diagnostic checks those dependencies in order, so you can start troubleshooting at the layer that actually failed.
Resolve public addresses, confirm authoritative nameservers, identify the network owner, and test TCP 443.
Inspect certificate health, remaining validity, issuer, chain, and the negotiated TLS connection.
Read the final HTTP status, response time, redirect path, and coverage of core security headers.
Confirm the domain registration, authoritative nameservers, DNSSEC status, and A or AAAA records. Recent changes may still be propagating.
Check port 443 on your firewall, load balancer, CDN origin, hosting service, and web server. A refused connection differs from a timeout.
Review certificate expiry, hostname coverage, intermediate certificates, SNI configuration, and the protocols accepted by the server.
The network path is working. Inspect application, reverse-proxy, upstream, database, capacity, and deployment logs for the returned status.
No. It is a live observation from the Netest server. Regional CDNs, WAF rules, split DNS, VPNs, and local ISP paths can produce different results.
No. An HTTP error proves the request reached a web server. A 404 is usually a route or content issue; a 503 usually means the application or an upstream dependency is unavailable.
No. Private, local, loopback, multicast, and reserved destinations are blocked. Use local diagnostics for internal services.
Redirects are common and often intentional, but a long or unexpected chain adds latency and can reveal a hostname or protocol configuration issue.