Warning:this tool cannot identify solutions hosted on-premises or working through APIs such as ICES (Integrated Cloud Email Security) and CAPES (Cloud-native, API-enabled Email Security).
Warning:IP geolocation uses a free API and may return unknown results due to request limits.
Info:email addresses are not stored â only domain names and analysis results are.
Enter up to 200 domains or email addresses (separated by new line, comma, or semicolon):
Domain
Identified providers in MX records
MX IP location
Identified providers in SPF record
Providers in DMARC record (RUA)
DMARC policy
Analysis time
Actions
No analysis yet â enter domains above and run.
Key points to emphasize
Detected situation
Mode
Domain(s)
Points to emphasize
Battlecard
Analyzed Domains
Domain
MX providers
SPF providers
DMARC policy
Analysis time
Actions
Monitored Domains
Monitored domains are re-checked on demand here. In the hosted version, a scheduled backend job would re-analyze them automatically and alert on changes (e.g. a competitor appearing, or DMARC posture regressing).
Domain
MX providers
DMARC policy
Last check
Actions
My Statistics
Global Statistics
This static build has no shared backend, so "global" statistics reflect every analysis stored in this browser. In the hosted version this tab would aggregate anonymised results across all users.
API Token & Integrations
Issuing and validating API tokens requires a server holding secrets â it cannot run in a static, client-side file. To enable this: expose the analysis engine as an endpoint (the same DoH + fingerprint logic on a small Node/PHP backend), store per-user tokens, and rate-limit by token. The client below is otherwise fully functional without it.
Planned endpoint
POST /api/v1/analyze { "domains": ["exemple.fr"], "geo": true }
Auth header
Authorization: Bearer <token>
Live DNS via DNS-over-HTTPS (Google) · geolocation via ipwho.is · nothing sent to a server · results stored locally in your browser.