Frequently Asked Questions

Please ensure you have downloaded any expected files by EOD Friday, July 17, 2026 from your mailbox IDs to prevent any potential lost access to this data on the migrated platform.

A Fully Qualified Domain Name (FQDN) is the complete domain path used to connect to our server (oft.firsthorizon.com); you will need to update your SFTP client configuration to use the FQDN instead of a static IP address. If you are already specifying the FQDN of oft.firsthorizon.com, no change is required for this.

You may need to accept our new server host key upon your first logon to the new platform, depending on your configuration.

Unfortunately, no. Connections made directly to a static IP address may fail after migration. FQDNs allow us to manage security certificates, routing, and updates without requiring further action from you in the future.

The new platform supports modern, secure protocols including, but not limited to:

• SFTP: SSH with strong key exchange and MAC algorithms (e.g., AES-256, SHA-2)

If your firewall rules are based on IP addresses, they may need to be updated to accommodate new IPs behind the domain name; please ensure outbound connections to the FQDN are allowed. Please ensure the following ranges are whitelisted on your firewall, if necessary, as these will allow access to both our non-Production and Production environments: 199.46.40.0/32; 199.46.40.1/32; 20.96.167.48/28; 20.7.87.160/28

Yes, any scripts using hardcoded IP addresses should be updated to use the FQDN. In addition, confirm that your automation tools support modern ciphers.

Yes, all existing public SSH keys we have on the current platform will migrate. However, if there are changes in authentication methods or key policies, we will notify you in advance.

Older ciphers are no longer considered secure and may be vulnerable to cryptographic attacks. This update aligns with modern compliance frameworks like NIST, HIPAA, and PCI-DSS.

Yes, the new platform is designed to meet or exceed common regulatory standards, including encryption requirements and auditability.

We are working to minimize and/or entirely eliminate any service interruption. A specific maintenance window (if needed) will be communicated in advance; however, it would only occur during non-business hours.

Login credentials will remain the same. If there are any changes required in relation to credentials, you will be contacted directly..