j00nix.co.uk

Observed Aug 28, 2026, 12:43 UTC (3d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of j00nix.co.uk was taken 3d ago

j00nix.co.uk is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting j00nix.co.uk under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.

Watch j00nix.co.uk Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Runs onOVH SAS
Registered with123-Reg Limited t/a 123-reg
IPv6 · 5 subdomains · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for j00nix.co.uk in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.

HTTPS probe

Timed out No response within the timeout Connection timed out - no response within 3s
HTTP status0
Servernot observed
TLS protocolnot observed
TLS issuernot observed
Behind Cloudflareno
Time spent waiting6,200 ms (2 attempts, 3s each) - nothing answered
DNS resolutionNOERROR
What this reading means

Nothing answered on 443 inside our budget: 2 attempts of 3s each, from Cloudflare's network. DNS resolved, so the name and its delegation are fine - the failure is below that, at the connection or HTTP layer.

It does NOT mean the site is down for everyone. Our budget is deliberately tight so a two-million-domain sweep stays affordable, and a site that is merely slow will miss it while working fine in a browser.

Probed from Cloudflare's network. A site can be healthy and still not answer us: use the live checks on the domain page to run the same probe from your own network and compare.

What produces this, in rough order of how often
  • The origin takes longer than 3s to send its first byte - real users see this as a slow site, not a broken one.
  • A firewall DROPS our packets rather than refusing them. A refusal would have come back as "connection refused"; silence is what a drop rule looks like from outside.
  • Traffic from datacenter or cloud networks is filtered. We egress from Cloudflare, which many origins treat differently from a residential connection.
  • An AAAA record is published for an address that is not actually serving, so clients that prefer IPv6 hang.
  • The origin only answers browser-like requests. We identify ourselves as DomainDrift rather than impersonating a browser.

These are the known causes, not a diagnosis of this domain. We recorded that nothing answered; we did not measure why.

Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".

SIGNED-OUT VIEW Provider names, posture and counts are shown. The record values - every DNS answer, each subdomain hostname, raw TXT, IPs, cert names and WHOIS - are the product. Sign in for the full signed record, or use the API with a key.

DNS records 9

A1AAAA1NS2MX1TXT2CAA1SOA1

TLS certificates 0

None.

Subdomains 5

5 subdomain hostnames observed and signed - the list itself is part of the paid record.

The proof

Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; the only network request the check makes is for the published public keys.

Verify this receipt
Ed25519 receiptthe raw cryptographic proof
Receipt ID
rcpt_e303b88882aad210
Output Hash
d13c4ce96480de2c34f741d68d3ec46a71b9cd59e5bab8a4bd684fb3a1376ace
Signature
ed25519:d9e87a4df1995b7ff2ebc4bcd2c0f320e136f1d50f7b5016568a8c41f09bf1185fcf51487f8eae166100fc27bf9d6607cae6851ee07265e213585bf75acfb705
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
CONTINUOUS INTERNET TELEMETRY24H DRIFT4,185 material changesacross 2,433 domains · 24h to ~3h agoROTATION61 domains moved DNS from magpiedns.com to koaladns.com, 53 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT3 changed registrar24hNOW564 curated domains not reachablelast probe, steadySITE ERRORS18,226 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 80,767 sites429 rate-limit / 403 bot-block, a posture signal