CONTINUOUS INTERNET TELEMETRY24H DRIFT38,088 material changesacross 34,280 domains · 24h to ~20m agoDNS DRIFT52 domains changed DNS providertop destination koaladns.com · +30 vs yesterdayNOW543 curated domains not reachablelast probe, steadySITE ERRORS33,703 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 157,225 sites429 rate-limit / 403 bot-block, a posture signal

zamartz.com

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

This reading of zamartz.com was taken 3d ago

zamartz.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zamartz.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 zamartz.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCloudflare
Email byGoogle Workspace
Secured byGoogle Trust Services
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 20:58 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 zamartz.com actually stands on - every host below is a signed observation
zamartz.com
A / AAAA
141.193.213.10141.193.213.11
Cloudflareserves the site
NS
ns-1340.awsdns-39.orgns-2034.awsdns-62.co.ukns-208.awsdns-26.comns-531.awsdns-02.net
awsdns-39.org + awsdns-62.co.uk + moreanswers its DNS
MX
aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comzamartz.com+2 more
Google Workspacereceives its email
TLS
zamartz.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 141.193.213.10
  • 141.193.213.11

MX 6

  • 1aspmx.l.google.com
  • 10alt3.aspmx.l.google.com
  • 10alt4.aspmx.l.google.com
  • 20zamartz.com
  • 5alt2.aspmx.l.google.com
  • 5aspmx.l.google.com

TXT 3

  • anthropic-domain-verification-8nh77e=dhz7klGc7l7gmFQRxEWLHLcqd
  • include:relay.mailchannels.net ~all
  • v=spf1 include:_spf.google.com include:shops.shopify.com include:servers.mcsv.net

NS 4

  • ns-1340.awsdns-39.org
  • ns-2034.awsdns-62.co.uk
  • ns-208.awsdns-26.com
  • ns-531.awsdns-02.net

SOA 1

  • ns-1340.awsdns-39.org awsdns-hostmaster.amazon.com

SRV 1

  • autodiscover.bluehost.com.zamartz.com:443 p0

MCP_RECORDS 3

  • anthropic-domain-verification-8nh77e=dhz7klGc7l7gmFQRxEWLHLcqd
  • include:relay.mailchannels.net ~all
  • v=spf1 include:_spf.google.com include:shops.shopify.com include:servers.mcsv.net

DMARC_RECORDS 1

  • v=DMARC1; p=quarantine;rua=mailto:dmarc.ug3xh@zapiermail.com;pct=100;

BIMI_RECORDS 3

  • anthropic-domain-verification-8nh77e=dhz7klGc7l7gmFQRxEWLHLcqd
  • include:relay.mailchannels.net ~all
  • v=spf1 include:_spf.google.com include:shops.shopify.com include:servers.mcsv.net

MTA_STS_RECORDS 3

  • anthropic-domain-verification-8nh77e=dhz7klGc7l7gmFQRxEWLHLcqd
  • include:relay.mailchannels.net ~all
  • v=spf1 include:_spf.google.com include:shops.shopify.com include:servers.mcsv.net

TLS Certificates (3)

Common NameIssuerExpires
zamartz.com C=US, O=Google Trust Services, CN=WE1 Sun, 25 Oct 2026 09:05:29 +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 (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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_8c33a3d79fc16e49
Output Hash
1b35b05558f8a20cdeb4117fee7791b15b62d5e54ab0796c75cdfcae54bcfe8f
Signature
ed25519:c071340a896667efaa1251388414f8f3ee9f69bc89f60c1aeeb27e6de160ef9f3f8a0cdcdf466a7a1563ca310399056af614f4884782c68a85d719e5e6625d0b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser