Fight Fraud.

Fraud, VPN and proxy checks for any IP, plus disposable and temporary email detection. Free, with no signup.

lookups answered on 23 September 2026
678,761
countries those requests came from
137
confirmed attackers in the open data
1,544,269
disposable email domains
223,301

Two checks, one free API.

Score any IP address, and catch throwaway email before it reaches your signup form. Both answer live below: type your own, or click an example.

IP intelligence

Fraud score, VPN, proxy, Tor and datacenter detection, abuse history.

Try

Address

185.220.101.34

TORSERVERS-NET · AS60729 · Germany

Verdict

Critical

Fraud score

100/ 100

Signals

  • Tor exit: yes
  • VPN: yes
  • Proxy: yes
  • Datacenter: yes
  • Residential proxy: no
  • Known abuser: yes

Why

Active command & control (C2) server used to coordinate malware operations. Identified as part of a botnet network. Performing SSH brute force attacks against servers. Exploiting web server vulnerabilities and launching HTTP attacks. Spam and automated registration abuse across multiple platforms. Flagged as an indicator of compromise during active incident response. Persistent high-severity threat, confirmed repeatedly by our honeypot sensors and community reports. VPN connection detected (Tor). Located in a high-risk network neighborhood where 97% of the /24 subnet is flagged for abuse - this level of concentration typically indicates compromised infrastructure or a malicious hosting operation

Full report for 185.220.101.34
  • 1.5M confirmed attackers, and an answer for every other address too
  • Written reason, threat tags, the network around it and who runs it
  • No key for single lookups, no daily cap

Email checks

Disposable and temporary addresses, role accounts, reported spammers.

Try

Address

[email protected]

mailinator.com

Verdict

Disposable

A throwaway inbox. Block it at signup.

Signals

  • Disposable: yes
  • Role address: no
  • Reported spammer: no
  • Valid format: yes

Why

This domain is a known disposable or temporary mailbox provider, confirmed by our own monitoring and by community reports.

Full report for mailinator.com
  • 223.3K throwaway domains, plus new ones caught by their mail servers
  • Gmail, Outlook and other real providers can never be flagged as throwaway
  • One call at signup, before the account exists

Already in production: clients that named themselves on 23 September 2026

  • n8n workflows24,132
  • Python backends7,444
  • Proxy validation tools7,106
  • Node backends2,142
  • Monitoring systems1,505
  • Minecraft server plugins1,018

Requests that day by each client type. 678,761 lookups in total, most of them from apps that do not name themselves.

Coming from AbuseIPDB, IPQualityScore or ipinfo?

Change the base URL and the key. The answer comes back in the shape your code already parses, with an ffraud_extras object on top.

Pick the API your code calls today

Requestone line changes

GET https://api.abuseipdb.com/api/v2/check?ipAddress=185.220.101.34

GET https://api.ffraud.com/compat/abuseipdb/v2/check?ipAddress=185.220.101.34

Key: ff_live_your_key

Same Key header, your free FFraud key in it.

Your parser
unchanged
Fields it reads
4, same names
Added
ffraud_extras

Response200 OK, AbuseIPDB shape

{"data": {"ipAddress": "185.220.101.34","abuseConfidenceScore": 100,"countryCode": "DE","usageType": "Data Center","isp": "TORSERVERS-NET","isTor": true,"ffraud_extras": {"fraud_score": 100,"vpn": true,"proxy": true,"risk": "critical","threat_tags": ["c2_server", "botnet_node", "ssh_brute_force"],"confidence": "high"}}}

fields your code readsonly in FFraud

Live answer for 185.220.101.34, a Tor exit node, reshaped exactly as the compatibility endpoint does it.

Our honeypot community, all over the world.

People all over the world volunteer to run honeypots and share what hits them with us, next to the reports our community sends in. The globe shows where the addresses they confirmed most often are.

1,000most confirmed addresses

52countries they come from

Where the most come from

  1. United States423
  2. Netherlands119
  3. Germany102
  4. Portugal47
  5. Sweden37
  6. United Kingdom29
  7. France25
  8. Vietnam18

