Search the Community
Showing results for tags 'email@example.com'.
We get many fraudulent bitcoin spam mails from the same server group 126.96.36.199 - 188.8.131.52. Each time, another IP from that group is beeing used - abuse contact for all used servers is firstname.lastname@example.org. I suppose, this could be the spammer himself, since reporting is beeing ignored. What kind of reporting makes sense in this case? I allready figured out, that the servers are hosted by nshostu.ru - so i instead started to send my reporting to email@example.com. Any other ideas? Thanks for your help! Best regards Sam This one of many exampels: Tracking message source: 184.108.40.206: Routing details for 220.127.116.11[refresh/show] Cached whois for 18.104.22.168 : firstname.lastname@example.orgUsing last resort contacts email@example.com Yum, this spam is fresh! Message is 0 hours old22.214.171.124 not listed in cbl.abuseat.org126.96.36.199 not listed in dnsbl.sorbs.net188.8.131.52 not listed in accredit.habeas.com184.108.40.206 not listed in plus.bondedsender.org220.127.116.11 not listed in iadb.isipp.com