Comprehensive, runnable examples showing how to use the Fraudlogix IP Score API to evaluate visitor risk and take actions (block, challenge, or allow).
- Use
https://iplist.fraudlogix.com/v5?ip=<IP>withx-api-keyto retrieve risk data. - Implement 6 configurable security scenarios across PHP, Python, Node.js, Go, Java, C#, and Ruby.
- Includes rate limit handling (HTTP 429) and sensible failure defaults.
- Register a free account with 1,000 IP lookups at https://ipui.fraudlogix.com/register.
- After registering, use your
x-api-keyin requests toiplist.fraudlogix.com. - Store keys in environment variables or secrets managers; avoid hardcoding.
- Block high/extreme risk outright
- Quarantine medium risk for verification (captcha/2FA)
- Strict mode: allow only low-risk visitors and known search-engine bots
- Block proxies/VPN/TOR, allow search-engine bots
- Block anonymizers or extreme cases
- Geo-block by
CountryCode
- PHP: see examples/php/security.php
- Python (Flask): see examples/python/app.py
- Node.js (Express): see examples/javascript/app.js
- Go: see examples/go/main.go
- Java (Spring sample): see examples/java/FraudlogixSecurityInterceptor.java
- C# (.NET middleware): see examples/csharp/FraudlogixSecurityMiddleware.cs
- Ruby (Rails before_action): see examples/ruby/fraudlogix_security.rb
- Set your API key and scenario toggles inside each example.
- Prefer environment variables in production:
FRAUDLOGIX_API_KEY,BLOCKED_PAGE,CAPTCHA_PAGE.
- Exceeding limits returns HTTP 429 with
{ "message": "Limit Exceeded" }. - Examples default to fail-open (allow access) when API errors occur; adjust per your policy.
- API fields: docs/API.md
- Security scenarios: docs/SecurityScenarios.md
- Rate limiting & error handling: docs/RateLimiting.md
- Implementation guide: docs/ImplementationGuide.md
- Replace placeholder keys and URLs.
- Implement proper logging, auditing, and user privacy compliance (GDPR/CCPA) in production.