On this page

For school IT

Network Requirements

NotAI runs in your students' browsers and needs to reach two hosts. If your district filters the web on student devices, allow these hosts so NotAI can load and report. This page lists them, explains why a filter may block them, and shows how to allow them in common school filters.

Overview

When you install NotAI in Canvas, a small script loads on each Canvas page from cdn.isnotai.com, then sends what it observes to chl.isnot.ai. Both connections start in the student's browser, so any web filter on the device or the network sees them.

If a filter blocks either host, Canvas keeps working normally. The browser silently refuses the blocked request, the student sees nothing, and no block page appears. Your NotAI dashboard simply shows no sessions for the students behind that filter.

Hosts to allow

Host Used for Protocol
cdn.isnotai.com Loads the NotAI script (/api.js) and the parts it loads on demand HTTPS, port 443
chl.isnot.ai Receives what the script reports (accounts that store data in the United States) HTTPS and secure WebSocket (WSS), port 443
chl-eu.isnot.ai The same, for accounts that store data in the European Union HTTPS and secure WebSocket (WSS), port 443

For teachers and administrators

Students need only the hosts above. Staff who review work in the NotAI panel inside Canvas, or in the NotAI dashboard, also need these:

Host Used for Protocol
sso.isnotai.com Staff sign-in for the review panel and the dashboard HTTPS, port 443
api.isnot.ai Reading results in the review panel and the dashboard HTTPS, port 443
dash.isnotai.com The NotAI dashboard HTTPS, port 443

The simplest rule is to allow the two domains isnotai.com and isnot.ai, including their subdomains. That covers every host on this page.

Custom data domain: if your NotAI agreement includes a custom data domain (a subdomain of your own domain that points to NotAI), students' reports go there instead of chl.isnot.ai. Allow that host too.

Why a filter may block NotAI

School web filters sort websites into categories and block some categories for students. Many districts block categories for AI tools or for sites the filter has not categorized yet.

NotAI is academic-integrity software. It helps teachers and administrators find coursework that was completed with AI tools or automation, and it gives students no AI features. Some filters, including Lightspeed, have placed NotAI's hosts in an AI category. When that category is blocked for students, the filter also blocks NotAI, the tool your district uses to enforce that same policy.

An allow entry for the hosts above fixes this for your district right away. You can also ask your filter vendor to recategorize them (see below).

Lightspeed Filter

In the Lightspeed Filter admin console:

  1. Allow the domains. Go to Internet Access > Custom Allow List for the group or OU your students are in, and add isnotai.com and isnot.ai. Enter the domain only, without https:// and without a trailing slash. An entry on the Custom Allow List overrides the category.
  2. Check the category. Go to Internet Access > Default Rules, enter cdn.isnotai.com in the search bar and select Check. You can change the category for your district from the result.
  3. Request a recategorization. Lightspeed accepts categorization requests from administrators through the Filter Admin Portal (Access Checker). Suggested wording is below.

Menu names can differ between Lightspeed versions. Your Lightspeed account team can point you to the current location.

Other web filters

GoGuardian, Securly, iboss, Linewize, ContentKeeper (Ativion) and similar filters all support an allow list. In each:

  • Add isnotai.com and isnot.ai to the allow list that applies to student users and devices.
  • Make sure the entry covers subdomains (some filters need *.isnotai.com written out).
  • If your policy blocks an AI or uncategorized category, confirm that a domain allow entry takes precedence over the category block in your filter's rule order.
  • Apply the change to every policy your students fall under, including off-network and at-home policies on managed Chromebooks.

HTTPS inspection and proxies

If your filter or firewall decrypts HTTPS traffic (HTTPS or SSL inspection), exclude the NotAI hosts from inspection. NotAI prefers a secure WebSocket connection, which some inspecting proxies interrupt. When the WebSocket fails, NotAI falls back to ordinary HTTPS requests, so data still arrives, but a clean WebSocket path is more reliable.

Verify from a student device

Blocked requests are silent inside Canvas, so test the hosts directly. On a device signed in with a student account and your student filter policy:

  1. Open https://cdn.isnotai.com/api.js. You should see JavaScript text. A block page means cdn.isnotai.com is still blocked; the block page usually names the category.
  2. Open https://chl.isnot.ai/health (or https://chl-eu.isnot.ai/health for EU accounts). You should see a short status line that includes "healthy".
  3. Open a Canvas course page as that student, then check your NotAI dashboard for a new session.

The device check runs the host and browser checks in one page on that device and writes a report you can send to your IT team or to us.

Asking your vendor to recategorize

Filter vendors usually accept recategorization requests from their customers' administrators. Suggested wording:

Please recategorize cdn.isnotai.com, chl.isnot.ai, isnotai.com and isnot.ai as Education or Educational Technology. These hosts belong to NotAI, the academic-integrity software our district uses in Canvas to identify coursework completed with AI tools or automation. It is not an AI tool and offers students no AI features. Under an AI category, our policy that blocks AI tools for students also blocks the software we use to enforce it.

Still blocked after allowing the hosts? Support usually replies within a business day.

Contact support

Installing NotAI in Canvas?

Follow the Canvas install guide, then allow the hosts above so students on filtered devices are covered.