What it is
DAN TOR (dan.me.uk/torlist) maintains a real-time list of active Tor exit nodes. Tor exit nodes are the final point at which anonymised Tor traffic re-enters the regular internet, making them appear to be the source IP of traffic that actually originated from an anonymous Tor user. This is not a spam list: it specifically targets anonymising infrastructure.
How it affects SMTP delivery
Some mail servers use the DAN TOR list to reject or flag mail originating from Tor exit nodes, on the basis that anonymous mail is more likely to be abusive. This is a policy decision by the receiving organisation rather than a deliverability reputation signal. Most legitimate senders are unaffected.
What causes a listing
An IP appears on DAN TOR exclusively because it is operating as a Tor exit node. If you are a Tor relay operator and your exit node is configured to allow SMTP, mail from that IP will be listed here.
How to get removed
There is no removal process. IPs are listed while they are active Tor exit nodes and removed automatically when they cease exit node operation.
For the full reference catalog, see the email blocklist directory.
Delisting process in detail
The DAN Tor Exit Nodes list (torexit.dan.me.uk) is not a spam blocklist in the traditional sense: it lists IPs that are active Tor exit relays. Delisting is not possible in the usual sense because the list is a factual enumeration of Tor exit nodes, not a judgment about spam behavior. To be removed, the IP must stop operating as a Tor exit relay. The list updates automatically as Tor exits come and go, typically within hours of a relay going offline. If your sending IP appears on this list, you are (or recently were) running a Tor exit relay on that IP.
Prevention practices
Preventing DAN Tor listings is straightforward: do not run a Tor exit relay on your sending IPs. Tor exit relays should be operated on dedicated infrastructure with no legitimate outbound mail traffic, both for legal safety and for network segmentation. If you inadvertently allocated a Tor-exit IP for sending, migrate to a fresh IP and verify against torexit.dan.me.uk before starting the warmup process. Some hosting providers list IPs that have historically been used for Tor even after the relay has been shut down; monitor for such stale listings.
Common listing causes
DAN Tor listings result from operating a Tor exit relay on the listed IP. There are no false positives in the traditional sense: the IP either is a Tor exit or is not. Legitimate senders who find themselves on this list either inherited an IP that was previously used for Tor, misconfigured a server that was intended for internal use as an outbound relay, or accidentally exposed a Tor-testing environment to production traffic. Rotating IPs from a hosting provider without checking their Tor exit history is the most common inadvertent cause.
Related blocklists
Tor exit IPs appear on multiple blocklists beyond DAN, including TorDNSBL and various commercial reputation services. Because Tor exits are used for both legitimate anonymous browsing and abusive traffic, many mail servers block them by default. Enterprise mail gateways that block Tor exits by policy usually query multiple Tor-specific lists rather than relying on general spam blocklists. If your sending IP is caught on any Tor list, the practical solution is IP migration rather than delisting attempts.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
