SPFBL DNSBL

The SPFBL DNSBL is a Brazilian-based blacklist. It collects reputation data and spam reports to create a real-time blocklist of IPs sending spam.
Updated on 17 Jun 2026: We updated this guide with SPFBL's return codes, DNSBL usage limits, and current delisting requirements.
Summarize with
Check if you are listed on SPFBL DNSBL
And 143 other blocklists.















What is SPFBL DNSBL?
The SPFBL DNSBL is an IP-based blocklist (or blacklist) from Brazil. Its primary goal is to identify IPs that are unsuitable for sending email, with a strong focus on reducing spam originating from or targeting Brazilian recipients. It operates as a Real-time Blackhole List (RBL), using the zone dnsbl.spfbl.net.
The blacklist builds its reputation database from data provided by its customers and a network of contributors. When recipients file a complaint about an email, the system processes it and can return a listing code for the sending IP. SPFBL states that this DNSBL should not be used to reject mail during the SMTP transaction. Treat it as a scoring signal for filtering decisions, such as routing suspicious mail to the junk folder.
Who runs SPFBL DNSBL?
SPFBL DNSBL is operated by the Brazilian organization SPFBL. It was created in late 2015 to combat the high volume of local spam. Since its creation, it has been publicly available for mail server administrators to use as one signal for filtering spam sources and protecting their infrastructure.
What do SPFBL DNSBL return codes mean?
SPFBL DNSBL returns different DNS responses depending on the query result. These codes matter because a listed IP is not always listed only for confirmed spam. Some responses point to poor rDNS, missing responsible-party information, a residential or NAT connection, or an abuse team that has not handled reports for the same IP range.
- FORMERR means the query format is invalid.
- NXDOMAIN means SPFBL has no reported abuse for that address.
- REFUSED means the querying server has exceeded the service limit, which SPFBL lists as 10 queries per second.
- 127.0.0.2 means the IP is blacklisted due to bad reputation confirmed by anonymous complaints.
- 127.0.0.3 means SPFBL has difficulty identifying who is responsible for abuse, or the MTA does not comply with RFC 5321.
- 127.0.0.4 means SPFBL did not identify an email service, or it considers the IP a NAT router or residential connection.
- 127.0.0.5 means SPFBL considers the abuse treatment team unreliable for the same IP range.
How do I get removed and delisted from SPFBL DNSBL?
SPFBL provides a self-service removal process on their website. Before you request delisting, resolve the underlying issue that caused the listing. The IP address also needs an active email server running, because SPFBL does not process delisting requests for IPs without one. SPFBL offers both a free and a paid delisting path, each with specific requirements.
Free delisting requirements
- The IP address must have a valid reverse DNS (rDNS) record that points back to the mail server IP, with FCrDNS validation.
- The rDNS must belong to the MTA administrator's domain, not a generic ISP or data center domain. The domain's TLD cannot be a free TLD and must have a public WHOIS record without privacy protection.
- A 'postmaster' email account must be active and able to receive email for the domain in the rDNS record.
- If you use IPv6 with the SLAAC flag, keep port 25 open so SPFBL can verify an active SMTP service.
- The IP's reputation score must have less than 25% negative points relative to its total sending volume.
Paid delisting requirements
Paid delisting is an option for administrators who cannot meet the strict free delisting criteria. The payment registers your PayPal email as the responsible party for any abuse from the IP. This allows repeated delistings of the same IP without new payments, provided you address future abuse reports sent to that email.
- The IP must be static and have a configured mail server reverse record, even if FCrDNS is not valid.
- You must use a PayPal account for the transaction. The associated email address will be publicly assigned to the IP as the contact responsible for abuse.
- The email address used in the delisting process will receive abuse reports for that IP and must be monitored.
- The IP's reputation score must remain below 25% negative points.
What's the impact of being listed on SPFBL DNSBL?
The impact of being on the SPFBL DNSBL blacklist is generally low for senders who do not have a significant audience in Brazil. The blocklist is primarily used by Brazilian mail servers and companies. However, if your business communicates with customers in Brazil, being listed can have a major impact on email deliverability to that region.
A listing can indicate spam complaints, but it can also point to infrastructure problems such as weak rDNS, missing responsible-party information, an IP that looks residential, or a mail server that does not meet expected MTA rules. Read the returned code before assuming the cause.
Even with a low global impact, any blocklist or blacklist inclusion is a sign of a potential problem with your email program. It can indicate a compromised system, misconfigured authentication, or poor sending practices. Addressing the listing is recommended to maintain a healthy sender reputation.
