```json
{
    "title": "Blocking Anonymizer Hits",
    "url": "https://performancezen.com/2005/03/11/blocking-anonymizer-hits/",
    "datePublished": "2005-03-11",
    "dateModified": "2005-03-11",
    "language": "en-US",
    "description": "Someone has been abusing the Anonymizer system and hammering my system. Again, IPTABLES is my friend. /sbin/iptables -A INPUT -s 168.143.113.125 -j DROP This IP Address points to vortex.anonymizer.com. dig…",
    "author": "spierzchala",
    "publisher": "Performance Zen"
}
```

# Blocking Anonymizer Hits

Someone has been abusing the Anonymizer system and hammering my system. Again, IPTABLES is my friend.
/sbin/iptables -A INPUT -s 168.143.113.125 -j DROP
This IP Address points to vortex.anonymizer.com.

dig -x 168.143.113.125
; <<>> DiG 9.3.0 <<>> -x 168.143.113.125
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52723
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;125.113.143.168.in-addr.arpa. IN PTR
;; ANSWER SECTION:
125.113.143.168.in-addr.arpa. 10800 IN PTR vortex.anonymizer.com.
;; AUTHORITY SECTION:
113.143.168.in-addr.arpa. 10800 IN NS ns1.infonex.net.
113.143.168.in-addr.arpa. 10800 IN NS ns2.infonex.net.
;; ADDITIONAL SECTION:
ns1.infonex.net. 172693 IN A 168.143.113.201
ns2.infonex.net. 172693 IN A 168.143.113.202
If someone at Anonymizer can bring these requests under control, I will turn the access back on.