meta-chart.com
Observed Aug 10, 2026, 23:46 UTC (5d ago). Every field below was attested with an Ed25519 signature at scan time.
meta-chart.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting meta-chart.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 meta-chart.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.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.
DNS Records
A 2
104.21.31.127172.67.176.134
AAAA 2
2606:4700:3036::ac43:b0862606:4700:3032::6815:1f7f
MX 3
10mx.zoho.com20mx2.zoho.com50mx3.zoho.com
TXT 4
brevo-code:249844a68b6ab05ee01de1179cffa666google-site-verification=conao7xoijdo2-b_24KSb9q3WGszyG_Ay-ZzpUud28Ev=spf1 include:zohomail.com include:amazonses.com ~allzoho-verification=zb42625185.zmverify.zoho.com
NS 2
chloe.ns.cloudflare.comduke.ns.cloudflare.com
SOA 1
chloe.ns.cloudflare.com dns.cloudflare.com
MCP_RECORDS 4
brevo-code:249844a68b6ab05ee01de1179cffa666google-site-verification=conao7xoijdo2-b_24KSb9q3WGszyG_Ay-ZzpUud28Ev=spf1 include:zohomail.com include:amazonses.com ~allzoho-verification=zb42625185.zmverify.zoho.com
DMARC_RECORDS 1
v=DMARC1; p=quarantine; rua=mailto:webmaster@meta-chart.com; ruf=mailto:webmaster@meta-chart.com; sp=none; adkim=r; aspf=r
BIMI_RECORDS 4
brevo-code:249844a68b6ab05ee01de1179cffa666google-site-verification=conao7xoijdo2-b_24KSb9q3WGszyG_Ay-ZzpUud28Ev=spf1 include:zohomail.com include:amazonses.com ~allzoho-verification=zb42625185.zmverify.zoho.com
MTA_STS_RECORDS 4
brevo-code:249844a68b6ab05ee01de1179cffa666google-site-verification=conao7xoijdo2-b_24KSb9q3WGszyG_Ay-ZzpUud28Ev=spf1 include:zohomail.com include:amazonses.com ~allzoho-verification=zb42625185.zmverify.zoho.com
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
meta-chart.com |
C=US, O=Google Trust Services, CN=WE1 | Sat, 12 Sep 2026 04:34:26 +0000 |
WE1 |
C=US, O=Google Trust Services LLC, CN=GTS Root R4 | Tue, 20 Feb 2029 14:00:00 +0000 |
GTS Root R4 |
C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA | Fri, 28 Jan 2028 00:00:42 +0000 |
Subdomains (1)
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 receiptEd25519 Receipt
- Receipt ID
rcpt_eb6f57b7a5ae0b93- Output Hash
0c03fba1067f7849a16c30a537f0e299b1895c80d5d4aa91d87103b126c07738- Signature
ed25519:e76cb12fdd4a91adcbdb00b6c66b1dd43bf8c099054bbd4e1a81cbc4f5bfed62fa9ab2f1d286cf16a347fde570d43ce5d18b5495bed93ab5c5ca03e880e82103- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast