farfetch.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
403 — refused
Answered
88% of 8 probes
Refused
4 of 8 probes over 30 days
Median open time
1898 ms
Last seen
2026-10-30 06:19:58 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.farfetch.com/, which answered 403.
4 of our 8 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
118 days left
Issuer
DigiCert Global G3 TLS ECC SHA384 2020 CA1
Chain valid
valid
Name matches
matches
HTTP version
2
Cipher
TLS_AES_256_GCM_SHA384
Address family
v4
Headers and cookies
Header grade
not measured
HSTS
not measured
Mixed content
not measured
Cookie flags
not measured
Redirect hops
1
Exposure check
not measured
The request ended at https://www.farfetch.com/. 7 of the 7 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
170 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.
368 bytes returned, after 1 redirect.
Registration and published DNS
Domain registration
207 days left
Registrar
Lexsynergy Limited
Registered
2003-05-29
DNSSEC
signed
SPF
softfail
DMARC
reject
Accepts mail
MX published
Registry record read over RDAP on 2026-11-01. SPF and DMARC read from public DNS on 2026-10-19. 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.