Networking requirements for PitneyShip Pro and PitneyTrack Inbound

The following URLs and IP addresses must be accessible in order for PitneyShip Pro and PitneyTrack Inbound to connect to the internet.
Products affected: SendPro® Online powered by PitneyShip® Pro and PitneyTrack® Inbound

Use these network requirements to prepare your IT and local network environment for connecting PitneyShip Pro and PitneyTrack Inbound to the internet.

If you have extensive network security restrictions, your IT or network administrator may need these specifications to prepare for the installation.

URL Information

The URL hostnames must be accessible from the device, without any obstructions. This includes being free of any SSL packet inspection, web filtering devices or software monitoring. Unless indicated otherwise, these URLs apply to PitneyShip Pro and PitneyTrack Inbound.

  • PitneyShip Pro and PitneyTrack Inbound have certain URLs it must connect to for its basic operation. These are listed under “Required URLs”.

Required URLs

  • SendPro360 – Applies to all inbound requests to Commercial
    • sendpro360.pitneybowes.com
    • shipping360.pitneybowes.com
    • admin.sendpro360.pitneybowes.com
    • enrichtoken.sendpro360.pitneybowes.com
    • api.sendpro360.pitneybowes.com
  • IOT Core with PB Static IP – Applies to all inbound requests to DeviceHub
    • devicehub.pitneybowes.com
  • SendPro360 SFTP – Applies to all inbound requests to SFTP
    • sftp.sendpro360.pitneybowes.com
  • AirWatch – Tracking Assistant device - For PitneyTrack Inbound Tracking Assistant Application 
    • cn700.awmdm.com
  • Xamarin – Cloud - For PitneyTrack Inbound Tracking Assistant Application 
    • xaapi.xamarin.com
  • Time synchronization servers – Cloud - For PitneyTrack Inbound Tracking Assistant Application 
    • time.nist.gov
  • SendPro360 Commercial/Global Outbound traffic – OPTIONAL. Use-case driven.  Applies to all outbound traffic to the internet originating from PitneyShip.
  • ParcelPoint Smart Lockers – ParcelPoint Smart Lockers
    • pitneybowes.com
    • okta.com
    • eloview.com
    • teamviewer.com
    • ssm.*.amazonaws.com
    • smmessages.*.amazonaws.com
    • ec2messages.*.amazonaws.com
    • s3.*.amazonaws.com/
    • us-east-1.amazonaws.com
    • sending.us.pitneybowes.com
    • us-west-1.amazonaws.com
    • sendpro.pitneybowes.com
    • api.pitneybowes.com
    • api.sendpro360.pitneybowes.com
    • www.google.com
    • get.teamviewer.com
    • manage.eloview.com
    • content.eloview.com
    • google.com/generate_204
    • debian.pool.ntp.org
    • 0.debian.pool.ntp.org
    • 1.debian.pool.ntp.org
    • 2.debian.pool.ntp.org
    • pitneybowes.com
    • okta.com
    • logmein.com

Communication requirements

The PitneyShip Pro and PitneyTrack Inbound connection uses these ports and protocols. The system will require access through your network and firewall therefore the ports 22 and 443 should be open.

Ports

Port 22

  • SendPro360 SFTP

Port 443

  • SendPro360
  • IOT Core with PB Static IP
  • AirWatch
  • Xamarin
  • Time synchronization servers

Port 80 (TCP/UDP)

  • google.com/generate_204

Port 123

  • NTP servers for sync to the clock

Port 8883 (TCP)

  • AWS IoT MQTT for diagnostics

Port 53

  • DNS lookup

Port 5938 (TCP / UDP)

  • TeamViewer

IP Addresses

  • 52.205.16.237
  • 18.210.150.37

Email addresses

The following email addresses must be allowed so that users and recipients will receive email notifications from the system.

User Welcome messages / invitations

User password resets and package notifications

UPDATED: 14 November 2024