diclib.com

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

This reading of diclib.com was taken 5d ago

diclib.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting diclib.com 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 diclib.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Guarded by a firewall
Runs onCloudflare
Secured byLet's Encrypt
Registered toPersonal data
Registered withRegional Network Information Center, JSC dba RU-CENTER
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for diclib.com 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

Bot-blocked Blocked our probe (WAF / bot protection) 403 blocked by cloudflare - bot protection active
HTTP status403
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time25 ms
DNS resolutionNOERROR
What this reading means

A security layer answered instead of the site. That is a working defence doing its job, and we record it as its own state rather than as a failure.

It does NOT mean the site is down or misconfigured. It also does not mean we were treated as hostile - most rules of this kind refuse every non-browser client alike.

What produces this, in rough order of how often
  • A WAF or bot-management rule refuses non-browser user agents by default.
  • Automated traffic from datacenter networks is challenged as a matter of policy.

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 8

A2AAAA2NS2TXT1SOA1

TLS certificates 0

None.

Subdomains 96

96 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_02303209cff1b2ea
Output Hash
961a9aee58c3019286220e4cdcfb5c50eea7612f6dc6ff262ff07e03967f1ccf
Signature
ed25519:cd64a499da6833c6edb34b8a0be6c00ee668c137203da30a1b10c940de4b7052117b53e5b95f19369ea9b76768a6355b09bd0ca73f6a02626fa7ee69c1d0dc07
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
CONTINUOUS INTERNET TELEMETRY24H DRIFT9,458 material changesacross 8,238 domains · 24h to ~3h ago · +4,231 vs yesterdayROTATION55 domains moved DNS from magpiedns.com to koaladns.com, 54 moved backa rotation loop, not a migration · 24hCERT DRIFT1 domains switched issuing CA24hREGISTRAR DRIFT2 changed registrar24hNOW563 curated domains not reachablelast probe, steadySITE ERRORS18,184 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 80,467 sites429 rate-limit / 403 bot-block, a posture signal