← Radar

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

no response — http exchange

Answered

86% of 22 probes

Refused

none of 21 probes over 30 days

Median open time

5973 ms

Last seen

2026-10-28 06:37:12 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 request stopped at: HTTP exchange

The connection was established but no HTTP response was read from it.

This is what happened to one request from one region at one moment. A refusal aimed at our bot, a problem on our own egress and a fault at the host all end at the same stage, and nothing we record separates them — so this is not a claim that the site is down.

Transport

TLS

not measured

Certificate expiry

no certificate inspected

Issuer

not measured

Chain valid

not measured

Name matches

not measured

HTTP version

not measured

Cipher

not measured

Address family

v4

Headers and cookies

Header grade

not measured

HSTS

not measured

Mixed content

not measured

Cookie flags

not measured

Redirect hops

2

Exposure check

not measured

The request ended at https://lazada.com/en/.

Where the time went

DNS (first request) 0 msConnect (first request) 221 msTLS handshake (first request) 0 msRedirects, then waiting for the first byte 0 msTransfer 7050 ms

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

Registration and published DNS

Domain registration

560 days left

Registrar

MarkMonitor Inc.

Registered

2009-08-25

DNSSEC

not signed

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