tui.co.uk

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

403 — refused

Answered

60% of 5 probes

Refused

2 of 4 probes over 30 days

Median open time

9135 ms

Last seen

2026-10-26 07:08:45 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.

Our last probe was refused

Our request was refused at an address this host chose: after 1 redirect it ended at https://www.tui.co.uk/, which answered 403.

2 of our 4 probes over the last 30 days were refused.

We never asked for a particular page: each probe is one request, from one region, to the hostname's front door, following whatever redirects the host sends. A refusal is an answer rather than a failure to answer, and we do not record what made it — so this is not a measurement of whether the site works for anyone else.

Transport

TLS

1.3

Certificate expiry

99 days left

Issuer

Thawte TLS ECC CA G1

Chain valid

valid

Name matches

matches

HTTP version

Cipher

TLS_AES_256_GCM_SHA384

Address family

Headers and cookies

Header grade

not measured

HSTS

not measured

Mixed content

not measured

Cookie flags

not measured

Redirect hops

Exposure check

not measured

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

Where the time went

DNS (first request) 0 msConnect (first request) 18 msTLS handshake (first request) 0 msRedirects, then waiting for the first byte 9349 msTransfer 33 ms

9400 ms in total, across 2 requests — the first and 1 redirect. 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 request 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.

365 bytes returned, after 1 redirect.

Registration and published DNS

Domain registration

386 days left

Registrar

CSC Corporate Domains, Inc

Registered

1994-11-19

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.