If the resource you are checking is listed, you can try to have the listing removed by firstly fixing the reason why the resource is listed. Each one of the millions of listed resources on superblock.ascams.com has recorded abuse originating from that resource.

superblock.ascams.com contains no false positives. “your” resource was responsible for scams, spam, phish, cyber crime, etc.

Removal: It is easy to apply for removal and be removed if the resource score is low.

  • The listing is younger than 12 months. Old listings means that the resource manager does not and did not care about abuse reports or listings on ascams.com.  The resource score will also be higher as listed resources gain points for each year of listing.
  • If the resource you are trying to remove has a single reverse DNS entry, matching the forward DNS and the name belongs to a real and/or known email server.
  • If the resource has a published Abuse contact email address which responds and manages abuse according to a published AUP
  • If the abuse from the resource has stopped for the reputation period (Each and every IP number has an ascams.com reputation score. The score increases depending on a number of factors, the resource score triggers a listing on any one of the 12 Data lists published by ascams.com)
  • The person applying is also the listed abuse contact for the resource

Listed resources WILL NOT BE REMOVED if:

  • They are not real email servers and not operationally sending and/or receiving any email (see the real ascams.com list for actual email server scores)
  • If the forward and reverse DNS does not match
  • If the resource whois does not publish or manage abuse according to a published AUP or other known policies.
  • If the resource score is too high. (if the same resource is also listed on other ascams.com lists and/or other reputable RBL)
  • If the resource is listed as DROP on dnsbl.ascams.com or if the resource is an automated spam service and is also listed on block.ascams.com – First remove the resource from all other lists and superblock.ascams.com as the last removal.

If you, the applicant is not the listed resource operator: Add a paragraph explaining your abuse of the Internet. If you are the resource operator, please be careful as a request from you will trigger an investigation and may have negative results if you lie to us, provide us with incorrect information or if you try to scam us.

You cannot pay anyone to be removed or added to any of our lists.

At ascams.com there are no magic unicorn fairy lists, such as “paid” sender score or “paid I may send unsolicited emails” lists or “clubs” whom are supposedly providing “ethical sending standards” – In fact, membership of “bulk email clubs” means that the scores allocated to your resources may be added to. Many such “ethical email marketing organisations” are in fact also listed on various RBL for abuse of the Internet.

We do not care if you are nice, mean, nasty, pleasant, unpleasant, sorry, not sorry, angry, friendly, pink, green, big, small, american, chinese, russian, marsian, from venus, nation state actor or even a unicorn with two fairy wings.

ALL we care about is the permanent reputation of your ipv4 or ipv6 resource.

We consider threats as cyber crime. Organised Bulk Email Groups (and countries, groups of service providers and other internet gangs) sometimes operate like a “mafia”. Organisations/Countries/Groups behaving like cyber criminals empowering the relay of bulk emails to random email resources will be listed and it will be difficult to have these resources removed.

If your IP resources are listed on Ascams.com ipv4 BLACKLISTS and:

– you request addition, such addition, such addition is performed if we deem it required (and it is possible to reset the resource score)

– you request removal, such removal may be possible if you follow these suggested guidelines for blacklist removal. Removal, if at all possible, is performed whenever us humans get around to it.

– Ascams.com blacklists contains NO FALSE POSITIVES so remember that “your” resources are listed because of abuse originating from it. If you have just received a “new” resource and it is listed on many RBL – and you wish to operate an email server, consider that you may require a different service provider. It may be a lot of work to clean the resource, it may take long or it may even never be removed. best is to involve the resource holder, get your service provider or abuse contact, to apply to del@ascams.com directly.

– Whereas it is true that “Everyone Leaks” or everyone sends SPAM, SCAMS, PHISH and Cyber Crime : The management (and actual application of your use policies) of your resource abuse is the single largest scoring factor on many blacklists. – If you do not allow your users to relay bulk email, if you do not allow your users to send unsolicited emails, if you do not allow your users to be involved in cyber crime and if you respond to abuse complaints by applying your use policies – your resource should be easy to remove or delist from any public facing blacklist. If you are a large, even multi national corporation, and you do not apply your use policies on an equitable basis to all of your assigned resources, you will face challenges with our scoring requirements.

Suggested Guideline for Addition and Removal Requests from superblock.ascams.com

Removal Requests Suggestion:

Check that the resource you are applying for removal for IS NOT STILL LISTED ANYWHERE ELSE OR WITH ANY OTHER RBL. (First remove your resource from all other reputable blacklists.)  Only after your resources are “cleaned”, then request removal from Ascams.com – unless you believe that your other listings are not relevant

Check your reverse DNS name matches your forward facing name

Check that at least port 25 is open, operational and not an open relay

Check that the resource has a published abuse contact and that the operator has published use policies which is actually applied and all operational.

Check the resource history: When last has it abused others? How old is the listings? Can this resource ever be used for an email server? (Please consider that a large percentage of ipv4 resources are basically ‘trash’ and will never be able to operate as email servers – it is easier to find a different service provider than to use certain resource ranges for email)

If you are sure of the above, you can apply:

In the subject line of a plain text email to del@ascams.com : Removal/Addition from superblock.ascams.com

In the BODY of the same plain text email: The ipv4/ipv6 resource number on the first line

You do not need to send anything else, if you are the resource operator. If you are not the resource operator, you can add additional information supporting the request below the resource number.

How long will it take for my resource to be removed from any blacklist?

If it is possible, removal is usually done between 24 hours and 30 days, depending on RIR and how many items your resource generates on our removal checklist. If your resource is still listed on other blacklists, we may contact those lists and require to receive feedback and additional information. Only after we have received the information and additional data will we be able to make a decision on the removal or non removal of your resource. If your resource has been on our lists for a period longer than 5 years, removal may no longer be possible without additional declarations. Please check the additional information in the answer, for more information.

You will/should never receive any feedback or any emails from ascams.com – Your resource will either be (1) added or (2) removed or (3) nothing will happen.

We consider it fair for anyone to submit one request per ip resource, per month.  Multiple requests in the same month will be considered abusive requests.

When a resource operator requests anything: Please be careful and please pay atention as your request will trigger an investigation and the outcome of that may not be positive if your resource(s) are known for abuse and you, as the resource operators, have not taken action in the past or have operated a @devnull abuse reporting system…