Most of our customers select a Custom URL that uses the following naming conventions:

This enables the Trust Center's URL in the browser to have their company name in it, vs app.safebase.io that you see in Preview Mode.

Please see SafeBase's Custom URL for an example.

Note: Selecting a format such as security.securitycompany.com works best, as this is natively supported by our reverse proxy. It may be possible to setup something such as example.com/security, however configuration will be required on your infrastructure team's end, and we may not be able to fully troubleshoot.

Please contact us with your desired custom URL as we are now rolling out Cloudflare Custom Hostnames providing additional WAF and anti-DDoS coverage at no extra charge.

We will be sharing 1 DNS CNAME record and 2 DNS TXT records that your team will add for this process to be completed.

To begin, add a CNAME record for the desired URL (e.g., security.example.com) with the target pointing to: proxy-ssl.safebase.io

Example:

If you use Cloudflare, Fastly, Route53, or similar services, you must add an additional DNS-only (no proxification) CNAME record with the following details:

Note: Replace the site in bold with your company's new Custom URL

Host: _acme-challenge.security.example.com

Points to: security.example.com.2r10.flydns.net

Our reverse proxy uses Let’s Encrypt to generate certificates for custom URLs that are used for Trust Centers and follow the format of example.company.com. If your domain has existing CAA records, you will need to add an entry for Let’s Encrypt: 0 issue "letsencrypt.org"

More details can be found here: https://letsencrypt.org/docs/caa/