Parallel Queries
We query 80+ sources simultaneously using non-blocking I/O.
How it works
From a DNS lookup to an alert in your channel
HostRepute checks your monitored hosts against configured data sources, stores the results, and sends alerts through the destinations your team has set up.
How HostRepute turns monitored assets into alerts and reports
-
1
Your Assets
IPs & Domains are scheduled for checking based on your plan frequency.
-
2
Analysis Engine
Distributed workers query 80+ sources in parallel and filter false positives.
-
3
Alerts & Reports
Notifications and scheduled digests keep stakeholders current.
Step 1
Distributed DNS Scanning
HostRepute doesn't rely on a single server. We operate a distributed network of scanners to ensure high availability and prevent our own IPs from being rate-limited.
IPv4 & IPv6 Support
Full support for both standard and modern IP addressing protocols.
resolver.log
resolving
192.168.1.1
80+ sources queued
- zen.spamhaus.org clean
- b.barracudacentral.org clean
- bl.spamcop.net listed 127.0.0.2
- cbl.abuseat.org ...
Step 2
Intelligent Analysis
Raw data can be confusing. Our engine parses the cryptic DNS return codes to tell you exactly why you were listed and how severe it is.
Return Code Parsing
We translate codes like 127.0.0.4 into human-readable reasons (e.g., "Exploit Detected").
False Positive Logic
Our algorithms filter out "flapping" listings to reduce alert fatigue.
analysis_log.json
{
"host": "192.168.1.1",
"status": "LISTED",
"threat_level": "HIGH",
"sources": [
{
"rbl": "SpamCop",
"reason": "Trap hit within last 24h",
"delist_url": "https://www.spamcop.net/..."
}
]
}
Step 3
Instant Notification and Reporting
Time is money. When a listing is confirmed, we dispatch alerts immediately to your preferred channels and keep scheduled report snapshots ready for stakeholder review.
- Slack
- Telegram
- Discord
- PagerDuty
- Pushover
Alert: IP Blacklisted
192.168.1.1 was listed on SpamCop.
View Details
Silence
Available alert destinations
Email, Slack, Telegram, Discord, PagerDuty, Pushover
Route reputation events to the channels your team already watches.
- Next report
- 09:00 UTC
- Executive PDF snapshot queued
- Escalation
- On-call owner
- Auto-reminder if unresolved
Stakeholder report ready
Noindex link- Listed IP
- 1
- Sources checked
- 24
- Recipients
- 3
Client-ready output
Share reputation proof without exposing your dashboard
Turn a completed scan into a noindex public report for customers, vendors, or incident tickets. The report uses a stable snapshot, so later source edits or team changes do not rewrite what you already shared.
Public report
mail.example.com
Prepared for Acme Support
- Checked
- 80+
- Listed
- 1
- Clean
- 79
-
Snapshot saved
The shared result stays stable after later scans or source edits.
-
Secret and noindex
The link is unlisted by default and includes noindex robot controls.
-
Revoke anytime
Disable the link when a ticket closes or a customer handoff ends.
Recurring stakeholder updates
Send reputation summaries before anyone asks
Scheduled reports turn the same monitoring history into daily, weekly, or monthly email digests. Teams can scope a digest to all monitored hosts or a single host tag, then share the immutable snapshot when a customer, support team, or incident channel needs proof.
Weekly scheduled report
Transactional mail digest
Team scope: production mail
- Total
- 20
- Clean
- 18
- Listed
- 2
- Changed
- 1
-
Team or tag scope
Focus a digest on the whole team or a specific host tag.
-
Send only on changes
Skip routine emails when reputation did not move.
-
Immutable snapshot
Every sent report keeps the period metrics and noindex public link stable.
Broad Source Coverage
HostRepute checks public RBLs and reputation feeds from one place, then keeps the history attached to each monitored host.
- Sources
- 80+
- Monitoring
- 24/7
- Alert Channels
- 5+
Experience the speed yourself
Start your 14-day free trial and run your first comprehensive reputation check in seconds.