Ending up on a deny list can be detrimental to your domain’s email deliverability. These days, there are hundreds, maybe thousands of deny lists out there. Some, like the Spamhaus SBL, can have a great impact on your email deliverability, while others may not. Many of the world's largest inbox providers use deny lists to help them make inboxing and filtering decisions. Others rely only on their own internal metrics. No action should be taken with listing entities requesting a fee for delisting or stating they do not accept requests to delist. If you find that your IP address has been added to a deny list by a legitimate entity, then submitting a delisting request would be recommended. Depending on your plan, you should approach being added to a deny list in one of 2 ways:
If you are on one of our shared IP plans and you notice a block message from Spamhaus based on one of our IP addresses, please know that we are already working with Spamhaus directly to address the issue. There is no need to make an additional request through our support team.
If you are on one of our shared IP plans and you notice a block message from any other deny list based on one of our IP addresses, please note that blocklists are a natural part of sending through shared IP Pools with multiple senders utilizing the same set of IPs. The large majority of these blocklists do not have an impact on your deliverability and often self-mitigate over time. We are actively monitoring these listings to ensure appropriate actions are taken for any that may impact our senders' deliverability.
We ask that our dedicated IP plan users make the initial delisting request in the event that they discover their SendGrid IP on a deny list. These IP addresses are only assigned to one account at a time, so we expect those users to take responsibility for all of the mail that is sent through their account. SendGrid will still be happy to step in and assist with these delisting requests if the listing service requires the IP administrator to take action, or if the delisting form is too complicated.
In the event that a sending domain (and not the IP address) is added to a deny list, the domain’s controller will be responsible for handling the delisting request.
Here are 2 aggregation websites that anyone can use to check on the status of their IP:
Below are links to the delisting forms used by the more popular external deny listing services:
If you request a delisting from a deny listing service, and don't do anything to change the behavior that caused the listing in the first place, it is likely to occur again. Depending on the list, it can be progressively harder to get delisted after the second or third listing.
Don't delist from major deny lists without a plan in place to address the issue that caused the listing! Learn more about how to avoid and mitigate risk of being added to a deny list here.
Let us know how we’re doing! Please rate this page:
Please note, we cannot resolve account and login issues reported on GitHub. Contact support for account assistance.
Thanks for helping us improve our docs!