{"version":"2.1.113","anchor":"network-denied-domains-configuration","canonical_anchor":"network-denied-domains-configuration","heading":"Network Denied Domains Configuration","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.113\/e\/network-denied-domains-configuration","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.113","markdown":"### Network Denied Domains Configuration\n\n**What**\n\nExpanded network security with a new `deniedDomains` field that blocks specific domains even if they match `allowedDomains` rules.\n\n**Details**\n\n- Accepts an array of domain strings with wildcard support (same syntax as `allowedDomains`)\n- Merged from all settings sources regardless of `allowManagedDomainsOnly` \u2014 meaning organization policies can always enforce domain blocking\n- Takes priority over `allowedDomains`: a domain matched by both lists is blocked\n- Logs denials with the specific domain and port for debugging\n\n**Evidence**\n\nSchema definition (search for `\"Domains that are always blocked, even if matched by allowedDomains\"`)"}