Sample taken on 15 September 2026 and located with the FFraud API.

Run a honeypot? Share what it catches

The download is the list. The API is the full answer.

The files on GitHub hold the addresses we have confirmed as attackers, so anyone can block them for free. The API answers for every address, with everything we know about it, including what we keep out of the files on purpose.

What you want to knowOpen data filesAPI
Which addressesConfirmed attackers only: seen at least twice, score 50 or higherAny address you ask about
Addresses confirmed only onceLeft out until a second, independent confirmationAnswered, and already weighed into the score
VPN, proxy, Tor, datacenter, residential proxyOnly as the type of a listed attackerFor every address
When it was activeNo datesFirst seen, last seen, times seen, recent abuse
Why it is flaggedThe worst categoryEvery threat tag and a written reason
Its neighbourhoodNot includedHow much of its /24 network is abusive
Who runs itNot includedASN, ISP, organisation, hostname, WHOIS abuse contact
Where it isNot includedCountry, region, city, timezone
Open portsNot includedIts open ports
EmailThe list of disposable domainsAlso brand-new throwaway services, caught by their mail servers before any list has them

Never published, by design

Who reported an address, and the evidence they sent
People report to us in confidence. Their identity, their logs and their screenshots stay with us.
Addresses confirmed only once
One report is a claim, not proof. It goes public after an independent second confirmation; until then only the API weighs it.
Where our sensors are
A honeypot only works while attackers do not know it is one.
Which internet providers have infected customers
A ranking of consumer networks by infected machines would be a target list for criminals. The networks file names only small networks where almost every address we saw was abusive; large providers are left out on purpose.

Use the files to block known attackers in bulk. Use the API when you decide about a specific visitor: a first-time address, a VPN user, a signup from a datacenter. Both are free.

Free where others cap or charge.

How FFraud compares with three well-known IP intelligence APIs, going by their public plans.

FeatureFFraudAbuseIPDB logoAbuseIPDBIPQualityScore logoipinfo logo
PriceFree, foreverFree tier, then paidPaid, per lookupFree tier, then paid
Daily capNoneCapped on freeBilled per lookupCapped on free
Fraud scoreYesConfidence scoreYesNo
VPN, proxy and Tor detectionYesLimitedYesOn paid plans
Open ports and CVEsYesNoNoNo
WHOIS abuse contactYesNoNoGated
Blocklist published as open data1.5M IPs, MITNo bulk export on freeNoNo

Summarised from each provider's public plans. Plans change, so check theirs before you decide. Full comparisons: AbuseIPDB, IPQualityScore and ipinfo.

Common questions

What people ask before they send their first request.

Yes. Lookups through the API and the open data cost nothing, with no daily or monthly caps and no credit card. FFraud is an anti-fraud project, not a sales funnel. Fraud data gets better the more people use it and report to it, so a paywall would make it worse.

See the pricing page

No. Single lookups work without signing up. A free key adds batch lookups and usage stats.

Get a free API key

There are no daily or monthly caps. Short bursts are rate limited to keep the API fast for everyone: cross the limit and you get a 429 for a moment, not a paywall. If you need sustained heavy traffic, email us and we raise your limit for free.

Rate limits and errors

No. The open data is the confirmed core: the addresses we have caught attacking at least twice, with a score and a category, made for blocking in bulk. The API answers for every address, including ones confirmed only once, with the VPN and proxy verdict, when it was active, every threat tag and a written reason, the network around it and who runs it. Some things never leave the private database at all: who reported an address and the evidence they sent, where our sensors are, and which internet providers have infected customers, because a list like that would help criminals more than defenders.

What each one answers

Yes, both the API and the open data. The data is MIT licensed, so you can use it in commercial products, redistribute it and even build a paid product on top. Attribution is appreciated, never required.

Check an address now.

Single lookups need no signup. A free key adds batch calls, usage stats and the reporting API.

Or get a free API key, or read the docs.