Currently we use both, but it's probably wrong:

radare2 on  master [$?] 
[i] ℤ rg __WINDOWS__ | wc -l                                                                                                                                                                                                       17:44:21 
377
radare2 on  master [$?] 
[i] ℤ rg _MSC_VER | wc -l                        

The gist of it is:

• Look at url and domain attributes.
• If url, extract domain and add a domain attribute.
• Run similarity scorer on the domains using #734 (hides then commonly visited domains)
• Do some sort of analysis on the domains... either the ones that are not commonly visited or all of them... ideas would include something like:
  • VT or some other domain service l

The project works with 8 modules < reference source/Module >

• Creating issue to accelerate/track test frame building of each module
• The test folder has a very basic example to start with.
• Feel free to make a pull request for the test cases

Right now a lot of the logging from the tasks does not get propagated back to the user, so we should make sure that all of the tasks are adding logs and errors to the results so that at minimum the data gets put into the worker-log.txt. Ideally we would store this info in datastore so that the clients could query it later (this part is in #115).

If somebody has time, it would nice to have an https://intelx.io module for your project.
We have a SDK here with some code samples (including Go code): https://github.com/IntelligenceX/SDK