google.com.af
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 6 probes
Median open time
91 ms
Last seen
2026-09-13 04:54:39 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.
Transport
TLS
not measured
Certificate expiry
no certificate inspected
Issuer
not measured
Chain valid
not measured
Name matches
not measured
HTTP version
1.1
Cipher
not measured
Address family
v4
Headers and cookies
Header grade
F
HSTS
not sent
Mixed content
not measured
Cookie flags
insecure cookie
Redirect hops
2
Exposure check
not measured
The request ended at http://www.google.com/. 6 of the 6 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
102 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.
83,373 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.