Security · head-to-head
IPLogs vs PhishStats
IPLogs scores an IP address's likelihood of being a VPN, proxy, Tor exit node, or datacenter host by combining 25+ signals -- ASN/PeeringDB classification, TCP/IP and TLS fingerprinting, RTT timing, and active probing -- into a single verdict and confidence score. A single keyless POST to /v1/check (optionally enriched with client-side signals like user-agent, timezone, and WebRTC IP) returns the verdict, a 0-1 risk score, and the matched signals with their weights, run by DigitalD.tech. There's no signup and no enforced rate limit today -- the public endpoint is explicitly fair-use, with dedicated deployments available on request for high-volume callers.
PhishStats crowdsources and republishes a running feed of phishing URLs, screenshots, and detection metadata, giving anyone a free real-time phishing blocklist to query or download. The REST API — now served from api.phishstats.info after moving off its old port-based endpoint — supports complex filter queries against the phishing database and returns JSON records ready to stream into an existing security stack. Anonymous lookups are capped at 50 requests/day per IP; a free registered key raises that to 150/day, with paid tiers for higher volume.
| IPLogs | PhishStats | |
|---|---|---|
| Authentication | None | None |
| Pricing | free | freemium |
| Formats | JSON | JSON |
| CORS | yes | no |
| HTTPS | Yes | Yes |
IPLogs supports CORS, while PhishStats doesn't — pick IPLogs for direct browser calls.