List Information
List name: Atma
Author: Atma
Author's website: atma.es
Author's description:
Attackers who try to spy or remotely control others' computers by means such Microsoft remote terminal, SSH, Telnet or shared desktops.
Threats for email servers or users: spiders/bots, account hijacking, etc.
Sites spreading virus, trojans, spyware, etc. or just being used by them to let their authors know that a new computer has been infected.
Threats for servers: exploits, fake identities/agents, DDoS attackers, etc.
Port scans, which are the first step towards more dangerous actions.
Malicious P2P sharers or bad peers who spread malware, inject bad traffic or share fake archives.
Update URL: http://list.iblocklist.com/?list=tzmtqbbsgbtfxainogvm
List Details
Last update: 04/09/2010
Update frequency: 6 (days)
Number of ranges: 87513
Number of IPs: 103210
| Date | Ranges | IPs |
| 10/09/2010 |  |
|
| 09/09/2010 | |
|
| 08/09/2010 | |
|
| 07/09/2010 | |
|
| 06/09/2010 | |
|
| 05/09/2010 | |
|
| 04/09/2010 | |
|
Usage Details
Popularity: 
Comments
fakhir (Founder) wrote:
@ Rendan
It is always best to contact the author of a list directly about any concerns with the contents of a list.
@ Rendan
It is always best to contact the author of a list directly about any concerns with the contents of a list.
posted on 30/01/2010 at 03:47PM
BigEagle (Member) wrote:
I hope that there is a post here when there is a fix for this problem because I use OpenDNS on my home network computers. I use 208.67.222.222 as my primary DNS Server and 208.67.220.220 as my secondary DNS Server. I will not use this list until this problem is fixed and posted here.
I hope that there is a post here when there is a fix for this problem because I use OpenDNS on my home network computers. I use 208.67.222.222 as my primary DNS Server and 208.67.220.220 as my secondary DNS Server. I will not use this list until this problem is fixed and posted here.
posted on 04/02/2010 at 06:48AM
fakhir (Founder) wrote:
@ BigEagle
This is not a problem as far as I am concerned.
If you have a problem with the contents then your options are to not use the list, contact the list author, or allow the IPs in your IP blocker.
Complaining about the contents of the list here will do nothing for you because in two years I have never removed an IP from a third party list.
@ BigEagle
This is not a problem as far as I am concerned.
If you have a problem with the contents then your options are to not use the list, contact the list author, or allow the IPs in your IP blocker.
Complaining about the contents of the list here will do nothing for you because in two years I have never removed an IP from a third party list.
posted on 04/02/2010 at 12:22PM
BigEagle (Member) wrote:
I contacted Atma.es via their website email regarding the problem with including the OpenDNS DNS servers' IP addresses in the Atma list. I gave them specific details and URLs and asked to please post a comment here if and/or when the problem gets fixed. If they fix (or have already fixed) the problem and tell me so in a reply email, then I will post that here for others like me to know if and/or when the problem gets fixed, that is if they (or somebody else) does not post a comment here like that before I get around to it.
I contacted Atma.es via their website email regarding the problem with including the OpenDNS DNS servers' IP addresses in the Atma list. I gave them specific details and URLs and asked to please post a comment here if and/or when the problem gets fixed. If they fix (or have already fixed) the problem and tell me so in a reply email, then I will post that here for others like me to know if and/or when the problem gets fixed, that is if they (or somebody else) does not post a comment here like that before I get around to it.
posted on 07/02/2010 at 01:28AM
BigEagle (Member) wrote:
Oh yeah, I forgot to mention: thanks for reminding me about adding the IP addresses to the allow list, duh! I was very tired when I posted my original comment about the problem with the OpenDNS servers' IP addresses and I was not thinking as clearly as I should have been. I frequently spend long hours on my computers and lose track of time and other things like sometimes common sense. I apologize for any trouble I may have caused anybody. But I am still hoping that the problem gets fixed, especially since I spent so much of my time already trying to solve it.
Oh yeah, I forgot to mention: thanks for reminding me about adding the IP addresses to the allow list, duh! I was very tired when I posted my original comment about the problem with the OpenDNS servers' IP addresses and I was not thinking as clearly as I should have been. I frequently spend long hours on my computers and lose track of time and other things like sometimes common sense. I apologize for any trouble I may have caused anybody. But I am still hoping that the problem gets fixed, especially since I spent so much of my time already trying to solve it.
posted on 07/02/2010 at 03:01AM
BigEagle (Member) wrote:
I got an answer from Atma.es regarding delisting the OpenDNS IP addresses. They said that only 208.67.222.222 was a false positive on the Atma list. They implied that 208.67.220.220 was not even on the list.To get a timely updated Atma.es list, you need to set your IP blocker to look for the Atma list at http://www.atma.es/atma.p2p which should be fixed in about 4 hours from now. They said an updated list from I-BlockList might take several days.
I got an answer from Atma.es regarding delisting the OpenDNS IP addresses. They said that only 208.67.222.222 was a false positive on the Atma list. They implied that 208.67.220.220 was not even on the list.
posted on 07/02/2010 at 08:17PM
fakhir (Founder) wrote:
@ BigEagle
208.67.220.220 is not in this list.
Don't propagate false information.
Any changes to their list shows up here in 12-24 hours.
@ BigEagle
208.67.220.220 is not in this list.
Don't propagate false information.
Any changes to their list shows up here in 12-24 hours.
posted on 07/02/2010 at 08:54PM
BigEagle (Member) wrote:
I am sorry for, as you put it, propagating any false information that I was given by Atma.es. I had been, up to this point, using only I-BlockList lists and did not have any problems with any of them. This is a very good website and I appreciate all of the hard work that you do. I just recently decided that I had been using too many lists because I was spending too much time allowing IP addresses (or creating ranges of allowed IP addresses) that were on blocklists, so I changed my List Manager settings in PeerBlock.
I am sorry for, as you put it, propagating any false information that I was given by Atma.es. I had been, up to this point, using only I-BlockList lists and did not have any problems with any of them. This is a very good website and I appreciate all of the hard work that you do. I just recently decided that I had been using too many lists because I was spending too much time allowing IP addresses (or creating ranges of allowed IP addresses) that were on blocklists, so I changed my List Manager settings in PeerBlock.
posted on 08/02/2010 at 05:55AM
p-root (Member) wrote:
The ClamAV Antivirus cloud's dowloader ip is in the list : 75.101.163.230:80
http://download.immunet.com/
Atma
2010-06 Malware .....................: 75.101.163.230-75.101.163.230
Whois query : Amazonaws.com
CIDR: 75.101.128.0/17
OriginAS:
NetName: AMAZON-EC2-4
The ClamAV Antivirus cloud's dowloader ip is in the list : 75.101.163.230:80
http://download.immunet.com/
Atma
2010-06 Malware .....................: 75.101.163.230-75.101.163.230
Whois query : Amazonaws.com
CIDR: 75.101.128.0/17
OriginAS:
NetName: AMAZON-EC2-4
posted on 28/08/2010 at 09:01PM
the opendns ips are in this list for some reason 208.67.222.222
208.67.220.220