CONTINUOUS INTERNET TELEMETRY24H DRIFT7,064 material changesacross 6,687 domains · 24h to ~2h ago · -1,699 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

yeproc.com

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

Up right now
Runs onCloudflare
Email byGoogle Workspace
Secured byGoogle Trust Services
Also usesGoogle Search Console
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 22:40 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 yeproc.com actually stands on - every host below is a signed observation
yeproc.com
A / AAAA
160.153.0.79
Cloudflareserves the site
NS
ns16.domaincontrol.comns15.domaincontrol.com
domaincontrol.comanswers its DNS
MX
alt2.aspmx.l.google.comalt4.aspmx.l.google.comalt1.aspmx.l.google.comaspmx.l.google.com+1 more
Google Workspacereceives its email
TLS
yeproc.com
Google Trust Servicesissued its certificate

DNS Records

A 1

  • 160.153.0.79

MX 5

  • 5alt2.aspmx.l.google.com
  • 10alt4.aspmx.l.google.com
  • 5alt1.aspmx.l.google.com
  • 1aspmx.l.google.com
  • 10alt3.aspmx.l.google.com

TXT 5

  • google-site-verification=zAVVC1PvPb6yDtNjs0P57hBsGMyN_A6IeoSDR69jJ54
  • aceki8k5m2pic4693npi5q49d8
  • MS=ms89716807
  • google-site-verification=P49K0py-bUHZ_6lFfZFZP8Ev6vGRsU6xy5sw3qJnchE
  • google-site-verification=yUt8sE3aFMPWklSsl2Pb7YKoWJZkpVsBA37o13H4c1o

NS 2

  • ns16.domaincontrol.com
  • ns15.domaincontrol.com

SOA 1

  • ns15.domaincontrol.com dns.jomax.net

MCP_RECORDS 1

  • v=spf1 include:_spf.google.com ~all

DMARC_RECORDS 1

  • v=DMARC=1; p=none;

BIMI_RECORDS 1

  • v=spf1 include:_spf.google.com ~all

MTA_STS_RECORDS 1

  • v=spf1 include:_spf.google.com ~all

TLS Certificates (3)

Common NameIssuerExpires
yeproc.com C=US, O=Google Trust Services, CN=WE1 Thu, 03 Sep 2026 13:55:40 +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_2f3128248fb14d9f
Output Hash
73d6e84ebf6902e6b75a13100dd233422c8973253bb39ed872729276b7f5ea61
Signature
ed25519:dece01ac0791265fadcc545649cec07a67198abcbe57c8ac7f322a5b6d724a97421f53c964b6fbea7db947dad35b7268d25a1bcff940e0a005af3c8d91154e05
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser