Required Internet Access
Updated: 6 Feb 2025
Updated: 6 Feb 2025
If you operate in a corporate environment with strict firewalls or proxies, you may need to configure your firewall or proxy to allow Notch Builder to access the internet.
Notch Builder (not Playback) requires periodic internet access to function correctly, especially at installation and license activation.
Notch Playback does not require internet access to run. However, it does require internet access to activate the license.
For more details on running Notch Builder offline see Software Based Licenses
If your proxy/firewall supports wildcard domain whitelisting, you can whitelist the following:
Domain | Ports/Services |
---|---|
notch.auth0.com | HTTPS / 443 |
*.notch.one | HTTPS / 443 |
lc.codemeter.com | HTTPS & HTTP / 443 & 80 |
api.segment.io | HTTPS / 443 |
notch-assets.b-cdn.net | HTTPS / 443 |
cdn.contentful.com | HTTPS / 443 |
If you are unable to whitelist wildcard domains, you can whitelist the following specific domains:
Domain | Ports |
---|---|
notch.auth0.com | HTTPS / 443 |
auth.notch.one | HTTPS / 443 |
c1-auth.notch.one | HTTPS / 443 |
licence-api.notch.one | HTTPS / 443 |
ah-builder.notch.one | HTTPS / 443 |
ar-builder.notch.one | HTTPS / 443 |
manual.notch.one | HTTPS / 443 |
assets-b-cdn.notch.one | HTTPS / 443 |
api.notch.one | HTTPS / 443 |
manage.notch.one | HTTPS / 443 |
lc.codemeter.com | HTTPS & HTTP / 443 & 80 |
api.segment.io | HTTPS / 443 |
notch-assets.b-cdn.net | HTTPS / 443 |
cdn.contentful.com | HTTPS / 443 |
static-builder.notch.one | HTTPS / 443 |