Hostnames Used by Files.com

Files.com uses multiple specialized hostnames to deliver secure, high-performance file transfer and collaboration services. Each hostname serves a specific purpose; hostnames for identifying your site, or for providing application access, regional routings and storage access are the most critical. Other hostnames to support file editing, file sharing, and S3-compatible endpoints are optional.

If your organization uses network security controls like firewalls or secure web gateways, you'll need to whitelist certain hostnames to ensure Files.com functions properly. Which domains you need to allow depends on your site configuration and the features you use.

Site Identification Hostnames

Your site's primary hostname is the address your users need in order to connect. Unless a device or connection can only connect using an IP address, we strongly recommend using your hostname when configuring a connection to your site.

Each Files.com site has a unique custom subdomain hostname, which is managed by Files.com. If you configure a custom domain, you're responsible for managing the DNS records for that custom address. Both the subdomain hostname and your custom domain hostname (if you have one) provide an access point for your connections that is branded (for web access) and exists in a primary region to support data sovereignty.

Site Subdomain Hostname

Every Files.com site includes a single custom subdomain, in the format of SUBDOMAIN.files.com , which is the primary hostname for interacting with the platform.

Custom Domain Hostname

Site Administrators can configure a custom domain for use with the Files.com platform. This domain is used instead of the site subdomain for primary access to the site.

Core Application Layer Hostnames

The core application hostnames provide an entry point for connections. The global application hostname app.files.com routes connections through the nearest servers for global acceleration, or through specific regional hostnames if regional routing options are configured.

Global Application Hostname

The hostname app.files.com is used when the address of the site isn't known at the start of the session. Once a session is authenticated and the site is known, further traffic takes place using the more specific custom subdomain or custom domain hostnames.

app.files.com exists to ensure Files.com can safely accept traffic before site identity is known, and then route it correctly once that context is established.

Regional Application Hostnames

Files.com is a large, global cloud platform that operates in multiple geographic regions. Regional routing features for data sovereignty allow your site to restrict traffic to only servers in specific regions.

Regional application hostnames support deterministic routes for regional storage and Remote Server Mounts. Regional application hostnames have the format app-[region].files.com.

These hostnames provide predictable routing when uploads or downloads must be handled by infrastructure in a particular region, either because of your site's settings or because traffic is interacting with a Remote Server Mount.

S3 Storage URLs

The storage layer of the Files.com platform is where files are actually stored and retrieved. Within the storage layer, your files can exist on Remote Servers, private or on-premise servers via the Agent, or within Files.com's native storage.

For Files.com's secure, regional native storage, Amazon S3 is the storage provider. Each region of the Files.com native storage uses fixed storage URLs that do not change over time and are used only by Files.com. Networks that restrict access to online file services must allow access to these storage URLs for transfers to succeed.

For large file transfers, especially multipart uploads and downloads, Files.com provides direct, pre-signed links to this native storage. These pre-signed S3 links improve performance by allowing transfers to flow directly between the user and the storage without routing through the Files.com application layer.

This means that some hostnames that do not end in a files.com domain must be reachable from the user's device in order to transfer large files.

When your organization restricts access to online file-sharing services, it can inadvertently block access to the Files.com storage layer as well. Even if you have already whitelisted the IP addresses and application endpoints needed to access the platform, file transfers will fail until the storage URLs are reachable. These URLs represent the actual storage locations where Files.com stores and retrieves your encrypted files.

Here the list of all the storage URLs for these transfers. The URLs associated with each region are specific to Files.com and are not used by any other service. Files.com manages these URLs and the underlying S3 buckets exclusively, and all connections to these endpoints use encrypted HTTPS. This ensures both predictability for network configuration and complete data security during transit.

• https://s3.amazonaws.com/objects.brickftp.com/
• https://s3-ca-central-1.amazonaws.com/objects-ca-central-1-brickftp-com/
• https://s3-ap-southeast-2.amazonaws.com/objects-ap-southeast-2-brickftp-com/
• https://s3-eu-central-1.amazonaws.com/objects-eu-central-1-brickftp-com/
• https://s3-eu-west-2.amazonaws.com/objects-eu-west-2-brickftp-com/
• https://s3-ap-northeast-1.amazonaws.com/objects-ap-northeast-1-brickftp-com/
• https://s3-ap-southeast-1.amazonaws.com/objects-ap-southeast-1-brickftp-com/

