Blacklist Knowledgebase
- Home
- Blacklist Knowledgebase
Knowledgebase
Understanding BlacklistsBlacklist Removal
Blacklist Profiles
URIBL Advisory SitesRBL Advisories
Search
Empowering You, On Demand.At Impressionwise, we maintain one of the industry's most comprehensive and actively monitored email blacklist knowledgebases, encompassing over 230 major RBL (Real-time Blackhole Lists) and URIBL (Uniform Resource Identifier Blacklists) sources. This extensive coverage allows us to detect and assess blacklist threats in real time, helping organizations protect their sender reputation, ensure maximum deliverability, and proactively mitigate risks before they impact campaign performance or inbox placement. To learn more about what an email blacklist is and how it applies to your email delivery, see Understanding Blacklists. Alternatively, you can search for a specific blacklist name.
Stop wondering and start knowing - Sometimes it’s easier to just ask. Please feel free to reach out to us with any questions to experience for yourself what sets Impressionwise apart! Understanding Email BlacklistingBlacklisting is a term that applies to the practice of identifying spammers based on the IP’s and domains that they send email from, then compiling this information into a list that can be referenced by email servers, which then blocks email from those IP’s being delivered to the intended recipient. This is an essential part of maintaining email as an effective tool, however based on the fact that blacklists operate on a largely independent and automated basis, they often mistake good senders for bad.
There are many specific reasons a blacklist may mistake a good sender for spam, but simply put, senders do not pay enough attention to their email marketing approach. If the only focus is to send email campaigns without understanding possible undesired effects, you’re potentially unintentionally triggering red flags and causing delivery issues. When properly managed, this risk can be entirely mitigated. This guide will get you on the right track when it comes to understanding the main concepts at play, and beginning to correct any bad email sending practice you currently have. Email blacklists explained
As you can see, there is a lot that goes in to determining your emails inbox status. Even if you do strictly follow email marketing best practices, you are at risk of being blacklisted inadvertently. Blacklists can frequently mistake legitimate senders as spammers due to their email sending habits. Common blacklisting triggers
Doing everything right and still on a blacklist?Even though you may be following best email practices to a tee, it does happen. The good news is that you can perform email reputation management by monitoring the blacklists on the web. Your ISP should be doing this on your behalf, however, if you’re keen to check this out yourself, you can go to http://multirbl.valli.org/ – a basic tool to monitor whether you are blacklisted. Simply type in your domain or IP and this free multiple DNS Blacklist service will cross reference other blacklists by IPV4, IPV6, or domain. If you are blacklisted, but believe you shouldn't be, or you’ve addressed the reasons that got you on to the list in the first place, you’ll need to take action to get your IP removed from the list. You can do this by applying for a “delisting” from the blacklist in question by contacting the blacklists’owner via their website. The key is to be proactive and address these issues quickly to prove to the ISPs that you’re serious about your reputation and about remedying your delivery challenges. Blacklist delisting guidelines
Now that you know more about email blacklisting, you’ll agree that basic email reputation management is one you don’t want to neglect. Don’t assume your ESP will always monitor this for you, your ESP cannot stop ISPs from receiving negative responses from your recipients in your database. It is up to you to maintain your brands reputation, and developing an effective marketing strategy on a foundation of email marketing best practices will prevent you getting blacklisted in the future. ISP InformationImpressionwise maintains these ISP reference tables for the benefit of senders and systems administrators working to improve email delivery. The “Sender Support” table below offers a quick reference to various ISP postmaster pages, FBL pages and unblocking pages. The second table, “Delivery and Filtering Details”, lists known connect limits, spam filters and certification services. Sender Support
Delivery and Filtering DetailsA little more information about the specifics of delivery at various ISPs. Note that the “does not publish” for limits means that the ISP has said they have limits, but they do not publish those limits specifically. Many of these ISPs tie sending limits to reputation; IPs with poor reputations have much lower sending limits than IPs with good reputations.
Threats API OverviewOur Hygiene API can be seamlessly integrated into your signup or onboarding process with just a single request. This high speed processing option is designed for continuous, real-time, data cleansing for cleansing an individual email address using standard HTTP methods. Structure and Definition for Inbound SubmissionsOur API requires you to authenticate each individual request. Below is an example of a basic URL structure request, just substitute with the provided account, associated password along with any optional parameters. Structure: https://post.impressionwise.com/fastfeed.aspx?CODE=000001&PWD=password1&<paramlist> Required Data FieldsParameters need to be separated by "&"
&CODE= 6 Digit Alpha-numeric, account code provided by Impressionwise = 000001 Optional System Fields&MX= To receive the MX domain information for an email address = 1 Optional Client Pass-thru Fields&MX= To receive the MX domain information for an email address = 1 Optional Client Pass-thru FieldsParameter's need to be separate by "&" = param1=value1¶m2=value2&...
&fname=test ** Maximum of 20 "other" variables. URL Structure ExampleA properly formatted URL post would resemble the following example as shown below. https://post.impressionwise.com/fastfeed.aspx?code=000001&pwd=askme&email=testme@impressionwise.com&fname=test&lname=me&addr1=123 sw 150 ave &addr2=&city=miami&state=FL&zip=33222&country=USA&phone=3057645678&gender=m&optinsite=www.impressionwise.com&optindate=2010-02-10&optinip=34.44.55.32 Parameters and UsageTo verify an email address simply use the request shown in the sample below substituting the required parameters with provided credentials and email address you want to verify. Sample = https://post.impressionwise.com/fastfeed.aspx?code=000001&pwd=password1&email=noexist@testme.com Upon successful posting of an email address, you can expect to receive the following response. Response = EMAIL=noexist@testmelink.com&RESULT=INVALID&TTP=2.41 Possible result parameter/values include:
&RESULT= "See below section Result Code section for additional detail" Error HandlingFrom time to time you may experience an API error. It is important to watch out for these and handle them appropriately. Specifically, if your submission contains an invalid account code or password the result response would be WRONG_PSW. Additionally, it has been our experience that with some smaller email hosts it is not uncommon for their reply to take an excessive amount of time to respond (sometimes more than 10 seconds). Due to this possible condition, you will receive a result code of RETRY. Upon reception of this response, please continue your HTTP submissions thru to completion of the entire data set to be submitted.. Once complete, please retry any/all responses with "RETRY" or as shown below: Response = EMAIL=noexist@testmelink.com&RESULT=RETRY&TTP=1.33 If you receive any other response other than those previously shown, please contact support. Result CodesThe recommended guidelines presented below will ensure you are adhering to email best practices, enabling more emails to reach the inbox. As a result, you will mitigate any risk associated with emailing to potentially "bad" addresses and you will experience additional opens, higher click through rates, increased conversions, and more revenue while protecting your online reputation. The recommended guidelines presented below will ensure you are adhering to email best practices, enabling more emails to reach the inbox. As a result, you will mitigate any risk associated with emailing to potentially "bad" addresses and you will experience additional opens, higher click through rates, increased conversions, and more revenue while protecting your online reputation.
Result Specifications
Version 1.0 Result Specifications
Net Protect (NPD) Codes (optional)To address specific deliverability challenges, use the network protected codes provided below to allow for individual classification suppression. NA = Not applicable or address is not a network protected domain or
010 = AppRiver The list of codes above, while infrequent, are subject to change. When a change occurs, generally a notification will be sent prior to any changes go live. Usage and GuidanceNetwork Protected Domains, and the recipients belonging to, are considered to be deliverable. However, the managed SMTP SaaS's are known to be highly collaborative, checking and notifying other leading industry DNSBL sites in real-time if email sent to an anti-spam solution is deemed spam. This section is designed to provide NOTICE ONLY as to which domains are being managed by a particular third party, anti-spam solution and aid in the delivery of your email. Recommended Usage: The anti-spam solution classifications are specifically designed to aid in deliverability challenges. For example, if you are unable to get any email through to any domain protected by a Barracuda appliance due to Barracuda labeling your email as spam, then using the Barracuda export would provide options not normally available. The sender could elect to suppress this domain grouping completely to protect the deliverability to the remaining certified domains within your list. The more popular option would be to take all the network protected domain groupings and send to them after you have sent all other data marked as good or certified to ensure optimal delivery footprint. Country Code Detail (optional)Due to the large number of country codes, a comma-delimited text file has been created for easy access and installation of code library into any existing application. This code library can be found at https://www.impressionwise.com/kb/CountryCodes.txt. The country codes are subject to change. While changes or new changes are rare, please check back monthly to ensure the version you downloaded is current. Domain Origination Note: Sourced from IANA’s database of TLD extensions, proprietary views as provided by domain registrars and Regional Internet Registries (AfriNIC, APNIC, ARIN, LACNIC, RIPE). Assessment is based off the geographic location of the originating IP that the MX record points to establish if domain is of domestic US or international origin. Supplemental confirmation utilizing corresponding RIR's SWIP and Rwhois data where possible. General Disclaimer: Every reasonable effort is made to locate all known threat and delivery classification elements mentioned herein, yet due to the constantly changing and dynamic nature of the online environment, we can not guarantee the results or deliverable will be free of any/all traps, threat or delivery classification elements identified within this report. While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Impressionwise does not accept responsibility for any kind of loss resulting from the use of information provided. Questions? Please feel free to contact us with any questions or specific customization requirements you may have regarding our automated, data cleansing feed services to ensure a successful evaluation or use of our services and let the results speak for themselves! Service Credits Balance API OverviewThe Service Credits Balance API provides a seamless way to check the current balance of your account’s service credits. This API allows users to retrieve their available service credits through a simple, automated process, making it easier to manage and track usage. In this overview, we will guide you through how to access and use the API, including instructions on authentication, endpoint details, and the parameters required to successfully check your service credits balance. By following these steps, you'll be able to integrate the API into your system for real-time updates on your account's service credits. Structure and Definition for Inbound SubmissionsOur API requires you to authenticate each individual request. Below is an example of a basic URL structure request, just substitute with the provided account, associated password along with any optional parameters. Structure: https://post.impressionwise.com/creditscheck.aspx?CODE=BBF&PSW=password Required Data FieldsParameters need to be separated by "&"
&CODE= 3 Digit Alpha-numeric, acccount code provided by Impressionwise = BBF. This code can be found in the Client Portal within the API Access section. Parameters and UsageTo retrieve the current service credits balance, simply use the request shown in the sample below substituting the required parameters with provided credentials and email address you want to verify. Sample = https://post.impressionwise.com/creditscheck.aspx?code=BBF&psw=password Upon successful posting, you can expect to receive the following response. Response = CODE=BBF&CREDITS=136,012&TTP=0.41 Possible result parameter/values include:
&CODE= "3 Alpha-numeric, account code assigned by Impressionwise = BBF”. This code can be found in the Client Portal within the API Access section. Error HandlingFrom time to time you may experience an API error. It is important to watch out for these and handle them appropriately. Specifically, if your submission contains an invalid account code or password the result response would be WRONG_CREDENTIALS. If you receive any other response other than those previously shown, please contact support. Questions? Please feel free to contact us with any questions or specific customization requirements you may have regarding our automated, data cleansing feed services to ensure a successful evaluation or use of our services and let the results speak for themselves! Bulk FTP TransferDesigned for automated, batched submissions of larger volume data sets. This service is designed for those clients who receive data on a regularly scheduled basis with 24/7 access to Impressionwise cleaning services without the wait time of traditional processing in a secure manner. Provided below is the site information required to access via FTP.
Place files within the \ToBeCleaned\ folder to begin cleansing process and results will be placed with a folder named \Cleaned\. Note: Only attempt to only upload delimited (tab, pipe or comma) files with extensions like txt, csv, xls, xlsx, zip, or rar. All other file extensions not listed will not be processed. You may upload a file containing as many fields of information as you wish, yet we require, at a minimum, the email address when scanning the files. Questions? Please feel free to reach out with any questions you may have about our cleansing process or your results, and we look forward to you experiencing the results that truly set Impressionwise apart! Bulk API List SubmissionSending a file by URLThe URL submitted must lead directly to the file and contain the type of input used, as well as any authentication credentials the request needs. The URL should be sent in the request as the input parameter and the input_type should be set to url. Below is an example request:
⇒ request POST (parameters need to be submitted in JSON format)
header "Content-Type: application/json"
url "https://www.impressionwise.com/app/api/create.aspx" data '{
"api_key" : "api key provided by Impressionwise",
}'
"input_type" : "url", "file_name" : "SampleFileAPI.zip", "input" : "url where file is located" Sending data directlyData submitted directly should exist as an array of arrays or an array of objects. The data should be sent in the request as the input parameter and the input_type should be set to data. Below is an example of this request:
⇒ request POST (parameters need to be submitted in JSON format)
header "Content-Type: application/json"
url "https://www.impressionwise.com/app/api/create.aspx" data '{
"api_key" : "api key provided by Impressionwise",
}'
"input_type" : "data", "file_name" : "SampleFileAPI.txt", "input" : '[
[
]'
"PeteyCruiser@testing.com",
],"Petey Cruiser" [
"AnnaSthesia@testing.com",
]"Anna Sthesia" Request ResponseWhen you submit a list via the API, the verification process will start automatically. If your credit balance is insufficient, the verification of your list will fail. You can purchase credits from the portal.
JSON Response
{
"status" : "success",
}
"token" : "b14a7c5c-a104-48c9-a522-22e9f1b79f6", "execution_time" : 10 (value in seconds) If an error occurs, the response will look like the below example:
JSON Response
{
"status" : "fail",
}
"description" : "Error downloading file. Please check it and try again" The failure description may vary depending on the type of fail action. Examples of common failure messages are:
Once you receive a response, you will want to store the value of the token, as it will be used to check the status and eventually retrieve the results. Checking the file statusNow that your list is running, you will need to poll the API and check the status periodically. For the first status check we recommended to wait approximately one minute until our cleaning system begins processing the file. For smaller lists (<50k) polling every 5-10 seconds is acceptable, but for larger lists (>50k) you’ll want to poll less frequently. Request Status
⇒ request GET\
url https://www.impressionwise.com/app/api/status.aspx?token=b14a7c5c-a104-48c9-a522-22e9f1b79f65
JSON Response
{
"status" : "success",
}
"token" : "b14a7c5c-a104-48c9-a522-22e9f1b79f6", "filename" : "SampleFileAPI", "created" : "2018-05-12 20:00:06", "started" : "2018-05-12 20:00:21", "checkpoint" : "exported", "finished" : "2018-05-12 21:52:46", "originalrecords" : 30000, "dedupedrecords" : 30000, "indeterminate" : 0, "invalidrcpts" : 2300, "catchall" : 0, "threat" : 6, "cert" : 20000, "suppress" : 10000, "dormant" : 0 In the response, the status parameter will indicate what the list is currently doing. Typically, status will be the only parameter you will need to watch. However, you may find the additional fields useful for monitoring list progress or to view a breakdown of the results in your list while it’s processing. "status" : This top-level job progress field contains one of four possible conditions. Shown below are these possible conditions and associated descriptions.
"checkpoint" : If you wish to follow the cleansing process in greater detail and the status condition = running then use the checkpoint field to determine job progress. Below are the possible condition descriptions.
Once the status value is set to success, you may begin retrieval of the results. Retrieving the ResultsNow with the cleansing process complete, it’s time to view our findings. Downloading Results
⇒ request GET\
url https://www.impressionwise.com/app/api/download.aspx?token=b14a7c5c-a104-48c9-a522-22e9f1b79f65
The data will be returned in a zip file containing the results. Example: SampleFileAPI.zip The following export files contain the full row of fields initially provided in comma-delimited or CSV files unless noted otherwise:
All file exports are formatted following the same field structure as provided with an additional field appended named “mxgroup” (Certified and Discretionary) or “threatclass” (Suppress). These file exports are sorted in ascending order (A-Z) using one of the two appended fields. The “mxgroup” field identifies the domain/ organization responsible for handling the reception and acceptance or filtering of email for that particular email address. For more information, see Delivery Group section. General Disclaimer: Every reasonable effort is made to locate all known threat and delivery classification elements mentioned herein, yet due to the constantly changing and dynamic nature of the online environment, we can not guarantee the results or deliverable will be free of any/all traps, threat or delivery classification elements identified within this report. While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Impressionwise does not accept responsibility for any kind of loss resulting from the use of information provided. Questions? Please feel free to reach out with any questions you may have about our cleansing process or your results, and we look forward to you experiencing the results that truly set Impressionwise apart! URI AdvisoriesShort for Uniform Resource Identifier Blacklist”., is a company/ website that produces a list of domain names observed sending spam or other undesired email content. As subscribers to the URI advisory, ISPs and companies will know from which domain names appearing in the email from which to block traffic. Most traffic blocking occurs during the SMTP connection phase. The receiving end will check the URI for the connecting or sender domain name. If the domain name matches one on the list, then the connection gets dropped before accepting any traffic from that email sender. For a complete understanding of the blacklisting process and how it can affect your email delivery as well as your sender reputation, see our Understanding Email Blacklisting help doc. The various URI’s have different policies yet generally encompass the three major points:
Impressionwise maintains the largest most complete knowledgebase of known anti-spam, URI or domain-based blacklists that can affect your online sending reputation and deliverability of your emails. Highlights include detailed information for each site:
Blacklist profilesTo view our knowledgebase of known anti-spam, URI or domain-based blacklist profile select from one of the following below.
For additional guidance or any questions you may have, please contact us. RBL AdvisoriesShort for Realtime Blackhole List, is a company/ website that produces a list of IP addresses observed sending spam or other undesired email content. As subscribers to the RBL, ISPs and companies will know from which IP addresses to block traffic. Most traffic blocking occurs during the SMTP connection phase. The receiving end will check the RBL for the connecting IP address. If the IP address matches one on the list, then the connection gets dropped before accepting any traffic from that email sender. For a complete understanding of the blacklisting process and how it can affect your email delivery as well as your sender reputation, see our Understanding Email Blacklisting help doc. The various RBL’s have different policies yet generally encompass the three major points:
Impressionwise maintains the largest most complete knowledgebase of known anti-spam, RBL or IP-based blacklists that can affect your online sending reputation and deliverability of your emails. Highlights include detailed information for each site:
Blacklist profilesTo view our knowledgebase of known anti-spam, RBL blacklist profile select from one of the following below.
For additional guidance or any questions you may have, please contact us. Blacklist Removal ProcessFor a complete understanding of the blacklisting process and how it can affect your email delivery as well as your sender reputation, see our Understanding Email Blacklisting help doc. Determine why you are listedEach blacklist has their own listing criteria that may include technical listings, policy listings, and evidence based listings. Technical listings - are those that occur mostly from mail server configuration issues such as missing or incorrect reverse DNS records, missing on incorrect banner greetings, and mail servers operating in IP address space that an ISP has specified that mail servers should not be operating in. Policy listings - are those based on an operator that does not wish to receive email from certain countries, or ISPs, or has a history of not honoring unsubscribe requests. Evidence based listings - are those where the operator has receive direct (or indirect) evidence that an IP address has been involved in sending unsolicited emails. For additional guidance, Impressionwise maintains the largest most complete knowledgebase of known anti-spam, IP and domain-based blacklists that can affect your online sending reputation and deliverability of your emails. Resolve the underlying issue(s)Once you have determined why an IP address has been listed you can begin your internal process of resolve the issue. This is a good time to confirm that your network, mail server, and computers are properly configured. Common resolutions include: fixing forward and reverse DNS records, STMP banners, scanning all machines on the network for viruses, patching operating systems, configuring routers more securely, and enforcing strong passwords. Follow the blacklist removal processAfter you have fixed the issues you'll need to go back to the blacklist's website and follow their specific removal process. Self-service removal - Some blacklists have a self-service removal feature. These generally allow for near immediate removal from the blacklist. Be sure that you've resolved the issue before doing this. When an IP address gets listed again after removal the process can become more difficult. Time-based removal - Most blacklists do not offer self-service or manual removal. They have a process that runs that will automatically remove low-level listings within a week or two. If the IP address has been involved in sending spam multiple times or in high volumes this process may take longer. Things to keep in mind when contacting a blacklist operatorDon't lie - Don't tell the operator you've resolved the problem when you haven't. If you lie that you've resolved the issue and it happens again they will likely not talk to you anymore. Keep it polite and professional - When you are having difficulty in removing a listing let them know what you are trying to do to resolve the issue. The more professional you are with them the more they'll be willing to help you resolve the issue. They are trying to stop people from receiving spam, not trying to keep you from legitimate non-spam correspondence. For additional guidance or any questions you may have, please contact us. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The recognized authority in email verification, threat intelligence and blacklist monitoring services
Impressionwise is trusted by organizations worldwide for industry-leading email hygiene solutions. We invite you to connect with us to explore how our services can deliver maximum value to your business.
Try it Now