CONTINUOUS INTERNET TELEMETRY24H DRIFT33,779 material changesacross 31,481 domains · 24h to ~2h agoDNS DRIFT56 domains changed DNS providertop destination koaladns.com · +34 vs yesterdayNOW556 curated domains not reachablelast probe, steadySITE ERRORS33,680 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 157,156 sites429 rate-limit / 403 bot-block, a posture signal

ysfine.com

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

This reading of ysfine.com was taken 2d ago

ysfine.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting ysfine.com 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 ysfine.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
Registered withTUCOWS.COM, CO.
5 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 15:32 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 ysfine.com actually stands on - every host below is a signed observation
ysfine.com
A / AAAA
172.203.251.89
unattributedserves the site
NS
ns2.turbify.comns1.turbify.com
turbify.comanswers its DNS
MX
mx-biz.mail.am0.yahoodns.netmx-biz.mail.am0.yahoodns.net
yahoodns.netreceives its email
TLS
ysfine.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 172.203.251.89

MX 2

  • 20mx-biz.mail.am0.yahoodns.net
  • 30mx-biz.mail.am0.yahoodns.net

NS 2

  • ns2.turbify.com
  • ns1.turbify.com

SOA 1

  • ns1.turbify.com hostmaster.ysfine.com

MCP_RECORDS 1

  • v=spf1 a mx ip4:172.203.251.89 include:relay.mailchannels.net -all

DMARC_RECORDS 1

  • v=spf1 a mx ip4:172.203.251.89 include:relay.mailchannels.net -all

BIMI_RECORDS 1

  • v=spf1 a mx ip4:172.203.251.89 include:relay.mailchannels.net -all

MTA_STS_RECORDS 1

  • v=spf1 a mx ip4:172.203.251.89 include:relay.mailchannels.net -all

TLS Certificates (3)

Common NameIssuerExpires
ysfine.com C=US, O=Let's Encrypt, CN=YR2 Wed, 21 Oct 2026 20:41:16 +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 (5)

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_4512776dc7cd4887
Output Hash
1b1a7ee5bef444c4465d3027f9d24c6513b8083a0d21db16d9da039b930910f2
Signature
ed25519:3db525807c2ba28de7c305d876374cafe8299c3310eafdb72bb8f32db185e3b960bd312b75fe15ae17b1529a5e3ad52846f4838bafc7f785bd176feb78defa0e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser