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

leisulivestats.com

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

This reading of leisulivestats.com was taken 12d ago

leisulivestats.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting leisulivestats.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 leisulivestats.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 13:53 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 leisulivestats.com actually stands on - every host below is a signed observation
leisulivestats.com
A / AAAA
177.211.55.52
unattributedserves the site
NS
a.share-dns.comb.share-dns.net
share-dns.com + share-dns.netanswers its DNS
TLS
leisulivestats.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 177.211.55.52

NS 2

  • a.share-dns.com
  • b.share-dns.net

SOA 1

  • a.share-dns.com master.share-dns.com

TLS Certificates (4)

Common NameIssuerExpires
leisulivestats.com C=US, O=Let's Encrypt, CN=YE2 Wed, 09 Sep 2026 06:35:36 +0000
YE2 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_d24d7e7a24a5cb84
Output Hash
9e1be395e87b6bc0562b5cc357401232d3af4c2ecedddd84c20ca305e68ca72f
Signature
ed25519:fa58770ed83e880e3dfbcbf3d79ad8ba00de2fc521f2cbe8156cf4b895c9422ff567a8c6173c4678e241f8599f4b14d2ff9d96b392791f6be8f973f94aae7707
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser