Removals and Listings 2017

Trends and Data: 2017 – (ED: published on 7 January 2018 – Please be aware that removals are now(2022) done only at

During 2017 saw a huge increase in data users using software such as spamassassin for “scoring” and not for mailserver ‘blocking’ or drop.

During 2017 Ascams provided millions of data records free of charge to the planet. It is our driving principle to provide reliable, fresh and updated data to anyone and everyone. (individuals, companies or even large multinationals) Everyone has free and open access to millions of fresh, regularly updated data records.

Outgoing data 2017: around 2.5 million IP numbers were removed from our active public data lists during 2017.

Incoming data 2017: had ZERO (0) “false positives” for 2017 works differently to other data lists. We do allocate reaction and ‘cleanup’ scores to various resource operators. The best increase in cleanup and response time for 2017 was achieved by


Please note: DOES NOT BLOCK ANYONE or ANYTHING – We simply provide a database of IP numbers that in some way is or was involved in Internet Abuse.

Removal from our data lists:

Removal is done by hand and involves an investigation into each IP number requesting removal. This can be as quick as 7 days to as long as 30 days or more. There is no instant removals at and there is no way to override or cheat the system. removals depends on multiple factors.

Firstly, are you the resource owner? or are you just a client of the resource owner? What is the history of the IP number? We do realize that you do not care if the IP number was used by pedophiles, slave traders, scammers or sno shoe spammers and all that you may be interested in is simply using the IP number. Unfortunately – we do care and unfortunately we do not care about what you want to do.

If you are struggling to have an IP resource removed from our active listings please consider that the score for the resource owner may be so high that a removal is impossible without the actual resource owner becoming involved in the cleanup score reduction. Some resource owners, all over the planet, have such high scores that their listed resources cannot be removed by a “client” of the actual resource owner.

Before you purchased, rented or received the IP number resource the resource may have a history of abuse without anyone being able to do anything about the abuse from this resource. Removal for this resource may be impossible as much time as well as a completely new resource owner may be required for this resource to become usable again.

Have you actually informed that you have established what the issue is?

Have you actually informed that you have stopped the abuse?

Have you actually (as in really) stopped the abuse?

Many resource operators inform us that they take abuse complaints seriously and that they have stopped the abuse. If investigations then reveal that the abuse is in fact ongoing the reputation score of the resource operator (and resource owner) is negatively affected as they have lied to and attempted to defraud by sending a fake removal request. Any removal request from anyone with an internal reputation score of over 80/100 is treated differently to a request from a high reputation source.

Many resource owners are non responsive to abuse complaints. (For example Such resource are automatically listed and will only be removed once the resource owner informs us that they now accept and will react/respond to abuse complaints and that abuse from their resources will in fact stop.

Each removal or de-listing from active lists is properly investigated. ( has many different types of data lists and data sets. For example: active and non active, historic and reputation lists. Private and Public lists and many more.)

Here is the rough process when a removal request is received:

System check if it is a valid, single IPv4 number (IPv6 works on whitelist – IPv4 has no whitelist)
System produces history report for the resource and allocates the request to a human person
Human person checks the reputation score of the resource owner as well as the separate (different) reputation score of the resource user
Human person decides, based on ruleset guide, what the next actions are

Actions include:

Allocate for investigation, Check all other public data sets as well as dates of reported abuse, Check if any abuse has been reported to the resource owner and the response (if any) from that resource owner, adjust reputation scores as per guidelines, update systems, escalate to spam deputies, escalate external, escalate to board, escalate to discussion boards, Allocate to other human person, Allocate to system for record and dispose