DomainTools Monitors vs Pulse Intelligence
DomainTools Monitors
domaintools.comPulse Intelligence
github.comSide by side
| Figure | DomainTools Monitors | Pulse Intelligence |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 2 | 1 |
| Spec score · Threat Intelligence Platforms | 7.3 (#17) | 8.4 (#3) |
| Integrations | DomainTools lists integrations for platforms including Splunk, Microsoft Sentinel, Elastic, Google Chronicle, IBM QRadar, Palo Alto Cortex, ServiceNow, and Tines. | Its public read-only API supports scoped keys and integrations such as analyst scripts, SOAR playbooks, and internal tools. |
Plans
DomainTools Monitors
- Enterprise membershipPriced on request
- Individual membershipPriced on request
In their own words
DomainTools Monitors
DomainTools Monitors has no write-up on Specifiction yet; its figures are above.
Pulse Intelligence
Pulse Intelligence is an open-source, self-hosted threat intelligence workspace for analyst workflows. It organizes threat actors, aliases, campaigns, indicators, reports, sources, CVEs and ATT&CK mappings, and ingests public feeds including CISA KEV, NVD, FIRST EPSS, abuse.ch, OTX, vendor blogs and security news. Indicator enrichment uses OTX, AbuseIPDB and VirusTotal, with Redis-backed quota controls. Analysts can save hunts across indicator fields, receive alerts for new matches and export results as CSV, STIX 2.1, MISP JSON, or Snort and Suricata rules. Scheduled Markdown reports can cover new indicators, KEV additions, hunt alerts and feed health. A public read-only API with scoped keys supports integrations; its default limit is 120 requests per API key per 60-second window, and indicator pages are capped at 500. The project lists Argon2id passwords, database-backed session cookies, hashed API keys and an admin-only audit log. Deployment requires Node.js 20.9+, PostgreSQL 17 or compatible PostgreSQL, and a Redis-compatible server. Native and Docker Compose deployment paths are documented.