This article explains whether a partial configuration of the IPs and domains required by SMARTFENSE is possible, and what implications it may have. It also details the IPs used by the platform according to their function.
Can a partial configuration be done?
Yes, it is possible to configure only some IPs or domains, but it is not recommended. To ensure the platform works correctly, it is advised to configure all elements listed in the whitelist.
In some cases, organizations choose to configure only some sending IPs or certain domains. This may work depending on the environment, but can cause:
- Email delivery issues
- Missing statistics records
- Inconsistent behavior in simulations
Email sending IPs
The IPs used by the platform for sending emails are:
- 190.210.135.44
- 50.6.200.66
- 52.16.33.192
Additionally, the phishing report button uses:
- 160.153.250.248 (only if this feature is used)
SMARTFENSE instance fixed IPs
When a connection to a SMARTFENSE instance is required —for example, in on-premise configurations with a proprietary mail server for sending notifications, user import via FTP, user synchronization via LDAP, or other integrations requiring a direct connection— the tenant must be configured with a fixed IP.
The fixed IPs for the instance are:
- 54.194.86.204
- 54.194.98.136
To enable fixed IP configuration on your tenant, you must request it from the SMARTFENSE team.
Sending and navigation domains
The domains used by the platform are available at:
Settings > Security > Whitelist
- Whitelist Process in SMARTFENSE
To ensure correct operation, it is recommended to add all domains listed in the whitelist. In case of a partial configuration, at least the domains used in active campaigns must be included.
Considerations
- Partial configuration may cause inconsistent behavior.
- Some features depend on multiple domains and IPs simultaneously.
- Behavior may vary depending on the client's security tools.
💡 Best practices
- Configure the full whitelist whenever possible.
- Avoid partial configurations in production environments.
- Request fixed IP configuration for the tenant before implementing integrations that require a direct connection to the instance.
- Validate operation through test campaigns after any changes to the whitelist.