CONTINUOUS INTERNET TELEMETRY24H DRIFT5,762 material changesacross 5,364 domains · 24h to ~20m ago · -3,001 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

zenpayments.com

Observed Aug 2, 2026, 22:07 UTC (5h 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.

Guarded by a firewall
Email byMicrosoft 365
Secured byLet's Encrypt
Also usesFacebook/MetaGoogle Search Console
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 22:07 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 zenpayments.com actually stands on - every host below is a signed observation
zenpayments.com
A / AAAA
76.76.21.21
unattributedserves the site
NS
ns2.hover.comns1.hover.com
hover.comanswers its DNS
MX
zenpayments-com.mail.protection.outlook.com
Microsoft 365receives its email
TLS
zenpayments.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 76.76.21.21

MX 1

  • 0zenpayments-com.mail.protection.outlook.com

TXT 6

  • facebook-domain-verification=ri7j5yo5e87x637qd3ajj9ng40dh1t
  • google-site-verification=iRAGpb_w0M36EfkIIxfj6IUL23NVGF2Vkp_01YhEQOA
  • v=spf1 +a +mx include:_spf.safewebservices.com include:spf.protection.outlook.com include:trustpilotservice.com include:_spf.salesforce.com include:spf-westus.emailsignatures365.com ~all
  • apple-domain-verification=3tUVW7pCDrjN815g
  • MS=ms39874896
  • google-site-verification=9di73v8MYP0fgLaHNSCtBRMFdiiE0VmRMUkhh7cAXlY

NS 2

  • ns2.hover.com
  • ns1.hover.com

SOA 1

  • ns1.hover.com dnsmaster.hover.com

MCP_RECORDS 1

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

DMARC_RECORDS 1

  • v=DMARC1;p=quarantine;rua=mailto:dmarc@zenpayments.com,mailto:4511dcb81a@rua.easydmarc.us;ruf=mailto:dmarc@zenpayments.com,mailto:4511dcb81a@ruf.easydmarc.us;fo=1;

BIMI_RECORDS 1

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

MTA_STS_RECORDS 1

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

TLS Certificates (3)

Common NameIssuerExpires
zenpayments.com C=US, O=Let's Encrypt, CN=YR2 Sun, 20 Sep 2026 00:31:31 +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 (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_744af776bee7b7b1
Output Hash
e5d0e051ac55f777186b5db7d214a3951ccef77ed2c99933d4944bc9c8e11016
Signature
ed25519:b0408d58c20665336cd358250df1dba26e442468d10841bac1f051f6b31be15313b6564d9d1cbd904f94c25195d52d3ffde4b8c0ecc878b7abe4a4a0a36ed400
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser