CONTINUOUS INTERNET TELEMETRY24H DRIFT31,235 material changesacross 30,192 domains · 24h to ~11h ago · -6,787 vs yesterdayROTATION59 domains moved DNS from kirklanddc.com to koaladns.com, 57 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW552 curated domains not reachablelast probe, steadySITE ERRORS33,788 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,640 sites429 rate-limit / 403 bot-block, a posture signal

lib-ebooks.com

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

This reading of lib-ebooks.com was taken 4d ago

lib-ebooks.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lib-ebooks.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 lib-ebooks.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCloudflare
Secured byGoogle Trust Services
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 19:23 UTC

DomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.

Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.

This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.

INFRASTRUCTURE MAPwhat lib-ebooks.com actually stands on - every host below is a signed observation
lib-ebooks.com
A / AAAA
172.67.175.64104.21.31.702606:4700:3037::6815:1f462606:4700:3031::ac43:af40
Cloudflareserves the site
NS
chase.ns.cloudflare.comdolly.ns.cloudflare.com
cloudflare.comanswers its DNS
TLS
lib-ebooks.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 172.67.175.64
  • 104.21.31.70

AAAA 2

  • 2606:4700:3037::6815:1f46
  • 2606:4700:3031::ac43:af40

TXT 1

  • v=spf1 a -all

NS 2

  • chase.ns.cloudflare.com
  • dolly.ns.cloudflare.com

SOA 1

  • chase.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 1

  • v=spf1 a -all

DMARC_RECORDS 1

  • v=spf1 a -all

BIMI_RECORDS 1

  • v=spf1 a -all

MTA_STS_RECORDS 1

  • v=spf1 a -all

TLS Certificates (3)

Common NameIssuerExpires
lib-ebooks.com C=US, O=Google Trust Services, CN=WE1 Fri, 02 Oct 2026 12:26:35 +0000
WE1 C=US, O=Google Trust Services LLC, CN=GTS Root R4 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R4 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +0000

Subdomains (0)

None observed.

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 Receipt

Receipt ID
rcpt_b126b7886cf006e7
Output Hash
7194f5105a44d3fec3d257d2c3d814802cb52f32073cec08e445a9cfb732d7da
Signature
ed25519:4649161252b26913677eab3d612629457873b2a6aab5655992e1ee1ee4fcae816f8922d030b3bc0592d2c9709ea25383fe4935b9340630256fd5bc1d63499f00
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser