tracker.cl
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 5 probes
Median open time
286 ms
Last seen
2026-09-13 04:54:57 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
not measured
Redirect hops
0
Exposure check
clean
The request ended at http://tracker.cl/.
Graded against hg3.
Where the time went
272 ms in total, from one request. Transfer is the remainder after the first byte rather than a separately measured phase.
2,875 bytes returned.
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.