CONTINUOUS INTERNET TELEMETRY24H DRIFT66,120 material changesacross 63,653 domains · 24h to ~4h ago · +31,503 vs yesterdayROTATION56 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW533 curated domains not reachablelast probe, steadySITE ERRORS33,789 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 121,565 sites429 rate-limit / 403 bot-block, a posture signal

zarrabi.info

Observed Jul 27, 2026, 04:18 UTC (10d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of zarrabi.info was taken 10d ago

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

DNS Records

A 1

  • 103.224.182.239

MX 1

  • 10park-mx.above.com

TXT 5

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

NS 2

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

SOA 1

  • ns1.abovedomains.com hostmaster.trellian.com

TLS Certificates (3)

Common NameIssuerExpires
canadago.com C=US, O=Let's Encrypt, CN=YR2 Tue, 06 Oct 2026 02:56:44 +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_5f560a3f6e981462
Output Hash
1b2d403be1368a30b929f738e68f853990b2a0fc130195fd02d42ea3a7be1222
Signature
ed25519:f06ab266e25855ced75a22069bc0916c148de56d1f1372b47bf445903507009dfa3f168f4d9559cb446aabcf24ad4773926411d639869706574928b94d6aba04
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser