AG

@Ice3man543 FYI I just started on this an hour ago.. right now it is only stdout for dir mode, but it shouldn't take more than another hour or two to...

Output currently looks like this: ``` $ ./gobuster.git -J -w ../raft-medium-words-lowercase.txt -u http://localhost -X OPTIONS -e {"Expanded":"true","Mode":"dir","Output file":"","Status":"starting","Status codes":"200,204,301,302,307","Threads":10,"URL":"http://localhost/","level":"info","msg":"Scan initializing","time":"2018-03-04T02:16:40-05:00"} {"URL":"http://localhost/javascript","level":"info","msg":"HIT","size":-1,"status":301,"time":"2018-03-04T02:16:40-05:00"} {"URL":"http://localhost/out","level":"info","msg":"HIT","size":-1,"status":200,"time":"2018-03-04T02:16:40-05:00"} {"URL":"http://localhost/.","level":"info","msg":"HIT","size":-1,"status":200,"time":"2018-03-04T02:16:40-05:00"} {"URL":"http://localhost/httpd","level":"info","msg":"HIT","size":-1,"status":200,"time":"2018-03-04T02:16:40-05:00"} {"URL":"http://localhost/test2","level":"info","msg":"HIT","size":-1,"status":200,"time":"2018-03-04T02:16:40-05:00"} {"URL":"http://localhost/test1","level":"info","msg":"HIT","size":-1,"status":200,"time":"2018-03-04T02:16:40-05:00"} {"URL":"http://localhost/redirector","level":"info","msg":"HIT","size":-1,"status":200,"time":"2018-03-04T02:16:40-05:00"} ... ```

@Ice3man543 this is meant to be consumed line by line at runtime (in real-time) by a third party tool. If the user wants full results at the end they should...

@c0rvax @OJ one note on this, stepping back from the whole heuristic/detection deal, I will give you an example of the useful "ignore specific size" length feature.. you are right...

@OJ will you take a PR for this? Pretty reasonable functionality right? I would *almost* argue it's a bug, but it's really more paranoia by default on the part of...

I understand you're trying to ignore NXDOMAIN, SERVFAIL and REFUSED, but maybe what you really want to do is whitelist what you want instead? Via `--filter NOERROR`?

Use this instead: https://github.com/blechschmidt/massdns/blob/master/scripts/massdnsA.jq EDIT: If I'm misunderstanding your issue, please attach your list of hosts and resolvers, I'm happy to try quickly to reproduce the issue

I would recommend you confirm that the resolvers you're using are in-fact public recursive resolvers. All of them. When troubleshooting, use `--predictable` to cause the same resolvers to be used...

@blechschmidt thanks for the detailed response and the tips on the implementation- it would be quite bad to `tolower()` a label length byte by accident :) Let's leave this open...

I would recommend experimenting with different hashmap size, socket count and interval settings. It seems very unusual to me, I don’t have any suggestions aside from those