Hostnames That Support Specific Features

In addition to the hostnames used for identifying your site, accessing the application layer of the platform, and acessing the native Files.com storage layer, some hostnames are required to make use of specific features. This includes the Files.com Online Editor,

Hostnames Used for Online Editors

Files.com provides integrated online co-authoring for standard business format files. This includes an integration with Microsoft Office for Web and with the Files.com Editor.

All editor-related traffic is served from dedicated hostnames, regardless of your regional routing features. The editor subsystems communicate with the necessary storage URLs for transferring files to and from the editor systems

Editor-originated traffic has no access to authenticated Files.com sessions or any core Files.com services, and access for an editor session is limited to the file being edited.

The following hostnames must be reachable for your users to use the co-authoring feature, regardless of the type of online editor integration your site uses:

• wopi1.files.com
• wopi2.fles.com

If you have enabled the Files.com Editor, you must also allow access to

• editor1.files.com
• editor2.files.com

If your site is using Microsoft Office for Web as its online editor, Microsoft publishes a list of URLs that you'll need to access.

Public Hosting Hostnames

The Web Public hosting feature uses a separate domain from your custom subdomain or custom domain as a security measure. This separation provides multiple benefits: it prevents excessive download traffic of a publicly hosted folder from impacting the performance of your Files.com site, and it ensures ensures that a malicious file uploaded to a publicly hosted folder cannot interact with authenticated user sessions.

The hostname format for public hosting is: SUBDOMAIN.hosted-by-files.com , where SUBDOMAIN matches your site's custom subdomain.

Embedding Code Hostname

The jssdk.files.com domain is used with Embedded Share Links and Embedded Inboxes.

This domain is a deliberate security boundary for Files.com’s embedded, browser-executed functionality. The code that powers embeddedd Share Links and Inboxes must be accessible for a site from arbitrary locations that Files.com does not control.

By serving embedded JavaScript from a dedicated domain, we prevent embedded code from sharing origin privileges with authenticated Files.com application domains.

Inbound Email to Inbox Hostname

The domain inbox.files.com receives inbound emails for Inboxes. This domain does not need to be directly reachable from a user's device, but they must be able to send mail to the domain in order to upload files to an inbox through email.

S3-Compatible Endpoint Hostnames

The S3-Compatible Endpoint feature allows any S3 client or SDK to connect directly to Files.com and perform uploads, downloads, and object management operations.

The S3 API protocol expects to communicate with a service at the root of the domain, so Files.com uses the hostname s3.files.com for this type of connection. When you have enabled Dedicated IP addresses for your site, your S3-Compatible endpoint hostname is s3-SUBDOMAIN.files.com (replace the SUBDOMAIN with your custom subdomain name).

Other Optional Hostnames

There are a few other hostnames that provide helpful information but do not prevent any feature functionality or file transfers if they are not accessible.

The Files.com documentation about its features is publicly accessible at the www.files.com domain.

Technical information about all of Files.com's supported SDKs, the CLI, Zapier, Terraform, and all of the iPaaS connectors is located at developers.files.com

Information about the status of Files.com's platform and services is located at status.files.com

Comprehensive List of Domains To Whitelist

To fully enable Files.com in a firewall or secure web gateway operating in a default-deny configuration, allow outbound access to the following domains based on the features you use.

Always provide access to the following hostnames:

• Site identification hostnames - your custom subdomain, and your custom domain (if used)
• Application access hostnames - always include app.files.com. Include regional application hostnames for any needed regions (global acceleration will use all available regions)
• S3 storage URLs - enable access to all of the storage regions used for your Files.com native storage

Enable other hostnames as needed to support other features

• Hostnames for online editors - only if co-authoring is enabled for your site
• Public hosting hostnames - only if you are using the public hosting feature
• Sharing embed code hostname - only if users can embed share links or inboxes
• S3-Compatible endpoint hostname - only if using an S3 CLI or API to manage Files.com storage