cable provider: unitymedia.de
mobile provider: blau.de
yesterday only cable didn't work, today both cable and mobile don't work.
http://www.abuseat.org/lookup.cgi?ip=126.96.36.199Your IP 188.8.131.52 has been blocked because it is blacklisted. For details please see http://www.spamhaus.org/query/bl?ip=184.108.40.206.
Your IP 220.127.116.11 has been blocked because it is blacklisted. For details please see http://www.barracudacentral.org/lookups ... 08.248.128.
An entry on the blacklist may have several reasons:
1. You are a well-known spammer.
2. Last time a well-known spammer was using the dynamic IP address which you got from your ISP (Internet Service Provider), your e-mail address or the username you have choosen.
3. Your ISP is well-known for a lot of spamming customers and is not fighting against spammers enough.
IP Address 18.104.22.168 is listed in the CBL. It shows signs of being infected with a spam sending trojan, malicious link or some other form of botnet.
It was last detected at 2016-12-22 17:00 GMT (+/- 30 minutes), approximately 7 days, 1 hours ago.
This IP is infected (or NATting for a computer that is infected) with a spam-sending botnet, most likely kelihos. In other words, it's participating in a botnet.
Cutwail is a complex infection and requires a number of steps to ensure that it's eradicated.
First, cutwail spams out very high volumes, is one of the the largest vectors of malware on the Internet, and almost every cutwail infection also has a copy of the pushdo (DDOS by web transaction) malware and the zeus botnet. The zeus botnet controls the cutwail/pushdo pair as well as does information stealing/keyboard logging. Hence, this is a very severe threat - not just to the owner of the infected computer, the other members of your internal network (if you have one) but the rest of the Internet too.
Second, we have two methods for detecting cutwail. One of the methods is by detecting the spams that cutwail sends. The other method does not work that way. This means that even if you block outbound port 25 from non-mail-servers on your local network, we can still detect a cutwail infection on your local network. This means that if you implement port 25 restrictions, you should implement logging so that you can detect what internal machines are being blocked by it and are thereby probably cutwail infections.
If you simply remove the listing without ensuring that the infection is removed (or the NAT secured), it will probably relist again.
This IP is infected (or NATting for a computer that is infected) with a spam-sending infection. In other words, it's participating in a botnet. If you simply remove the listing without ensuring that the infection is removed (or the NAT secured), it will probably relist again.