Feature Requests

Allow users to create blocklist or allowlist entries using wildcard patterns for top-level domains (TLDs). For example, users could allow or block all subdomains associated with a base domain using a single entry such as example.* or example. to cover example.com , example.net , and other related TLDs. This feature would streamline domain management for customers who need to apply filtering rules across multiple domains with shared base names, reducing the need for multiple, repetitive entries.

Currently on this screen you can add to specific policy's allowlists but not the universal allowlist.

It would be advantageous to have the ability to set an expiry on a domain in the allow list when created. We often have users needing access to a page while it is investigated by support or web developers who need access to newly created domain. It does not make sense to leave them allowed once the initial categorisation no longer applies (domain ages or site is no longer a threat)

Request the ability to use RegEx or at least multiple wildcards within the Blacklist/Whitelist, to allow for targeting domains such as .some-text. (to cover any and all domains with 'some-text' within the domain). For example: .gettyimages. - - which uses a variety of TLDs that are constantly changing / being added.

Also being able to tag in order to sort allowable domains by category would be good.

Similar to Cisco Umbrella destination lists, this would give an ability to group together URLs in an allow list for better readability and management on what those URLs are used for

The notes feature is appreciated, but it could use some additional enhancements to improve overall function: 1) Allow editing of notes on existing list entries. 2) If a new entry raises the 'CNAME' workflow (where additional domains are recommended & added alongside the initial domain), apply any notes from the original entry to the CNAME entries as well. 3) Allow for notes entry from the 'inline' allow/block function on the Domain Query tool.

Add option for the DNS response to be NXDOMAIN instead of the block page IP. This would keep the client device from attempting to load anything for the DNS blocked traffic. Helpful for non-user devices, background traffic on client machine, etc. We have several scenarios where it would be preferable to just have the traffic drop, instead of attempt to load from the block page IP.

It would be great if there was an option to pause each entry in an allow/block list (both universal and policy). A pause/resume button next to each FQDN that's listed would be ideal. Additionally, the FQDNs should default to sorting by name.

After importing multiple .CSV files into the blocklist, should any of the domains in that list change names, it would be nice to have a feature where the list will automatically update rather than having to go back and manually change those items from the list.