CONTINUOUS INTERNET TELEMETRY24H DRIFT37,653 material changesacross 34,127 domains · 24h to ~20m agoDNS DRIFT55 domains changed DNS providertop destination koaladns.com · +33 vs yesterdayNOW556 curated domains not reachablelast probe, steadySITE ERRORS33,351 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,386 sites429 rate-limit / 403 bot-block, a posture signal

va2dfk.com

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

This reading of va2dfk.com was taken 2d ago

va2dfk.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting va2dfk.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 va2dfk.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
1 subdomain · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 08: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 va2dfk.com actually stands on - every host below is a signed observation
va2dfk.com
A / AAAA
69.51.231.221
unattributedserves the site
NS
ns2.no-ip.comns1.no-ip.comns4.no-ip.comns3.no-ip.com+1 more
no-ip.comanswers its DNS
MX
mail.va2dfk.com
va2dfk.comreceives its email
TLS
va2dfk.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 69.51.231.221

MX 1

  • 10mail.va2dfk.com

TXT 1

  • v=spf1 ip4:148.113.192.43 a:mail.va2dfk.com mx -all

NS 5

  • ns2.no-ip.com
  • ns1.no-ip.com
  • ns4.no-ip.com
  • ns3.no-ip.com
  • ns5.no-ip.com

SOA 1

  • ns2.no-ip.com hostmaster.no-ip.com

MCP_RECORDS 1

  • v=spf1 ip4:148.113.192.43 a:mail.va2dfk.com mx -all

DMARC_RECORDS 1

  • v=DMARC1; p=quarantine; rua=postmaster@va2dfk.com; adkim=r; aspf=r; ri=86400; pct=100; fo=1:d

BIMI_RECORDS 1

  • v=spf1 ip4:148.113.192.43 a:mail.va2dfk.com mx -all

MTA_STS_RECORDS 1

  • v=spf1 ip4:148.113.192.43 a:mail.va2dfk.com mx -all

TLS Certificates (4)

Common NameIssuerExpires
va2dfk.com C=US, O=Let's Encrypt, CN=YE2 Thu, 10 Sep 2026 10:33:38 +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 (1)

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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_1b40b280cbcec632
Output Hash
2ab767af23e77fb4fbcff2ff03873f1d1d547ee989618cb8bdbb788a6ebb7fb0
Signature
ed25519:32d09a25f28633d16d677fc6e2ed79df1aed5d2dd17979abaf54802c9c620186d056ea70a44181705f733bbee9647a158527ec756971849233d7b92fdf1a540d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser