CONTINUOUS INTERNET TELEMETRY24H DRIFT62,563 material changesacross 59,341 domains · 24h to ~2h ago · +27,946 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW536 curated domains not reachablelast probe, steadySITE ERRORS33,804 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 130,707 sites429 rate-limit / 403 bot-block, a posture signal

varzeshtv.ir

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

This reading of varzeshtv.ir was taken 3d ago

varzeshtv.ir is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting varzeshtv.ir 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 varzeshtv.ir 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
Signed observation on record.
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 03:58 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 varzeshtv.ir actually stands on - every host below is a signed observation
varzeshtv.ir
A / AAAA
77.36.149.91
unattributedserves the site
MX
mxb.irib.irmxa.irib.ir
irib.irreceives its email

DNS Records

A 1

  • 77.36.149.91

MX 2

  • 10mxb.irib.ir
  • 10mxa.irib.ir

TXT 3

  • actalis-dcv=YLQLHc8dko3pQb5vZvgWfaS
  • 525fff98fab3880f8070e732ab20408a4007ecfeac170280b221ce3b325cf70
  • v=spf1 mx -all

SOA 1

  • ns1.irib.ir hostmaster.irib.ir

MCP_RECORDS 1

  • actalis-dcv=YLQLHc8dko3pQb5vZvgWfaS

DMARC_RECORDS 1

  • v=DMARC1; p=reject; pct=100; rua=mailto:mailauth-rua@irib.ir; ruf=mailto:mailauth-ruf@irib.ir; fo=1

BIMI_RECORDS 1

  • actalis-dcv=YLQLHc8dko3pQb5vZvgWfaS

MTA_STS_RECORDS 1

  • actalis-dcv=YLQLHc8dko3pQb5vZvgWfaS

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_09cde79ffdf95160
Output Hash
c4f72569e440621bdaa6708c3fdf6792dfd1a1270a98c79b7a55cb5ed525da4c
Signature
ed25519:77b506fb086568d273b1c50575bbd2e361d10b7328a4b320a79fa4455fbeff931c6124b86db36c5069f21b25310a71331f09f453c9ada39690e1d96888c4e20d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser