rule34.gg
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
310 ms
Last seen
2026-09-13 04:54:47 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
1.3
Certificate expiry
44 days left
Issuer
WE1
Chain valid
valid
Name matches
matches
HTTP version
2
Cipher
TLS_AES_128_GCM_SHA256
Address family
v4
Headers and cookies
Header grade
F
HSTS
not sent
Mixed content
none
Cookie flags
not measured
Redirect hops
1
Exposure check
clean
The request ended at https://rule34.gg/.
Graded against hg3.
Where the time went
395 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.
36,647 bytes returned, after 1 redirect.
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.