gismeteo.kz

What our own request to this host returned, over the last 30 days. Nothing here was tested for weaknesses and nothing was captured from anyone else's traffic.

Last status

200

Answered

100% of 2 probes

Refused

none of 2 probes over 30 days

Median open time

6288 ms

Last seen

2026-09-13 06:14:32 UTC

“Answered” is how often our own request got a response, from one region at one probe per day. It is not an uptime figure and must not be read as one. A refusal is a response, so a refused probe counts as answered. "Refused" counts the probes whose answer was 403 or 429.

Transport

TLS

1.2

Certificate expiry

166 days left

Issuer

GlobalSign GCC R46 AlphaSSL CA 2025

Chain valid

valid

Name matches

matches

HTTP version

Cipher

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

Address family

Headers and cookies

Header grade

HSTS

sent

Mixed content

not measured

Cookie flags

insecure cookie

Redirect hops

Exposure check

not measured

The request ended at https://www.gismeteo.kz/. 2 of the 2 probes that got a response ended on a different host, so the fields above may describe that host rather than this one.

Graded against hg3.

Where the time went

DNS (first request) 0 msConnect (first request) 209 msTLS handshake (first request) 0 msRedirects, then waiting for the first byte 2307 msTransfer 417 ms

2933 ms in total, across 3 requests — the first and 2 redirects. Transfer is the remainder after the first byte rather than a separately measured phase.

Only the first request’s DNS, connection and TLS are timed separately, so that segment is not server think-time alone: it carries the other 2 requests and anything else between the first connection and the first byte.

The TLS handshake reads 0 ms because the first request was plain HTTP, so there was no handshake to time. The TLS version and certificate above are from the HTTPS hop the origin redirected to, which is a different connection from the one timed here.

150,733 bytes returned, after 2 redirects. The body hit our read cap, so that is a floor and not the size of the response.

Registration and published DNS

This top-level domain publishes no RDAP service, so there is no registry record for us to read.

Registry record read over RDAP on 2026-09-13. Neither involves a request to this host, and neither is a test: we read what the registry and the domain’s own DNS publish. A published policy is not evidence about what a mail receiver would actually do.

By observer region

Measured from one region. The per-region comparison §5.5 describes needs more than one, and the deployment has one today.