CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 24,136 material changesacross 23,195+ domains · 24h to ~12h ago · a floor, 12h of 24 walkedDNS DRIFT78 domains changed DNS providertop destination koaladns.com · +2 vs yesterdayNOW587 curated domains not reachable+56 vs yesterdaySITE ERRORS33,537 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,460 sites429 rate-limit / 403 bot-block, a posture signal

live-hub.net

Observed Aug 3, 2026, 01:11 UTC (5d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of live-hub.net was taken 5d ago

live-hub.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting live-hub.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 live-hub.net Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Not responding
Email byAmazon SES
Registered withSafeNames Ltd.
tranco_100k
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 05:59 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 live-hub.net actually stands on - every host below is a signed observation
live-hub.net
NS
ns-1291.awsdns-33.orgns-191.awsdns-23.comns-2034.awsdns-62.co.ukns-637.awsdns-15.net
awsdns-33.org + awsdns-23.com + moreanswers its DNS
MX
inbound-smtp.eu-west-1.amazonaws.com
Amazon SESreceives its email

DNS Records

MX 1

  • 10inbound-smtp.eu-west-1.amazonaws.com

TXT 1

  • v=spf1 include:amazonses.com ~all

NS 4

  • ns-1291.awsdns-33.org
  • ns-191.awsdns-23.com
  • ns-2034.awsdns-62.co.uk
  • ns-637.awsdns-15.net

SOA 1

  • ns-2034.awsdns-62.co.uk awsdns-hostmaster.amazon.com

MCP_RECORDS 1

  • _xp25k7wwmerxahl0jq39y6ma9lvmiyh

DMARC_RECORDS 1

  • _xp25k7wwmerxahl0jq39y6ma9lvmiyh

BIMI_RECORDS 1

  • _xp25k7wwmerxahl0jq39y6ma9lvmiyh

MTA_STS_RECORDS 1

  • _xp25k7wwmerxahl0jq39y6ma9lvmiyh

TLS Certificates (0)

None.

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_511fa6a5c1f62473
Output Hash
7cd55b3f39bc0da59b3bd4f70cee3313dbce726eec46d1db0482ae1c29636f71
Signature
ed25519:2d2c8211482b1ebc0ea0a6186462b34217ecff2c43ec6b68abd1f69eb636e1b6e8d760f186a918d4589812c09c72f011df0d841550df0c1efd4a18d0f32a3d07
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser