This article provides assistance to allow traffic from Lucid through your firewall, so your users can properly use Lucid. By filtering traffic by domain in your allow list, which is also known as whitelisting, you can ensure that emails from Lucid properly reach the users on your account.

We strongly recommend filtering by domain, as our AWS IP ranges change over time.

If you are in the FedRAMP environment, refer to our FedRAMP overview article for details on preparing your network for Lucid users.

Filter by domain

When setting up to filter by domain, you need to allow the following wildcard domains through your firewalls or other filters:

https://*.lucid.app
https://*.lucidextensions.app
https://*.lucidchart.com

Then, filter for the following domains:

https://lucid.app
https://lucidextensions.app
https://api.lucid.co
https://community.lucid.co
https://developer.lucid.co
https://help.lucid.co
https://training.lucid.co
https://lucidchart.com
https://lucidspark.com
https://lucidscale.com
https://lucidforeducation.com
https://lucid.co
https://lucid.readme.io

Basics of wildcard domains

The wildcard allows any requests from the domain or its subdomains to bypass certain security filtering layers. For example, adding https://*.lucid.app when filtering by domain will allow access to https://admin.lucid.app and https://users.lucid.app.

A wildcard domain uses an asterisk (“*”) as the leftmost domain name system (DNS) label following the hypertext transfer protocol secure (“https://”), which is a secure version of the HTTP protocol. The "s" indicates that the communication between a website and a web browser is encrypted and secure.

Give feedback on this article

Have feedback about this article? Tell us about your experience here.

Related articles