sassyclassy.de

Observed Aug 11, 2026, 04:17 UTC (4d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of sassyclassy.de was taken 4d ago

sassyclassy.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting sassyclassy.de 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 sassyclassy.de Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCloudflare
Email byZendesk
Secured byLet's Encrypt
Also usesFacebook/MetaGoogle Search ConsoleAppleKlaviyo
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-15 00:53 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 sassyclassy.de actually stands on - every host below is a signed observation
sassyclassy.de
A / AAAA
23.227.38.65
Cloudflareserves the site
NS
ns22.domaincontrol.comns21.domaincontrol.com
domaincontrol.comanswers its DNS
MX
mx0.sassyclassy.de
Zendeskreceives its email
TLS
sassyclassy.de
Let's Encryptissued its certificate

DNS Records

A 1

  • 23.227.38.65

MX 1

  • 50mx0.sassyclassy.de

TXT 6

  • v=spf1 include:spf.server-he.de include:shops.shopify.com include:mail.zendesk.com -all
  • facebook-domain-verification=dyupvopul00qcs5nvnu8c801zbb4n8
  • google-site-verification=vbaZfwTrYT1LJnPYQC04jbNgiq0qYWN5aQOQh16tetc
  • apple-domain-verification=GDZghB5qcoxK0UEW
  • google-site-verification=MJHbDggjht1bc_nTtaXZMUfGpwn4ow9LgRE4yoJnK5A
  • klaviyo-site-verification=K65bfe

NS 2

  • ns22.domaincontrol.com
  • ns21.domaincontrol.com

SOA 1

  • ns21.domaincontrol.com dns.jomax.net

MCP_RECORDS 1

  • klaviyo-site-verification=K65bfe

DMARC_RECORDS 1

  • v=DMARC1; p=none

BIMI_RECORDS 1

  • klaviyo-site-verification=K65bfe

MTA_STS_RECORDS 1

  • klaviyo-site-verification=K65bfe

TLS Certificates (4)

Common NameIssuerExpires
sassyclassy.de C=US, O=Let's Encrypt, CN=YE2 Mon, 14 Sep 2026 21:05:35 +0000
YE2 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_9b1c3b8055a22419
Output Hash
f62edbc7c965b63060f0d517e6d93bfbe3e5183984155d9e7ddcdfdd2fab5ae9
Signature
ed25519:c8f981d0ea6b61b8f68dca54e7e130e5a4963988110c5de5c010702a9c183f1acdcd7ee366a4c3f0490200ac2205122e66b71ba2a51c88dfd3c1d7075ec65402
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT42,439 material changesacross 40,751 domains · 24h to ~3h ago · -1,068 vs yesterdayROTATION59 domains moved DNS from koaladns.com to magpiedns.com, 58 moved backa rotation loop, not a migration · 24hNOW494 curated domains not reachablelast probe, steadySITE ERRORS36,315 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,316 sites429 rate-limit / 403 bot-block, a posture signal