NT-ware and Online Services DNS / IP addresses
- Jason Apel
The following information is provided to support organizations that have specific restrictions and controls in place within their IT infrastructure.
All communication between uniFLOW Online and company network components is sent encrypted via HTTPS (port 443 outbound). However, if you have restricted access out of your network, general access to the URLs and IP addresses below must be granted to reach uniFLOW Online.
uniFLOW Online email servers are used for various functionality like ‘Scan to Email’, user notifications, user registration etc. Email communication may also be blocked or subject to your company email filtering rules and policies. To ensure email traffic is not blocked we have listed our global uniFLOW Online email servers below which should be added to an ‘Allow List’.
Global hosted services
NT-ware global web services are required to provide uniFLOW Online installations, help material and resources. Please ensure you allow these sites if you are restricting traffic from and or to your organization. ALL IP and URL exclusions are required if restrictions are in place. These provide local and regional resilience and redundancy.
uniFLOW Online resources.
IP address
5.9.111.67, 78.46.35.44, 135.181.0.40, 147.135.37.12, 147.135.1.50
Region specific URLs
EUROPE | DNS | IP |
Deployment | <tenant>.eu.uniflowonline.com | 40.113.96.203 |
Tenant creation / device registration via device UI 2 | 40.113.96.203 | |
NTWOIS service 3 | 13.73.143.121, 20.123.128.99, 74.234.111.228, 68.219.118.151 | |
Azure IoT Hub 4 7 | - | |
Device Access Extension5 |
| |
Send diagnostics trace log button function. | - | |
uniFLOW SmartClient and MEAP device check for manual trigger of Emergency Mode 6 | - |
UK | DNS | IP |
Deployment | <tenant>.uk.uniflowonline.com | 51.132.34.151 |
Tenant creation / device registration via device UI 2 | 51.132.34.151 | |
NTWOIS service 3 | 52.151.72.165, 20.117.73.188, 51.142.165.157, 51.142.148.43 | |
Azure IoT Hub 4 7 | - | |
Device Access Extension 5 |
| |
Send diagnostics trace log button function. | - | |
uniFLOW SmartClient and MEAP device check for manual trigger of Emergency Mode 6 | - |
JAPAN | DNS | IP |
Deployment | <tenant>.jp.uniflowonline.com | 13.71.129.59 |
Tenant creation / device registration via device UI 2 | 13.71.129.59 | |
NTWOIS service3 | 13.78.27.73, 20.222.233.159, 20.89.248.222, 20.89.252.104 | |
Azure IoT Hub 4 7 | - | |
Device Access Extension 5 |
| |
Send diagnostics trace log button function. | - | |
uniFLOW SmartClient and MEAP device check for manual trigger of Emergency Mode 6 | -
|
AUSTRALIA | DNS | IP |
Deployment | <tenant>.au.uniflowonline.com | 13.70.152.165 |
Tenant creation / device registration via device UI 2 | 13.70.152.165 | |
NTWOIS service 3 | 23.101.239.160, 20.211.250.80, 20.5.79.157, 4.196.169.251 | |
Azure IoT Hub 4 7 | - | |
Device Access Extension 5 | autunnelingserveruniflow.australiasoutheast.azurecontainer.io |
|
Send diagnostics trace log button function. | - | |
uniFLOW SmartClient and MEAP device check for manual trigger of Emergency Mode 6 | - |
SINGAPORE | DNS | IP |
Deployment | <tenant>.sg.uniflowonline.com | 52.187.22.132 |
Tenant creation / device registration via device UI 2 | 52.187.22.132 | |
NTWOIS service 3 | 52.163.85.154, 20.205.191.8, 20.239.83.198, 20.239.86.61 | |
Azure IoT Hub 4 7 | - | |
Device Access Extension 5 |
| |
Send diagnostics trace log button function. | - | |
uniFLOW SmartClient and MEAP device check for manual trigger of Emergency Mode 6 | - |
USA | DNS | IP |
Deployment | <tenant>.us.uniflowonline.com | 137.117.90.136 |
Tenant creation / device registration via device UI 2 | 137.117.90.136 | |
NTWOIS service 3 | 137.116.127.38, 20.25.54.169, 20.253.243.215, 20.253.187.40 | |
Azure IoT Hub 4 7 | - | |
Device Access Extension 5 |
| |
Send diagnostics trace log button function. | - | |
uniFLOW SmartClient and MEAP device check for manual trigger of Emergency Mode 6 | - |
CANADA | DNS | IP |
Deployment | <tenant>.ca.uniflowonline.com | 4.204.58.190 |
Tenant creation / device registration via device UI 2 | 4.204.58.190 | |
NTWOIS service 3 | 4.204.61.228 | |
Azure IoT Hub 4 7 | - | |
Device Access Extension 5 |
| |
Send diagnostics trace log button function. | - | |
uniFLOW SmartClient and MEAP device check for manual trigger of Emergency Mode 6 | - |
uniFLOW Online Global Services
Deployment Status Integration 8 | Dynamic IP, Microsoft managed. |
uniFLOW Online email servers
Europe | 94.130.72.34, 94.130.97.143, 50.85.219.80, 20.67.245.213 |
|---|---|
Australia | 52.255.51.184, 139.99.200.184, 20.211.75.3 |
USA | 40.114.54.68, 5.161.118.71, 13.91.89.76 |
Japan | 13.73.5.41, 40.74.132.151 |
Singapore | 52.187.66.27, 15.235.163.86, 20.2.248.27 |
United Kingdom | 51.140.48.125, 51.195.253.209, 20.254.190.46 |
Canada | 4.206.153.83, 192.99.43.159, 4.248.33.5 |
If you have configured uniFLOW Online to use your own email provider, it is not necessary to add these IP addresses.
[1] Due to some legacy device support the download for MEAP applets takes place via HTTP at present.
[2] For creating tenants and onboarding devices via the Canon imageRUNNER ADVANCE device user interface. It will also need to resolve and access ‘device02.c-cdsknn.net', ‘a02.c-cdsknn.net', and ‘device.c-cdsknn.net'. The listed cdsknn.net URL’s will resolve to a ‘CloudFront’ Content Delivery Service hosted on AWS. This will also need to be explicitly listed if you are filtering these URL’s, Locations and IP address ranges of CloudFront edge servers - Amazon CloudFront .
[3] NT-ware OAuth Identification Service.
[4] IoT Hub is a managed service, hosted in the cloud, which acts as a central message hub for bi-directional communication between the uniFLOW SmartClient and the devices it manages. IOT Hub has a temporary "static" address, which is subject to change over time, so there is no IP address that can be documented here. Microsoft suggests following best practices, described in this article Understanding the IP address of your IoT hub .
[5] Enabling the 'Device Access' extension provides device access in a zero-trust environment. The listed URL is a required endpoint for the secure tunnel to be established between uniFLOW Online and the connected device.
[6] This URL is required for the uniFLOW SmartClient and MEAP devices to perform a check on Microsoft Azure functionality if a tenant or deployment is manually forced into Emergency Mode. Note that the URL has a temporary "static" IP address, which is subject to change over time so that no IP address can be documented. Microsoft suggests following the best practices described in this article.
[7] The uniFLOW SmartClient utilizes IoT standard protocols like MQTT (either native or via WebSocket) for real-time communication with uniFLOW Online. If MQTT (Native) is utilised, port 8883 will need to be allowed, this is the preferred method. Should opening this port be unavailable, MQTT (via WebSocket) is used as a fall back on port 443. When SSL inspection is configured within the proxy/firewall application MQTT (via WebSocket) must be supported. In case this is not supported, the Azure IoT Hub must be bypassed for SSL inspection.
[8] Display of current uniFLOW Online deployment status to end-users on Canon MEAP enabled devices based on https://status.uniflowonline.com.
Update History:
Date | Change |
|---|---|
Jan 6, 2025 |
|
Nov 29, 2024 |
|
Nov 22, 2024 |
|
Oct 8, 2024 |
|
Nov 19, 2024 |
|
Related pages
