CONTINUOUS INTERNET TELEMETRY24H DRIFT29,105 material changesacross 28,144 domains · 24h to ~13h ago · -8,917 vs yesterdayROTATION58 domains moved DNS from kirklanddc.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW560 curated domains not reachable+29 vs yesterdaySITE ERRORS33,740 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,660 sites429 rate-limit / 403 bot-block, a posture signal

leblanc.io

Observed Aug 6, 2026, 05:43 UTC (22h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Not responding
Secured byLet's Encrypt
IPv6 · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 05:43 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 leblanc.io actually stands on - every host below is a signed observation
leblanc.io
A / AAAA
51.75.144.1742001:41d0:700:1dae::
2001serves the site
NS
ns106.ovh.netdns106.ovh.net
ovh.netanswers its DNS
MX
mx1.ovh.netmx2.ovh.netmxb.ovh.net
ovh.netreceives its email
TLS
leblanc.io
Let's Encryptissued its certificate

DNS Records

A 1

  • 51.75.144.174

AAAA 1

  • 2001:41d0:700:1dae::

MX 3

  • 1mx1.ovh.net
  • 5mx2.ovh.net
  • 100mxb.ovh.net

TXT 2

  • v=spf1 a mx include:mx.ovh.com -all
  • keybase-site-verification=wWZmxoHCXX_wF_ta2kl_ZQrD3UicYjgxuentQVyRxQQ

NS 2

  • ns106.ovh.net
  • dns106.ovh.net

SOA 1

  • dns106.ovh.net tech.ovh.net

MCP_RECORDS 1

  • v=spf1 a ra=postmaster -all

DMARC_RECORDS 1

  • v=spf1 a ra=postmaster -all

BIMI_RECORDS 1

  • v=spf1 a ra=postmaster -all

MTA_STS_RECORDS 1

  • v=spf1 a ra=postmaster -all

TLS Certificates (4)

Common NameIssuerExpires
leblanc.io C=US, O=Let's Encrypt, CN=YE1 Mon, 21 Sep 2026 18:51:58 +0000
YE1 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 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_44625b594eb79982
Output Hash
146ac69a287c12e9e5d06d85cf73c97e3d7efa7fbfae6c4984891d5c48552db5
Signature
ed25519:9dc8b5bea92c1152232993c0ee8771b628684eb134109dfbab1b5bbcbf996a6fcf7437f097282550f147b428262460bd985d05988ecf3cb180447c13d6078f0e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser