It provides response formats: xml, json, csv, newline separated, serialized php. And enforce a limit of 240 requests per minute (that's 14,400 per hour for the lazy).
Fun fact, if you're running tor (tor-0.2.4.17 as proxy not the browser) you'll see the tor exit node in "IP:" and your actual ip i "Real IP:", thanks to gdns' EDNS (https://gdns.re/edns-demo/)
https://trac.torproject.org/projects/tor/wiki/doc/Preventing...
I disagree, but have you said it is down to my inability to explain what the problem is, then I agree.
I'm aware of the DNS leaks, and obviously wasn't clear enough and failed to explain what the problem was.
The leak only happens when you run the tor proxy daemon, and your own browser with the appropriate proxy settings.
It's down to the way Firefox, uses the defined proxy for the initial DNS and HTTP requests, but then bypasses it when doing DNS lookups for JS within the initial page loaded.
It doesn't leak DNS lookups made by JS scripts if you use the tor version that includes a mod-Firefox browser.