Before launching simulated phishing campaigns on your employees, you need to whitelist ThreatCop’s IP's to make sure these emails reach the employees’ inboxes successfully. It's necessary to whitelist these IPs to prevent these simulated phishing emails from getting blocked or landed in the spam folder.

1. India:
   
1. 13.234.117.252 (Threatcop portal)
2. 13.127.7.201 (Awareness)
3. 202.22.164.131 ,  16.113.17.40  (SMTP IP)
   
2. KSA:
1. 34.166.57.137 (Threatcop portal)
2. 13.127.7.201 (Awareness)
3.  202.22.164.131 ,  16.113.17.40 (SMTP IP)
3. UAE:
1. 3.29.34.108 (Threatcop portal)
2. 13.127.7.201 (Awareness)
3. 202.22.164.131 ,  16.113.17.40 (SMTP IP)
   
4. Indonesia:
   
1. 43.218.47.156 (Threatcop portal)
   
2. 13.127.7.201 (Awareness)
3. 202.22.164.131 ,  16.113.17.40 (SMTP IP)
   
5. USA: 
   
1. 54.158.228.224 (Threatcop portal)
   
2. 13.127.7.201 (Awareness)
1. 202.22.164.131 ,  16.113.17.40 (SMTP IP)
6. OMAN
1. 185.64.25.225 (Threatcop portal), (Landing and Awareness URL)
2. 202.22.164.131 ,  16.113.17.40 (SMTP IP)

Once you have whitelisted these IPs in your environment, it is advisable to run a quick test campaign before launching the campaign on your employees. This will help you check that the emails are landing properly in the inbox and that everything is running properly. 

You are recommended to run a test campaign on two or three users who can check whether the emails are landing in the inbox successfully. The test campaign will also help you check that the tracking is working properly. Also, this test run is not going to affect your EVS score in the slightest.