CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 15,250 material changesacross 14,659+ domains · 24h to ~6h ago · a floor, 18h of 24 walkedNOW560 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

yhtechdlsips1.net

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

This reading of yhtechdlsips1.net was taken 1d ago

yhtechdlsips1.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting yhtechdlsips1.net 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 yhtechdlsips1.net Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
Secured byZeroSSL GmbH
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 12:02 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 yhtechdlsips1.net actually stands on - every host below is a signed observation
yhtechdlsips1.net
A / AAAA
34.41.139.1932600:1900:4001:96e:8000:1:d846:384d
2600serves the site
NS
ns2.hwrn.netns1.hwrn.net
hwrn.netanswers its DNS
MX
mx1.csof.netmx2.csof.net
csof.netreceives its email
TLS
*.yhtechdlsips1.net
ZeroSSL GmbHissued its certificate

DNS Records

A 1

  • 34.41.139.193

AAAA 1

  • 2600:1900:4001:96e:8000:1:d846:384d

MX 2

  • 10mx1.csof.net
  • 10mx2.csof.net

TXT 1

  • v=spf1 include:_incspfcheck.mailspike.net -all

NS 2

  • ns2.hwrn.net
  • ns1.hwrn.net

SOA 1

  • ns1.hwrn.net hostmaster.hwrn.net

MCP_RECORDS 1

  • v=spf1 include:_incspfcheck.mailspike.net -all

DMARC_RECORDS 1

  • v=spf1 include:_incspfcheck.mailspike.net -all

BIMI_RECORDS 1

  • v=spf1 include:_incspfcheck.mailspike.net -all

MTA_STS_RECORDS 1

  • v=spf1 include:_incspfcheck.mailspike.net -all

TLS Certificates (2)

Common NameIssuerExpires
*.yhtechdlsips1.net C=AT, O=ZeroSSL GmbH, CN=ZeroSSL RSA DV SSL CA 2 Sun, 06 Sep 2026 23:59:59 +0000
ZeroSSL RSA DV SSL CA 2 C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication Root R46 Sun, 23 Sep 2035 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_6c142a8d8a3ec725
Output Hash
b6ed33acf56845822a532d5cb6c6f42e3e9b52229dd99c92bd7b5c3624043d1b
Signature
ed25519:b32e76b158d121786bace00622239dcf1ede0e5448c76260329b92e4dd73e86f6a7b688f2fb0007ec6c32110503cb7ef85a57ef1e23467c58798accea36eb802
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser