CONTINUOUS INTERNET TELEMETRY24H DRIFT21,097 material changesacross 19,583 domains · 24h to ~3h agoROTATION57 domains moved DNS from koaladns.com to kirklanddc.com, 55 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination ~NOW603 curated domains not reachablelast probe, steadySITE ERRORS33,520 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,157 sites429 rate-limit / 403 bot-block, a posture signal

libros.com

Observed Jul 26, 2026, 03:41 UTC (13d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of libros.com was taken 13d ago

libros.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting libros.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 libros.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Email byGoogle Workspace
Secured byLet's Encrypt
Registered withAmazon Registrar, Inc.
1 subdomain · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 05:34 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 libros.com actually stands on - every host below is a signed observation
libros.com
A / AAAA
51.89.65.37
unattributedserves the site
NS
dns18.ovh.netns18.ovh.net
ovh.netanswers its DNS
MX
alt2.aspmx.l.google.comalt1.aspmx.l.google.comalt3.aspmx.l.google.comaspmx.l.google.com+1 more
Google Workspacereceives its email
TLS
libros.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 51.89.65.37

MX 5

  • 5alt2.aspmx.l.google.com
  • 5alt1.aspmx.l.google.com
  • 10alt3.aspmx.l.google.com
  • 0aspmx.l.google.com
  • 10alt4.aspmx.l.google.com

TXT 7

  • v=spf1 include:sendgrid.net ~all
  • v=spf1 include:mail.zendesk.com ?all
  • v=spf1 +a +mx -all
  • v=DMARC1; p=none
  • v3e6tsb3qj1irhnee0k4cc844a
  • v3e6tsb3qj1irhnee0k4cc844a
  • v3e6tsb3qj1irhnee0k4cc844a

NS 2

  • dns18.ovh.net
  • ns18.ovh.net

SOA 1

  • dns18.ovh.net tech.ovh.net

TLS Certificates (3)

Common NameIssuerExpires
libros.com C=US, O=Let's Encrypt, CN=YR1 Sun, 11 Oct 2026 23:01:00 +0000
YR1 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (1)

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_1e2d6a052da78e7e
Output Hash
72a2558654f028b42d75483e9dc322399e34b3c43a989846f53ad0d81df40086
Signature
ed25519:88153c920c40be00cada48fbe19d1f0f045d8393f06aa1bf3cca90287cc923a15f260ed139a9e6f8aee51c493e1a33fa854322b9b19d89f4e2ac657a42afab0e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser