AbuseIPDB Setup Guide

AbuseIPDB is a performance-critical component of the Preads Platform's security suite. Unlike real-time signal providers, AbuseIPDB specializes in historical reputation data, leveraging a global database of malicious activity reported by server administrators worldwide.

🚀 Activation & Connection

The AbuseIPDB integration is a standard feature of the IpIntelligenceService. Follow these steps to link your platform to the reputation engine.

1. Register for API Access

  1. Create a free account at AbuseIPDB.com.
  2. Navigate to your Account → API dashboard.
  3. Generate a new Standard API Key.

2. Configure in Admin Panel

Navigate to Admin → Security → Anti-Cheat → API Keys → AbuseIPDB.

  • API Key: Paste your generated key into the designated field.
  • Enabled: Toggle to ON.
  • Confidence Threshold: Set to 75 (Recommended).
  • Test API: Use the built-in test tool to verify credentials and check the reputation of a test IP (e.g., 8.8.8.8).

🛡️ Reputation Intelligence

The platform utilizes AbuseIPDB's Abuse Confidence Score to identify persistent bad actors across the industry.

Weighted Risk Analysis

  • Score Mapping: The IP's abuseConfidenceScore (0-100%) is directly mapped to the platform's unified risk score.
  • Threshold Sensitivity: Any IP meeting or exceeding the Confidence Threshold (default: 75%) will automatically trigger the is_datacenter and is_proxy flags if associated with high-risk usage patterns.
  • Temporal Precision: The system audits reports from the last 90 days (maxAgeInDays), ensuring that only relevant, recent abuse history impacts your traffic quality.

Automated Signal Interpretation

The IpIntelligenceService performs surgical keyword analysis on provider metadata:

  • Infrastructure Audit: IPs identified with "Data Center", "Web Hosting", or "Transit" usage types are analyzed against their abuse score to determine if they should be flagged as active proxies.
  • Whitelisting Awareness: The system respects global whitelists to prevent false positives for mission-critical infrastructure.

⚡ Operational Efficiency

Caching Strategy

Reputation data is highly stable but evolves over days. To optimize your account's daily limits:

  • Aggressive Caching: It is recommended to set a higher Cache TTL for AbuseIPDB results when used in isolation, though the platform defaults to 24 hours for unified safety.
  • Limit Management: The free tier provides 100 checks per day, making AbuseIPDB an excellent secondary audit layer when combined with more permissive primary providers like IPQualityScore.

Chaining Priority

In the default Smart Priority Chain, AbuseIPDB is positioned after IPQualityScore. This ensures that only traffic requiring deeper reputation auditing consumes your daily AbuseIPDB quota.

💰 Operational Scale

Feature Details
Free Tier 100 checks/day (No credit card required).
Usage Pattern Best used as a Secondary/Verification layer.
Specialization Historical abuse, brute-force participations, and known botnets.

Configure ProxyCheck Provider →