Web Filtering
Block malicious and non-work-related sites, and control access by category, site, or time window.
About
About Web Filtering
A network-level control for what employees can reach in the browser. Web filtering manages user access to enterprise-approved websites based on pre-determined security policies. It can enforce internet usage policies, block malicious sites, or restrict non-work-related content, and is typically implemented at the network level to improve productivity and security.
What it does
Benefits
Benefits of Web Filtering
A single control point for security, compliance, and productivity.
What it protects against
Web filtering protects networks from threats, helps ensure compliance with regulations like HIPAA and GDPR, improves employee focus by blocking non-work-related sites during work hours, optimizes network performance, mitigates legal risks, and safeguards sensitive data by blocking unauthorized file-sharing sites.
Endpoint Central MSP's web filter helps prevent malware, improves productivity, and ensures security — letting IT admins control downloads, set browsing times, block harmful sites, manage policies centrally, and protect remote workers.
Configuration
Implementing Web Filtering
Turn on the built-in threat protections, then layer time- and category-based access rules on top.
Create a policy and enable threat protections
- Go to Browsers → Policies → Web Filter.
- Click Create Policy and name the policy.
- Enable Block Malicious Websites to block access to malware sites.
- Enable SSL certificate protection to ensure SSL certificate encryption.
- Enable Restrict over-riding SSL certificate errors to stop users from ignoring or bypassing invalid/untrusted SSL certificate warnings.
- Enable Block other apps that inject code when that protection is required.
- Enable Block websites with excessive ads to prevent access to sites with an excessive amount of advertising.

Enabling the core web filter protections. - Configure the URL filter settings to allow or block access.

Configuring URL Filter access rules. - Customize the block page as needed.

Customizing the block page. - Click Save & Publish to save the policy.
- Deploy the policy with the computers or groups where web-application access should be restricted.
The web filter policy isn't supported in Incognito mode or Guest mode. Incognito mode can be disabled under Policies → Browser Customization → Security Restriction → Disable Incognito Policy, and Guest mode under Policies → Browser Customization → User Account Settings → Allow users to use guest mode.
Filtering by category, site, and time window
URL Filter controls website access based on specific time intervals. Allow or block access using AI-classified categories — Education, News, Entertainment, and so on — or by specifying individual websites or website groups. Refer the domain match criteria for URL filtering. Access time windows are specified in HH:MM:SS format.
If Artificial Intelligence is available in your category list, select it to include that category in the web-filter policy. Category-based website access and controls over data entered into an AI service are separate settings. Review Generative AI DLP when configuring data-entry restrictions.
Override Category Restriction lets a blocked domain within a category be overridden; every such request is recorded under Web Activity in the Insights tab. While configuring website groups, specific sites can also be excluded from filtering with Define exclusion list for URL filter. The Override Category Restriction is off by default in a new Web Filter policy. Turn it on when the policy must offer the category-review request workflow. Review this value when editing an existing policy; an existing policy can have a different saved choice.
The Web Category feature is currently in closed beta — reach out to msp-endpointcentral-support@manageengine.com for access. See web category based filtering for more.

A web filter rule does not distinguish personal and corporate accounts that use the same address. For supported Google Workspace account-domain restrictions, see Define accounts to access enterprise Google apps. This does not establish managed-device-only access or equivalent Outlook/Yahoo support.
If sign-in or a cloud application redirects to another host, record both original and redirected URLs. Review the applicable rules for each request. A rule for one hostname does not document all sign-in/resource dependencies. Limit changes to required domains and test the complete flow.
Customizing the block page and deploying
The message and logo shown on blocked pages can be customized, or the page can redirect elsewhere entirely. Allow users to contact admin from a blocked page lets end users send mail to the administrator directly from that page.

A Web Filter block page can show Website Blocked or another organization-defined message. Its wording depends on category filtering, category-override settings and block-page customization. The standard non-category message uses: Website Blocked! The [domain] is blocked in your organization. Contact your system administrator for further information
.
Record the complete message and blocked URL. Compare the affected browser, current policy and block-page customization. A saved or successfully deployed policy does not establish that every website must be accessible. Follow the enforcement checks on this page and review policy conflict precedence.
Verify Web Filter enforcement
Execution Status summarizes deployment results. Yet to update computers compares associated collections with the latest published collection. It does not have to equal Failed or Yet To Apply totals. See policy version and status guidance.
Web Filter requires the Browser Security extension on the managed browser. Verify it is installed and enabled in the profile used for testing. Check the policy/version, target and deployment exclusions.
For Website Blocked or Access Restricted after a change, record the complete requested and redirected URLs, time and browser profile. Review other Web Filter policies and policy-conflict guidance. Deployment success alone does not establish which rule matched.
If a blocked site remains accessible, compare the same URL/session on the affected browser, including private/guest mode, extension state and reported version. Collect these details for support if the result remains inconsistent.