CONTINUOUS INTERNET TELEMETRY24H DRIFT41,685 material changesacross 38,305 domains · 24h to ~85m ago · +7,068 vs yesterdaySHIFT42 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW540 curated domains not reachablelast probe, steadySITE ERRORS33,827 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 150,322 sites429 rate-limit / 403 bot-block, a posture signal

aromatica.co

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

This reading of aromatica.co was taken 3d ago

aromatica.co is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting aromatica.co 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 aromatica.co Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Email byGoogle Workspace
Secured byLet's Encrypt
Also usesGoogle Search Console
7 subdomains · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 02:19 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 aromatica.co actually stands on - every host below is a signed observation
aromatica.co
A / AAAA
203.245.12.121203.245.12.119203.245.12.115183.111.139.227
unattributedserves the site
NS
ns2.cafe24.co.krns1.cafe24.co.krns2.cafe24.comns1.cafe24.com
cafe24.co.kr + cafe24.comanswers its DNS
MX
ALT1.ASPMX.L.GOOGLE.COMALT4.ASPMX.L.GOOGLE.COMALT2.ASPMX.L.GOOGLE.COMASPMX.L.GOOGLE.COM+1 more
Google Workspacereceives its email
TLS
aromatica.co
Let's Encryptissued its certificate

DNS Records

A 4

  • 203.245.12.121
  • 203.245.12.119
  • 203.245.12.115
  • 183.111.139.227

MX 5

  • 5ALT1.ASPMX.L.GOOGLE.COM
  • 11ALT4.ASPMX.L.GOOGLE.COM
  • 6ALT2.ASPMX.L.GOOGLE.COM
  • 1ASPMX.L.GOOGLE.COM
  • 10ALT3.ASPMX.L.GOOGLE.COM

TXT 3

  • google-site-verification=-4aAJBzPznh47Y7pj6W6M45yjTcoGAfkWXqJQrRaa7k
  • google-site-verification=F3dSnV_eup_puWSAwJp-sw8vEVjE3tZ9vUYVUv_F-Vc
  • klaviyo-site-verification=V6QD7b

NS 4

  • ns2.cafe24.co.kr
  • ns1.cafe24.co.kr
  • ns2.cafe24.com
  • ns1.cafe24.com

SOA 1

  • aromatica.co postmaster.aromatica.co

MCP_RECORDS 3

  • google-site-verification=F3dSnV_eup_puWSAwJp-sw8vEVjE3tZ9vUYVUv_F-Vc
  • google-site-verification=-4aAJBzPznh47Y7pj6W6M45yjTcoGAfkWXqJQrRaa7k
  • klaviyo-site-verification=V6QD7b

DMARC_RECORDS 3

  • google-site-verification=-4aAJBzPznh47Y7pj6W6M45yjTcoGAfkWXqJQrRaa7k
  • google-site-verification=F3dSnV_eup_puWSAwJp-sw8vEVjE3tZ9vUYVUv_F-Vc
  • klaviyo-site-verification=V6QD7b

BIMI_RECORDS 3

  • google-site-verification=-4aAJBzPznh47Y7pj6W6M45yjTcoGAfkWXqJQrRaa7k
  • klaviyo-site-verification=V6QD7b
  • google-site-verification=F3dSnV_eup_puWSAwJp-sw8vEVjE3tZ9vUYVUv_F-Vc

MTA_STS_RECORDS 3

  • google-site-verification=F3dSnV_eup_puWSAwJp-sw8vEVjE3tZ9vUYVUv_F-Vc
  • klaviyo-site-verification=V6QD7b
  • google-site-verification=-4aAJBzPznh47Y7pj6W6M45yjTcoGAfkWXqJQrRaa7k

TLS Certificates (3)

Common NameIssuerExpires
aromatica.co C=US, O=Let's Encrypt, CN=YR1 Sat, 26 Sep 2026 15:18:55 +0000
YR1 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 (7)

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_f8e53da18af600f2
Output Hash
f78c7d95e87a25a107762dbf511cd9dedd9286135f978ba8116d687155d2f489
Signature
ed25519:b52e9a42b39e8ca5582d9b58c96f708b8be1b609f6ff594961c3137a9ce828e602bb285eee2dc57b1f5a2e7a7824757da9ef0bb391a7103140bce4235610590c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser