Category filter

Web Content Filter configuration profile settings for iOS

Creating web content filter settings for iOS devices can help IT admins manage user access to websites. It helps keep the devices safe from malware, phishing, and other harmful threats as it prevents access to identified malicious websites. Admins may use a custom configuration profile or Web Content Filtering policy to set up web content filtering for iOS devices from Hexnode. This document discusses various Web Content Filter profile settings for iOS devices. The remote deployment of the configuration profile is feasible via Hexnode’s Deploy Custom Configuration feature.


The configuration profile provided below is adapted from a third-party open-source site.


This configuration profile is supported on supervised devices running iOS 7.0 and later.

Configuration profile to set up web content filter

The configuration profile contains a set of keys that can be configured by the admin to set up web content filter on their iOS devices:

  • AutoFilterEnabled: Set the key value as true to enable automatic filtering of web pages. This feature scans every webpage as it loads in an effort to detect and block information inappropriate for young readers. Although the search algorithm is intricate and might change with each version, it essentially looks for language that is appropriate for adults.
  • DenyListURLs: Enter the URLs of all the websites that you intend to block under this key. You must enter each URL as a separate string entry. The maximum number of URL’s should be limited to 500.
  • FilterBrowsers: Set the key value as true to enable the filtering of Webkit traffic. Webkit is a web browser engine used by Safari, Mail, App Store, and many other apps running on iOS and macOS.

What happens at the device end?

Once the policy and custom configuration are associated, the URLs added under DenyListURLs can no longer be accessed, and web pages are filtered for inappropriate content for children.


  • To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager or manually create them using text editors.
  • Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across iOS devices.
  • Ensure that you do not associate conflicting configurations with the devices.
  • Use wildcards to fetch key values from the portal.
  • It is recommended to manually validate the configuration profile execution on a system before executing the action in bulk.
  • Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

  • Configuration Profile Repository