CONTINUOUS INTERNET TELEMETRY24H DRIFT16,621 material changesacross 15,551 domains · last 24h · +7,858 vs yesterdayNOW560 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

vezpi.com

Observed Aug 2, 2026, 19:50 UTC (17h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Verify this receipt yourself + Watch this domain
Responding, no home page
Secured byLet's Encrypt
2 subdomains · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 19:50 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 vezpi.com actually stands on - every host below is a signed observation
vezpi.com
A / AAAA
82.66.217.150
unattributedserves the site
NS
ns100.ovh.netdns100.ovh.net
ovh.netanswers its DNS
MX
mx1.mail.ovh.netmx2.mail.ovh.netmx3.mail.ovh.net
ovh.netreceives its email
TLS
blog.vezpi.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 82.66.217.150

MX 3

  • 1mx1.mail.ovh.net
  • 5mx2.mail.ovh.net
  • 100mx3.mail.ovh.net

TXT 2

  • 1|www.vezpi.com
  • v=spf1 include:mx.ovh.com -all

NS 2

  • ns100.ovh.net
  • dns100.ovh.net

SOA 1

  • dns100.ovh.net tech.ovh.net

MCP_RECORDS 2

  • 1|www.vezpi.com
  • v=spf1 include:mx.ovh.com -all

DMARC_RECORDS 2

  • 1|www.vezpi.com
  • v=spf1 include:mx.ovh.com -all

BIMI_RECORDS 2

  • 1|www.vezpi.com
  • v=spf1 include:mx.ovh.com -all

MTA_STS_RECORDS 2

  • 1|www.vezpi.com
  • v=spf1 include:mx.ovh.com -all

TLS Certificates (3)

Common NameIssuerExpires
blog.vezpi.com C=US, O=Let's Encrypt, CN=YR1 Mon, 07 Sep 2026 19:05:13 +0000
YR1 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_50e8ded6fab3737e
Output Hash
bd664871ec0d7528e39a796ab2442765a21668aea6092ba87322a361d1f519c8
Signature
ed25519:0c15784fa280da3a2c3aca76302be6355f70a105b4a00652afa4247729e7f9b9da94618f3a7cc645852c218f9dffa6a67a4cbedc373fc88e54ca244b434c1202
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser