mauvecloud.net

Observed Aug 10, 2026, 08:18 UTC (5d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of mauvecloud.net was taken 5d ago

mauvecloud.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting mauvecloud.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 mauvecloud.net Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
1 subdomain · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-14 14:09 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 mauvecloud.net actually stands on - every host below is a signed observation
mauvecloud.net
A / AAAA
20.121.56.79
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
www.mauvecloud.net
Let's Encryptissued its certificate

DNS Records

A 1

  • 20.121.56.79

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.mauvecloud.net

MCP_RECORDS 1

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

DMARC_RECORDS 1

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

BIMI_RECORDS 1

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

MTA_STS_RECORDS 1

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

TLS Certificates (3)

Common NameIssuerExpires
www.mauvecloud.net C=US, O=Let's Encrypt, CN=YR2 Tue, 15 Sep 2026 02:43:30 +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 (1)

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_50ba557e414302aa
Output Hash
b39fdb868126a104a0e67c4a26d1f9d3dbd5d65c749f8918be87a0eb3157d6f6
Signature
ed25519:ded61813d6215ff4662be4c65824d1e68fc61836b3a6b3e1a54421a2cd5f0d867e58d87ac5873f32ab6aa35d9ebf102fe8a2f159b7d37c9e244d1689deec8704
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT42,410 material changesacross 40,833 domains · 24h to ~80m ago · -1,097 vs yesterdayROTATION60 domains moved DNS from magpiedns.com to koaladns.com, 57 moved backa rotation loop, not a migration · 24hNOW495 curated domains not reachablelast probe, steadySITE ERRORS36,296 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,237 sites429 rate-limit / 403 bot-block, a posture signal