Live data from Hacker News

API providing threat analysis of any given IP address

fraudguard.io

1–10 of 84 posts

Re: API providing threat analysis of any given IP address

#4
post #3

Correction, API providing: 502 Bad Gateway nginx/1.8.1

Same here. And https://www.fraudguard.io/ uses the wrong SSL certificate (that of analytics.crynix.com)

Probably the site was taken down by removing the vhost config. So the domain is getting the default vhost and its certificate.

Re: API providing threat analysis of any given IP address

#8
post #7

If the creators are on HN, curious to know what sets this apart from other threat intel services like IBM X-Force, ThreatConnect, VirusTotal, Carbon Black, etc.

I'm Ryan, one of three devs that built FraudGuard.io. The answer is basically price. We do EVERYTHING ourselves and try to keep price extremely fair. We have plans that start at $10 /month and we also have a small free-for-life plan too.

Thats the best answer. The secondary part is we want a simple way for any dev off the street to integrate with api.fraudguard.io in 5 minutes. Imagine you are a small company and you want to limit back office access to you CMS to only IPs outside of Germany. That takes just a couple minutes. Or you want to allow back office access to you CMS from everywhere but you want to decrease the session timeout to only 30 minutes if the originating IP is a tor node or public proxy, etc.

We just got out of beta (literally last night) but so far thats the majority of use cases that we've seen so far.

Re: API providing threat analysis of any given IP address

#9
post #6

I plugged in a few IPs from stopforumspam.com and they all had the same "risk level" as my own IP: 1.

I'm Ryan, one of three devs that built FraudGuard.io. Honestly we have a lot more work to do specifically in spam. With that being said, spam is the least requested collector so far by our users. Just to share in beta we asked some of our heavy users and about 90% of our users preferred our focus was on honeypot collection, spam was less than 2%.

So heres how it works now. We do not rely on external sources at this time. The reason why, because our traffic is so high that no external source at least that we've found will serve our users traffic.

For example stopforumspam.com limits API requests to 20,000 per day. I haven't checked our stats today but during our beta (which ended yesterday) we served more than 20,000 API requests per hour. So even with huge cache durations set its very hard to rely on outside sources so instead we run all our own spam collectors, using our own domains, etc.

Post reply on HN