How to remove your IP from SpamRATS NoPtr

RATS-NoPtr flags sending IPs that have no reverse DNS. Fix the PTR record and you can clear it yourself.

Check your domain free → SpamRATS NoPtr removal tool ↗

What it is

The list, in plain terms.

RATS-NoPtr is one of the SpamRATS blocklists, published as the DNS zone noptr.spamrats.com. It collects IP addresses seen sending an abusive volume of connections, or attempting delivery to large numbers of invalid recipients at ISP and telco mail servers, where the distinguishing trait is that the IP has no reverse DNS (PTR) record. SpamRATS treats a high-volume sender with no PTR as almost certainly an infected machine or a misconfigured mail server.

SpamRATS is a reputation service used by receiving mail servers as a DNSBL. A NoPtr listing only affects you if you run your own mail server that sends directly to other servers on port 25. If you send through your provider or ISP and see delivery problems, removing the IP is not the fix — check your mail client configuration or ask your provider about authenticated submission on port 587.

The listing is behavioural and identity-based rather than a spam judgement: the operator states that no-PTR flood traffic of this kind accounts for roughly half of all wasted overhead facing mail servers. Legitimate mail servers are expected to have a reverse DNS record that identifies who is responsible for them.

Why you get listed

What a listing on SpamRATS NoPtr means.

No reverse DNS record The sending IP has no PTR record. Under email operator best practice, any IP running a mail server should have reverse DNS that reflects the responsible operator, such as mail.yourdomain.com or mx.yourdomain.com.

Abusive connection behaviour The IP was seen sending a flood of connections, or attempting delivery to many invalid users. The no-PTR trait combined with that volume is what triggers the listing.

A network that permits it The IP sits on a network known to allow outbound port 25 from addresses that have no reverse DNS. That combination is a strong signal of a compromised host or a poorly configured server.

How to get removed

Delisting, in order.

Removal is free. Fix the cause first — a listing you clear without a fix comes straight back.

1 Confirm you actually run a mail server on the IP. RATS-NoPtr only matters if this IP sends mail directly to other servers. If you send through your ISP or provider and mail is failing, do not remove the IP — check your mail client settings or switch to authenticated submission on port 587. Removal is neither needed nor appropriate.
2 Set a valid reverse DNS (PTR) record. Create a PTR record for the sending IP that identifies the responsible operator, for example mail.yourdomain.com or mx.yourdomain.com, in line with the reverse DNS naming conventions SpamRATS references. Reverse DNS is controlled by whoever owns the IP block, so you may need your hosting provider or ISP to set it.
3 Wait for DNS to propagate. Allow enough time for the new PTR record to propagate before you request removal. SpamRATS will not let you self-remove while the reverse DNS still appears missing.
4 Self-remove your IP. Look the IP up on spamrats.com and use the removal box on the RATS-NoPtr page to enter the address and clear it. Removal is self-service and free once the PTR record is corrected and has propagated.
5 If you cannot remove it, contact SpamRATS. If the PTR record is in place and propagated but self-removal still fails, use the SpamRATS contact form to raise the case. Do not pay any third party offering to speed up a SpamRATS delisting.

The official route

Straight to the source.

Removal happens on SpamRATS NoPtr's own tool — never through a paid service.

SpamRATS NoPtr removal tool ↗

Return codes

127.0.0.37 RATS-NoPtr — sending IP with no reverse DNS (also the NoPtr code in the combined RATS-All zone)

127.0.0.36 RATS-Dyna — separate SpamRATS list for dynamic/generic-PTR ranges, for reference

127.0.0.38 RATS-Spam — separate SpamRATS spam-source list, for reference

How long it takes

Removal is self-service and takes effect once you submit the request, provided the reverse DNS is corrected. There is no fixed queue: the gating factor is DNS propagation of your new PTR record, so allow time for that before you self-remove and re-check.

Common questions

About SpamRATS NoPtr, specifically.

Does SpamRATS charge to remove my IP from NoPtr? No. Self-removal on spamrats.com is free once you have fixed the reverse DNS. Any service offering to remove a SpamRATS listing for a fee is a scam — no third party is needed.

Why is my IP on RATS-NoPtr? Because the IP was sending an abusive volume of connections, or trying to reach many invalid recipients, while having no reverse DNS (PTR) record. SpamRATS treats a high-volume no-PTR sender as an infected machine or a misconfigured mail server.

I do not run a mail server — do I need to remove my IP? No. A NoPtr listing only affects you if you run a mail server that sends directly to other servers. If you send through your ISP or provider and mail is failing, the listing is not the cause — check your mail client configuration or ask your provider about authenticated submission on port 587.

How do I fix the reverse DNS? Set a PTR record for the sending IP that names the responsible operator, such as mail.yourdomain.com. Reverse DNS is controlled by whoever owns the IP range, so you may need your hosting provider or ISP to configure it for you.

I removed myself but got relisted — why? Either the PTR record is still missing or not yet propagated, or the abusive connection behaviour continued. Set valid reverse DNS and stop the flood of connections first, then remove the IP.

How long until the delisting takes effect? Removal is immediate and self-service once submitted. The only wait is DNS propagation of your new PTR record — allow time for that before you self-remove, then re-check the IP on spamrats.com.

The bounce behind the listing.

554 5.7.1 message rejected → The permanent bounce a listing most often triggers — what it means and how to clear it. 550 5.7.1 blocked → A rejection on reputation grounds — usually the same listing, seen from the sender side. Blacklist checker → Re-check your domain and every sending IP once the cause is fixed.

Do not fix it blind.

See every list you are on and every authentication problem behind the listing in one 40-second check — then let monitoring tell you the day a listing comes back.

Check your domain free → See monitoring