CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 24,136 material changesacross 23,195+ domains · 24h to ~12h ago · a floor, 12h of 24 walkedROTATION48 domains moved DNS from koaladns.com to kirklanddc.com, 46 moved backa rotation loop, not a migration · 24hNOW592 curated domains not reachablelast probe, steadySITE ERRORS33,533 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,513 sites429 rate-limit / 403 bot-block, a posture signal

linkwhats.app

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

This reading of linkwhats.app was taken 5d ago

linkwhats.app is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting linkwhats.app 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 linkwhats.app Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
IPv6 · 1 subdomain · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 05:19 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 linkwhats.app actually stands on - every host below is a signed observation
linkwhats.app
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
eegs.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
eegs.com C=US, O=Let's Encrypt, CN=YR2 Mon, 05 Oct 2026 09:30:01 +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_efd2de8d83e3c5de
Output Hash
18e55e52b3c7cd7b23fa365eb43f2328e610b1414495c80aa7763a027105459b
Signature
ed25519:9e9b279f46648261843d483e5d633f75188f34900d469566bec9710d318c9044b793ce73472d9098b02ae1ac704cacf836303a3f35837b10fc5fa9666b382a02
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser