Botnet Site Exceptions

You can create exceptions to the Botnet Detection sites list. These entries are configured and processed as Blocked Site Exceptions. When you add a site to the exceptions list, traffic from that site is not blocked, even if it is included in the Blocked Sites list as a result of the Botnet Detection feature. Traffic from sites on the exceptions list is also not automatically blocked by features such as Default Threat Protection, and by block actions configured in a proxy policy. For more information, see Create Blocked Sites Exceptions.

When you add a site to any one of the Botnet Detection Exceptions, Geolocation Exceptions, or Blocked Sites Exceptions lists, the site is not blocked by any of these services or Default Packet Handling.

For example, if you add www.example.com to the Geolocation Exceptions list, then Botnet Detection, Blocked Sites, and Default Packet Handling also do not block the site. If you already added a site to one exception list, you might see an error if you try to add the site to an exception list for another service.

You can add an exception for:

  • IP address
  • Network IP address range
  • Host IP address range
  • Host name (one time DNS lookup)
  • FQDN (includes wildcard domains).

For more information about how to use FQDN in exemptions and policies, see About Policies by Domain Name (FQDN).

See Also

About Botnet Detection

Configure Botnet Detection

Configure the Botnet Detection Update Server