EmailRep vs FilterLists

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%98.0%
Uptime · 30d100%96.7%
P50 · ms277357
P95 · ms7511813
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

EmailRep vs FilterLists: common questions

Which is more reliable, EmailRep or FilterLists?

On our scheduled checks, EmailRep leads on measured uptime — EmailRep at 100% versus FilterLists at 98.0% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, EmailRep or FilterLists?

EmailRep has the lower median latency in our checks — EmailRep responds in 277 ms versus FilterLists at 357 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do EmailRep and FilterLists need an API key?

Neither needs a paid key — EmailRep is callable with no signup, and FilterLists is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call EmailRep and FilterLists from the browser?

Neither sends browser-friendly CORS headers reliably, so call EmailRep and FilterLists from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are EmailRep and FilterLists free for commercial use?

EmailRep has unclear commercial terms, and FilterLists has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.