How to authorize Arsen's phishing simulations on your email servers?

Before you can start testing your employees, you need to configure your mail servers to deliver our simulations to the inbox and not to spam or marked as junk mail.

If you don't follow this procedure, our simulations may end up in spam, and you won't be able to properly educate your entire workforce.

Summary:

Which authorization procedure to follow?
Authorization procedure by IP address
Authorization procedure by email header (email headers))
IP addresses and headers to authorize

Which authorization procedure to follow?

The procedure varies depending on your environment.

If you're not using a phishing or spam filtering system in addition to your email service, we recommend authorizing our platform by allowing its IP address.

If you're using a phishing or spam filtering system upstream from your mail servers, we recommend authorizing our platform by using email headers. You will also need to authorize our IP address directly on your phishing or spam filtering system.

Authorization procedure by IP address

How to authorize Arsen simulations by IP address on Google Workspace/Google Apps?
How to authorize Arsen simulations by IP address on Microsoft Office 365?

Authorization procedure by email header (email headers)

How to authorize Arsen phishing simulations using headers on Google Workspace/Google Apps?
How to authorize Arsen phishing simulations using headers on Microsoft Office 365?
How to authorize Arsen phishing simulations using headers on Exchange 2010?

IP addresses and headers to authorize

Depending on the authorization procedure followed (see above section), you may need the following information:
IP address : 161.38.204.14
Default header : X-Arsen-Training

We encourage you to customize the header if you implement an authorization procedure by header.

Updated on: 03/03/2023