Check types

The worker resolves your target hostname to its IP addresses and records how long that took. The result includes the resolved addresses (resolved_ips) and the resolution time (dns_ms). A hostname can resolve to more than one IP, so results always list all of them.

Next, the worker opens a TCP connection to one of the resolved IPs on the target port. This step also validates that the port and the resolved IP are allowed before connecting. The time to establish the connection is recorded as tcp_connect_ms.

For HTTPS targets, the worker performs a TLS handshake and records how long it took as tls_handshake_ms. It also captures the certificate details in the ssl field, including the issuer, subject, subject alternative names, validity window, and fingerprints — useful for spotting an expired or mismatched certificate before it becomes an outage.

Finally, the worker sends the HTTP request — GET, HEAD, or POST — and records the response status (http_status), the response headers, and time to first byte (ttfb_ms). For JSON and XML responses, the body is captured up to your plan's size cap so you can inspect the actual payload, not just the status.

Some targets block plain HTTP clients but work fine in a real browser. If a request comes back with a 401 or 403, or a TLS or HTTP error, RegionCheck retries it with a browser-impersonation fallback. Which path produced the result is reported in http_via, so you can tell whether the primary request succeeded or the fallback was needed.