Search the Community
Showing results for tags 'apews'.
Found 3 results
Hi, I read the What to do if you're on APEWS article. But I want to document it somewhere. Please ignore this post if you don't care about APEWS. APEWS entry E-988096 is outdated: Entry matching your Query: E-988096 IP: 188.8.131.52 CASE: C-1445 Spammer, scanner, scammer, zombie PC, rooted PC, bot, etc History: Entry created 2013-12-21
Hi, I know... this is no APEWS forum, they abuse it by referring people here. I also read the What to do if you're on APEWS article. Anyway this should be documented somewhere. Please ignore this post if you don't care about APEWS. APEWS entry E-1718287 is outdated: Entry matching your Query: E-1718287 184.108.40.206/20 CASE: C-131 Unallocated CIDR, no traffic until allocated, or allocated to bad reputation provider or allocated but dynamic / generically named IPs, or bogons, see www.cidr-report.org, or orphaned IP / CIDR in routing table History: Entry created 2014-08-18 The entry now also covers lots of different provider allocations: inetnum: 220.127.116.11 - 18.104.22.168 netname: NL-NETWORKCONCEPTS-20120921 inetnum: 22.214.171.124 - 126.96.36.199 netname: RU-REDCOM-20120321 inetnum: 188.8.131.52 - 184.108.40.206 netname: DE-EGENTIC-20120921 inetnum: 220.127.116.11 - 18.104.22.168 netname: AM-IUNETWORKS-20140702 Each of these providers might or might not be worth an APEWS listing, but at least they should be handled independently.