CONTINUOUS INTERNET TELEMETRY24H DRIFT39,466 material changesacross 35,185 domains · last 24h · +4,849 vs yesterdayDNS DRIFT51 domains changed DNS providertop destination koaladns.com · +2 vs yesterdayNOW545 curated domains not reachablelast probe, steadySITE ERRORS33,676 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 157,341 sites429 rate-limit / 403 bot-block, a posture signal

ziphearing.com

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

This reading of ziphearing.com was taken 3d ago

ziphearing.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting ziphearing.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 ziphearing.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Email byGoogle Workspace
Secured byGlobalSign
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 04:45 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 ziphearing.com actually stands on - every host below is a signed observation
ziphearing.com
A / AAAA
192.124.249.154
unattributedserves the site
NS
pns53.cloudns.netpns54.cloudns.netpns52.cloudns.netpns51.cloudns.net
cloudns.netanswers its DNS
MX
alt2.aspmx.l.google.comalt1.aspmx.l.google.comaspmx.l.google.comalt3.aspmx.l.google.com+1 more
Google Workspacereceives its email
TLS
*.ziphearing.com
GlobalSign nv-saissued its certificate

DNS Records

A 1

  • 192.124.249.154

MX 5

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

TXT 3

  • v=spf1 +mx +a +ip4:172.16.186.72 +ip4:192.145.235.209 +ip4:69.167.186.72 +include:_spf.google.com +include:emsd1.com +include:_spf.mailersend.net include:_spf.paubox.com -all
  • _globalsign-domain-verification=5ld1tkterZnefp1JqUhlfmretwSQEyaTsKw98WYBo9
  • _globalsign-domain-verification=gvVY6QcoVedZ_--74tPxsHrTL_x8kXThKe7Q-v9OAZ

NS 4

  • pns53.cloudns.net
  • pns54.cloudns.net
  • pns52.cloudns.net
  • pns51.cloudns.net

SOA 1

  • ns51.cloudns.net support.cloudns.net

MCP_RECORDS 1

  • _globalsign-domain-verification=5ld1tkterZnefp1JqUhlfmretwSQEyaTsKw98WYBo9

DMARC_RECORDS 1

  • v=DMARC1;p=reject;sp=none;adkim=r;aspf=r;pct=100;fo=0;rf=afrf;ri=86400;rua=mailto:javadeveloperkyiv@gmail.com

BIMI_RECORDS 1

  • _globalsign-domain-verification=5ld1tkterZnefp1JqUhlfmretwSQEyaTsKw98WYBo9

MTA_STS_RECORDS 1

  • _globalsign-domain-verification=5ld1tkterZnefp1JqUhlfmretwSQEyaTsKw98WYBo9

TLS Certificates (2)

Common NameIssuerExpires
*.ziphearing.com C=BE, O=GlobalSign nv-sa, CN=GlobalSign GCC R3 DV TLS CA 2020 Sun, 07 Feb 2027 19:20:50 +0000
GlobalSign GCC R3 DV TLS CA 2020 2.5.4.11=GlobalSign Root CA - R3, O=GlobalSign, CN=GlobalSign Sun, 18 Mar 2029 00:00:00 +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_d8f338c313ca5694
Output Hash
4f4f27685c92954dadce0f555f2e27e7a7afe3433fb72b5ea56eb7cb50ca9579
Signature
ed25519:e8418fd88596c6dc0446b5bb30428d13b889159a36c7c95b9e410b64f32e48a0c55fd625b43721b87670487cf89d364a7a3e2a5fc28b18f3c8c77041181aed0e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser