File sites.json

The sites.json file contains all the blacklists to generate. Complies with the following format:

{
   "blacklistbox": [
      {
          "maintainer": "Cisco Talos Intelligence Group",
          "mainurl": "https://talosintelligence.com",
          "category": "reputation",
          "url": "http://www.talosintelligence.com/documents/ip-blacklist",
          "list": "HN-BLACKLIST-TALOSINTELLIGENCE",
          "comment": "TALOSINTELLIGENCE-IP-BLACKLIST",
          "delimiter": "",
          "mask": false,
          "subnet": "",
          "protocol": "IPv4"
      },
      { 
            "... more ..." 
      }
   ]
}

Values:

• maintainer: Name of company or person that maintains the updated list.
• mainurl: Maintainer's website.
• category: Categories (Example: malware, botnet, spam, bruteforce, bots, adservers, tor exits nodes, tor relays, cidr, voip, ssh, telnet, reputation, compromised, abuse, attacks, webbot, portscanner & more).
• url: File URL in plain text or RAW blacklist format.
• list: Name of the list file to be created in RSC format. Prefix required "HN-BLACKLIST-" + Name. (Example: "HN-BLACKLIST-TOR-EXITS-NODES")
• comment: Comment that is added on each line. You can use this to work with scripting. (Example: "TOR-EXITS-NODES")
• delimiter: Delimiter. If the file has a character other than a line break \n, you must specify it. Use "" to skip the step. (Example: " ", "-", "" & more)
• mask: Use true or false if the list has a netmask (Format: IP + /21, IP + /24 & more).
• subnet: If the list has the netmask fixed in a different format specify the netmask (Example: "/24", "/21" & more).
• protocol: Support for IPv4 and IPv6. If your list is IPv4, indicate that format, otherwise indicate IPv6. If your list has both IPv4 & IPv6 formats, create a list for each. Add to filename -IPv6.

In case you need to add a new list to BlackListBox, do a fork main and send a pull request. Please verify the file with JSON Formatter respecting the VALID format (RFC 8259).