IP Allow Keeper

IP Allow lists for Keeper network communications


If you have deployed a firewall or zero trust network which restricts end-user network traffic to specific services, you can add Keeper to your AllowList based on FQDN. We recommend using FQDN since some of Keeper's services use dynamic IPs.

FQDN Allow List

Outbound TCP port 443 should be open to your users for the following endpoints, depending on your tenant location.

Global - All Customers

  • keepersecurity.com

  • keeper.io

  • gitbook.io (documentation portal)

  • PLUS.. add additional endpoints listed below.

US Hosted Customers

  • keepersecurity.com

  • push.services.keepersecurity.com

  • files.services.keepersecurity.com

  • connect.keepersecurity.com

US / GovCloud Hosted Customers

  • govcloud.keepersecurity.us

  • push.services.keepersecurity.us

  • files.services.keepersecurity.us

  • connect.govcloud.keepersecurity.us

EU Hosted Customers

  • keepersecurity.eu

  • push.services.keepersecurity.eu

  • files.services.keepersecurity.eu

  • connect.keepersecurity.eu

AU Hosted Customers

  • keepersecurity.com.au

  • push.services.keepersecurity.com.au

  • files.services.keepersecurity.com.au

  • connect.keepersecurity.com.au

CA / Canada Hosted Customers

  • keepersecurity.ca

  • push.services.keepersecurity.ca

  • files.services.keepersecurity.ca

  • connect.keepersecurity.ca

JP / Tokyo Hosted Customers

  • keepersecurity.jp

  • push.services.keepersecurity.jp

  • files.services.keepersecurity.jp

  • connect.keepersecurity.jp

Emails from Keeper Security

Keeper sends several types of transactional emails.

  • If the role enforcement policy is enabled, email invitations are sent to newly provisioned end-users via the Admin Console, Bridge or SCIM methods. The content of the email invites can be customized by the Admin in the console configurations screen.

  • Keeper does not send marketing communications or any other product marketing emails to end-users.

  • Users with Administrative rights will receive emails related to account status and billing. End-users will not receive account related emails.

  • The primary account owner who signs up for Keeper will receive an onboarding email and documentation links, as well as direct communication from a Keeper customer success manager.

  • Device verification emails (when logging into a new device) are sent to end-users for authentication purposes.

  • Alerts configured by the Keeper Admin in the Advanced Reporting & Alerts application can be optionally sent to end-users, but this is not activated by default.

Email Delivery

Keeper's email services are hosted with Amazon SES using dedicated IPs. To ensure that emails from Keeper Security are delivered to users with high success, we recommend ensuring that your mail filters accept email from the below FQDNs and IP Senders. Domains:

  • keepersecurity.com

  • keepersecurity.com.au

  • keepersecurity.eu

  • keepersecurity.ca

  • govcloud.keepersecurity.us

  • keepersecurity.jp

Inbound Allow List

For customers who are receiving inbound SIEM events and Automator requests from the Keeper production environment, use the below IP addresses. This only applies to SIEM event reporting and SSO Cloud Automator where Keeper is the originator of the traffic.

See: SIEM and Automator Firewall Configuration

Last updated