Hey All, We're trying to build a universal JSON recon data format that all tools will export to. We've got subfinder, amass, and aquatone on board to make integrations. Now we just need a kickass standard. LMK your thoughts.https://github.com/Rhynorater/ReconJSON/ …
Why a separate "ip" field? It should be covered under dns IMO. With RR DNS A records, it's impossible to tell which IP should be in that field.
-
-
Thanks for the feedback,
@avlidienbrunn! My thought for breaking out the ip address field is that different ips (sometimes even RRed ips) have different ports open and describe different hosts. IMO there has to be something that defines which host we're talking about. Thoughts?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Company is kind of weird too, owns the IP? Owns the server/application? Owns the apex domain? Whatever is listed in WHOIS? It makes sense from BB perspective, but in my opinion it shouldn't be in the format :)
-
Good thoughts here - there is quite a bit of ambiguity to that. I think I'll add detail to that then ping you go check. Also, will move it to optional parameters.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.