CONTINUOUS INTERNET TELEMETRY24H DRIFT34,617 material changesacross 32,325 domains · 24h to ~3h agoDNS DRIFT49 domains changed DNS providertop destination koaladns.com · +27 vs yesterdayNOW545 curated domains not reachablelast probe, steadySITE ERRORS33,676 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 157,341 sites429 rate-limit / 403 bot-block, a posture signal

vendesaldo.mx

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

This reading of vendesaldo.mx was taken 2d ago

vendesaldo.mx is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting vendesaldo.mx 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 vendesaldo.mx Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
2 subdomains · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 11:12 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 vendesaldo.mx actually stands on - every host below is a signed observation
vendesaldo.mx
A / AAAA
50.28.110.199
unattributedserves the site
NS
ns.liquidweb.comns1.liquidweb.com
liquidweb.comanswers its DNS
MX
vendesaldo.mx
vendesaldo.mxreceives its email
TLS
mail.vendesaldo.mx
Let's Encryptissued its certificate

DNS Records

A 1

  • 50.28.110.199

MX 1

  • 10vendesaldo.mx

TXT 1

  • v=spf1 +mx +a +ip4:50.28.110.199 ~all

NS 2

  • ns.liquidweb.com
  • ns1.liquidweb.com

SOA 1

  • ns.liquidweb.com admin.liquidweb.com

MCP_RECORDS 1

  • v=spf1 +mx +a +ip4:50.28.110.199 ~all

DMARC_RECORDS 1

  • v=DMARC1; p=none;

BIMI_RECORDS 1

  • v=spf1 +mx +a +ip4:50.28.110.199 ~all

MTA_STS_RECORDS 1

  • v=spf1 +mx +a +ip4:50.28.110.199 ~all

TLS Certificates (3)

Common NameIssuerExpires
mail.vendesaldo.mx C=US, O=Let's Encrypt, CN=YR2 Tue, 06 Oct 2026 16:18: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 (2)

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_441db8b4832f5d15
Output Hash
e82c3a59127859feeb901222fb6672126da0cee02ef992ed10e33c4fd6d70df2
Signature
ed25519:45651106af5bb3ed674c0a7ea8b4d8b400fb01e0d0730cebc980d76713836d8f7126fdda9dcd6c58fb74ef703161dc7298e597af395e1a1cc32aec1743732e0e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser