CONTINUOUS INTERNET TELEMETRY24H DRIFT8,763 material changesacross 8,372 domains · 24h to ~3h ago · -32,097 vs yesterdayNOW562 curated domains not reachablelast probe, steadySITE ERRORS34,265 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,299 sites429 rate-limit / 403 bot-block, a posture signalMOVERokta.comNo mail routes in the latest observation

zxbmi.com

Observed Aug 2, 2026, 09:03 UTC (15h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Verify this receipt yourself + Watch this domain
Not responding
Secured byLet's Encrypt
2 subdomains · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 09:03 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 zxbmi.com actually stands on - every host below is a signed observation
zxbmi.com
A / AAAA
103.48.6.134103.48.6.133103.48.6.184103.48.6.185
unattributedserves the site
NS
a.share-dns.comb.share-dns.net
share-dns.com + share-dns.netanswers its DNS
TLS
zxbmi.com
Let's Encryptissued its certificate

DNS Records

A 4

  • 103.48.6.134
  • 103.48.6.133
  • 103.48.6.184
  • 103.48.6.185

TXT 5

  • app=failover; addressType=Primary; address=103.48.6.133; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.134; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.184; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.185; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Secondary; address=194.147.101.86; healthCheck=tcp80; healthStatus=Healthy;

CNAME 1

  • k8bwe5nf.n.dns819.com

NS 2

  • a.share-dns.com
  • b.share-dns.net

SOA 1

  • a.share-dns.com master.share-dns.com

MCP_RECORDS 5

  • app=failover; addressType=Primary; address=103.48.6.133; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.134; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.184; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.185; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Secondary; address=194.147.101.86; healthCheck=tcp80; healthStatus=Healthy;

DMARC_RECORDS 5

  • app=failover; addressType=Primary; address=103.48.6.133; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.134; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.184; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.185; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Secondary; address=194.147.101.86; healthCheck=tcp80; healthStatus=Healthy;

BIMI_RECORDS 5

  • app=failover; addressType=Primary; address=103.48.6.133; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.134; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.184; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.185; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Secondary; address=194.147.101.86; healthCheck=tcp80; healthStatus=Healthy;

MTA_STS_RECORDS 5

  • app=failover; addressType=Primary; address=103.48.6.133; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.134; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.184; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Primary; address=103.48.6.185; healthCheck=tcp80; healthStatus=Healthy;
  • app=failover; addressType=Secondary; address=194.147.101.86; healthCheck=tcp80; healthStatus=Healthy;

TLS Certificates (3)

Common NameIssuerExpires
zxbmi.com C=US, O=Let's Encrypt, CN=YR2 Tue, 08 Sep 2026 05:56:32 +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 (2)

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