← Radar

surriel.com

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 17 probes

Refused

2 of 16 probes over 30 days

Median open time

1209 ms

Last seen

2026-10-28 07:03:26 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.3

Certificate expiry

55 days left

Issuer

YR1

Chain valid

valid

Name matches

matches

HTTP version

1.1

Cipher

TLS_AES_128_GCM_SHA256

Address family

v4

Headers and cookies

Header grade

F

HSTS

not sent

Mixed content

none

Cookie flags

insecure cookie

Redirect hops

2

Exposure check

clean

The request ended at https://surriel.com/Home.

Graded against hg3.

Where the time went

DNS (first request) 0 msConnect (first request) 40 msTLS handshake (first request) 0 msRedirects, then waiting for the first byte 2106 msTransfer 35 ms

2181 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.

17,078 bytes returned, after 2 redirects.

Registration and published DNS

Domain registration

76 days left

Registrar

Domain.com - Network Solutions, LLC

Registered

2000-01-12

DNSSEC

not signed

Registry record read over RDAP on 2026-10-26. 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.