2 ms·
I think there are far more nameservers allowing AXFR than you think. Write a little app that attempts a zone transfer for the top 1000 of the Alexa list (http:/
by pmylund 15y ago
I think there are far more nameservers allowing AXFR than you think. Write a little app that attempts a zone transfer for the top 1000 of the Alexa list (http://s3.amazonaws.com/alexa-static/top-1m.csv.zip http://s3.amazonaws.com/alexa-static/top-1m.csv.zip) and see for yourself. (Note to anyone reading: Please don't try this before you've checked if it's legal in your state/country or not.)
Could you explain how you would learn about wide-open-dev-machine as simply as by using AXFR in your scenario (you aren't on the network, so no *casting).
Edit: "so what possible reason could there be for enabling it?" is eerily similar to my message :)
- tptacek 15y agoHere's your answer: imageshack.com about.com ehow.com sparkstudios.com yfrog.com liveinternet.ru pgmediaserve.com wikimedia.com adfly.com thefreedictionary.com amung.us btjunkie.com bluehost.com drtuber.com ero-advertising.com autohome.com.cn exblog.jp inetglobal.com milliyet.com.tr imagebam.com naukri.com bigpoint.com altervista.com hypergames.com gsmarena.com excite.co.jp admagnet.com macrumors.com linkbucks.com cracked.com traidnt.com radikal.ru paper.li eluniversal.com.mx wiktionary.org indianrail.gov.in docin.com 123rf.com perezhilton.com mangafox.com hostmonster.com myfreecams.com giveawayoftheday.com ultimate-guitar.com itpro1.nikkeibp.co.jp pantip.com hawaaworld.com 120ask.com 4.8%. That's more than I would have thought, but it's still a small number: 95.2% of the Alexa 1000 keep AXFR disabled. Also: someone should tell some of these people not to do this.
- pmylund 15y agoIndeed. Keep in mind it's the top, so these are the people you really expect to keep something like that hidden. I promise you the stats are much worse further down the list, or if you do the same, but for a specific country's TLD.