CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 14,671 material changesacross 14,104+ domains · 24h to ~8h ago · a floor, 16h of 24 walkedDNS DRIFT1 domain changed DNS providertop destination koaladns.comNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,304 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,289 sites429 rate-limit / 403 bot-block, a posture signalMOVERokta.comNo mail routes in the latest observation

vajra.me

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

This reading of vajra.me was taken 1d ago

vajra.me is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting vajra.me 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 vajra.me Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCloudflare
Secured byGoogle Trust Services
IPv6 · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 18:10 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 vajra.me actually stands on - every host below is a signed observation
vajra.me
A / AAAA
172.67.128.169104.21.2.342606:4700:3033::ac43:80a92606:4700:3036::6815:222
Cloudflareserves the site
NS
elle.ns.cloudflare.comhugh.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
mx1.privateemail.commx2.privateemail.com
privateemail.comreceives its email
TLS
vajra.me
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 172.67.128.169
  • 104.21.2.34

AAAA 2

  • 2606:4700:3033::ac43:80a9
  • 2606:4700:3036::6815:222

MX 2

  • 10mx1.privateemail.com
  • 10mx2.privateemail.com

TXT 2

  • keybase-site-verification=qMUA5OUSxp0LTnBwhk06TvogcKQcRK2ln2iOMGuM_io
  • v=spf1 include:spf.privateemail.com ~all

NS 2

  • elle.ns.cloudflare.com
  • hugh.ns.cloudflare.com

SOA 1

  • elle.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 2

  • keybase-site-verification=qMUA5OUSxp0LTnBwhk06TvogcKQcRK2ln2iOMGuM_io
  • v=spf1 include:spf.privateemail.com ~all

DMARC_RECORDS 2

  • keybase-site-verification=qMUA5OUSxp0LTnBwhk06TvogcKQcRK2ln2iOMGuM_io
  • v=spf1 include:spf.privateemail.com ~all

BIMI_RECORDS 2

  • keybase-site-verification=qMUA5OUSxp0LTnBwhk06TvogcKQcRK2ln2iOMGuM_io
  • v=spf1 include:spf.privateemail.com ~all

MTA_STS_RECORDS 2

  • keybase-site-verification=qMUA5OUSxp0LTnBwhk06TvogcKQcRK2ln2iOMGuM_io
  • v=spf1 include:spf.privateemail.com ~all

TLS Certificates (3)

Common NameIssuerExpires
vajra.me C=US, O=Google Trust Services, CN=WE1 Mon, 19 Oct 2026 05:08:00 +0000
WE1 C=US, O=Google Trust Services LLC, CN=GTS Root R4 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R4 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_f195ea17b1fab70b
Output Hash
1c8f5d66dc2ed1906d47b2ae0d643998274ddd51dc70ed67bfa87963225627d1
Signature
ed25519:17a0c6f4e46ecd018dff0ee9ed9773188a4924b740700a51bde9d9e465b5ae68432b4ff8b62b08fd6b3c921859e3c9a3ea83ecaf2b19379e256f514fbc64b608
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser