Skip to main content

Addresses and Certificates

IP Addresses

In this page you will find the list of IP addresses used by Plate Recognizer and ParkPow. This is important to know if you need to whitelist our servers in your firewall for incoming and outgoing connections. You can trust our servers and avoid any security issues.

warning

Please check this page for the most up-to-date list of IP addresses, as we might change them from time to time, depending on usage, maintenance, etc.

On-premise products

All on-premise products use the same server for license validation, on ports 80 and 443:

IPv4IPv6Domain
69.164.223.1382600:3c03:1::45a4:df8aapi.platerecognizer.com
172.104.25.230app.platerecognizer.com

Products covered: Snapshot SDK, Stream, ParkPow, Blur, Shipping Containers (images and live), USDOT OCR.

tip

If your firewall also blocks public DNS resolvers, include this option to your run command: --add-host api.platerecognizer.com:69.164.223.138

Cloud Instances of our Products

The following IP addresses are used by our cloud instances when they need to connect to customers' resources by means of webhooks, SSH tunnels, RTSP consumption, among other interactions and protocols.

If you are using any of our cloud services, you may need to whitelist the following IP addresses in your firewall, according to the ones you are consuming:

ProductIPv4IPv6DomainNote
Stream Cloud45.79.145.137, 45.79.183.116, 198.74.59.128
ParkPow Cloud45.79.136.82app.parkpow.com
Blur198.74.59.128blur.platerecognizer.com
Snapshot Cloud69.164.223.1382600:3c03:1::45a4:df8aapi.platerecognizer.com
TrailerID69.164.223.1382600:3c03:1::45a4:df8aapi.platerecognizer.com
VisionAlert69.164.223.1382600:3c03:1::45a4:df8aapi.platerecognizer.com
VIN ID69.164.223.1382600:3c03:1::45a4:df8aapi.platerecognizer.com
Shipping Containers image66.228.39.177container-api.parkpow.com
USDOT OCR66.228.39.177usdot.parkpow.com

Snapshot/ParkPow Cloud Images

Images uploaded to our services are hosted on *.linodeobjects.com. Fox example, us-east-1.linodeobjects.com (IP: 173.255.231.96).

Custom Root Certificates

If your company inspects TLS connections in the corporate network, you need to add your company CA certificate to the docker container's root CA certificates by including these options in the run command:

docker run ... \
-v <company-preconfigured-CA-certs>:/etc/ssl/certs/ca-certificates.crt \
-e REQUESTS_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt \
platerecognizer/<image>[:<tag>]

Replace <company-preconfigured-CA-certs> with the path to your CA certificate file. Common locations by OS:

OS / DistributionCA Certificate Path
Debian / Ubuntu / Gentoo/etc/ssl/certs/ca-certificates.crt
Fedora / RHEL 6/etc/pki/tls/certs/ca-bundle.crt
OpenSUSE/etc/ssl/ca-bundle.pem
OpenELEC/etc/pki/tls/cacert.pem
CentOS / RHEL 7 & 8/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem

Docker Registry

For downloading and updating Docker images. These are Docker images (virtual machine templates) and not snapshots (jpg files).

IP Addresses

The Base URL is https://registry-1.docker.io/ There isn’t a published list of IPs that the official registry uses. They aren’t guaranteed to stay the same and aren’t guaranteed, unfortunately.