CONTINUOUS INTERNET TELEMETRY24H DRIFT27,060 material changesacross 26,158 domains · 24h to ~13h ago · -10,962 vs yesterdayROTATION58 domains moved DNS from kirklanddc.com to koaladns.com, 54 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW561 curated domains not reachable+30 vs yesterdaySITE ERRORS33,742 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,733 sites429 rate-limit / 403 bot-block, a posture signal

librio.net

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

This reading of librio.net was taken 4d ago

librio.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting librio.net 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 librio.net Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 21:50 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 librio.net actually stands on - every host below is a signed observation
librio.net
A / AAAA
103.224.182.253
unattributedserves the site
NS
ns1.abovedomains.comns2.abovedomains.com
abovedomains.comanswers its DNS
MX
alltheemails.com
alltheemails.comreceives its email
TLS
mybutcher.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 103.224.182.253

MX 1

  • 10alltheemails.com

TXT 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

NS 2

  • ns1.abovedomains.com
  • ns2.abovedomains.com

SOA 1

  • ns1.abovedomains.com hostmaster.trellian.com

MCP_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

DMARC_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

BIMI_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

MTA_STS_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

TLS Certificates (3)

Common NameIssuerExpires
mybutcher.com C=US, O=Let's Encrypt, CN=YR2 Tue, 06 Oct 2026 12:37:38 +0000
YR2 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 (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_8b69e56e7b20a430
Output Hash
7821b14600fb4e6e87336edd523f9010056a7170b4dc4d8863c61c168744ce61
Signature
ed25519:23a21370cad2467892369a0e7a3c8b662761104db9911e6bd9596e3162977874ac403ae331e1634375fa502bc2f50ac422e7624ed1d5c9d0053693022638340c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser