Security · head-to-head

FilterLists vs IPLogs

FilterLists

FilterLists is Collin Barrett's independent, actively-maintained directory of filter and host lists used by adblockers, firewalls, and DNS sinkholes to block ads, trackers, malware, and other unwanted content. Its ASP.NET Core REST API serves the same catalog that powers the site -- filter lists, the domains/URLs they target, licenses, and maintainer info -- with an interactive Swagger UI for exploring the schema before writing a query. The API and site are fully free and keyless, open-sourced on GitHub with commits as recent as this week. The API lives entirely on a separate `api.filterlists.com` host -- the intuitive REST paths on the main `filterlists.com` domain just return the site's own SPA shell.

IPLogs

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.

FilterListsIPLogs
AuthenticationNoneNone
Pricingfreefree
FormatsJSONJSON
CORSnoyes
HTTPSYesYes

IPLogs supports CORS, while FilterLists doesn't — pick IPLogs for direct browser calls.

More comparisons