Kerio Control does not rely solely on static blocklists. Instead, it uses . When a user requests a website, the Kerio appliance queries a remote categorization server (provided by Kerio’s parent company, GFI Software, or a third-party partner like McAfee). The server returns a category ID (e.g., 92 for “Gambling”). The appliance then applies your content rules.
This article explains why this message appears, the seven most common causes, and step-by-step solutions to restore full web filtering functionality. To understand the error, you must first know how Kerio Control’s web filter works. Kerio Control does not rely solely on static blocklists
By systematically working through the eight steps outlined above—license validation, enabling the engine, checking DNS and NTP, configuring an upstream proxy, and clearing corrupted caches—you can restore full web filtering in minutes. The server returns a category ID (e
Indirectly. HTTPS filtering (SSL inspection) is separate. However, if categorization is disabled, you cannot block HTTPS sites based on category, even if SSL inspection is on. To understand the error, you must first know
If categorization is disabled , the appliance cannot query the cloud. Consequently, no website receives a category, and all content rules dependent on categories fail silently.
nslookup categorization.gfi.com Alternatively, use (depending on version):
Kerio Control does not rely solely on static blocklists. Instead, it uses . When a user requests a website, the Kerio appliance queries a remote categorization server (provided by Kerio’s parent company, GFI Software, or a third-party partner like McAfee). The server returns a category ID (e.g., 92 for “Gambling”). The appliance then applies your content rules.
This article explains why this message appears, the seven most common causes, and step-by-step solutions to restore full web filtering functionality. To understand the error, you must first know how Kerio Control’s web filter works.
By systematically working through the eight steps outlined above—license validation, enabling the engine, checking DNS and NTP, configuring an upstream proxy, and clearing corrupted caches—you can restore full web filtering in minutes.
Indirectly. HTTPS filtering (SSL inspection) is separate. However, if categorization is disabled, you cannot block HTTPS sites based on category, even if SSL inspection is on.
If categorization is disabled , the appliance cannot query the cloud. Consequently, no website receives a category, and all content rules dependent on categories fail silently.
nslookup categorization.gfi.com Alternatively, use (depending on version):