Immunet - Not Recognizing Proxy

[4tygrit]

Is there a set of directions or actions available to allow Immunet to recognize my proxy? I am running WIN 10.
 

 

Thanks ahead of time.

[ritchie58]

Hello again 4tygrit,

You will need to make sure that the Domains & URL's that Immunet uses has unencumbered internet access to properly work with your proxy service.

Here is a list of Domains and URL's used by Immunet. Most of them use ports 80 & 443.

These Domains mostly use port  443/SSL, but may fall back to 80/HTTP, and also occasionally use 32137  TCP & UDP.

50.16.57.96

50.16.120.26

50.16.122.1

50.16.157.87

67.202.39.9

174.129.187.1

184.72.79.33

184.72.92.143

update.immunet.com

cloud-consumer-asn.immunet.com  

cloud-nfm.immunet.com

fmd.immunet.com

submit.immunet.com

console.amp.cisco.com

https://crash.immunet.com

cloud-consumer-est.immunet.com

https://consumer-event.immunet.com

https://cisco.amp.for.endpoints.connector.com

https://consumer-mgmt.immunet.com

https://policy.amp.cisco.com

public-cloud.immunet.com

ws.immunet.com

http://www.immunet.com/

http://support.immunet.com/

https://enterprise-m....sourcefire.com

current.cvd.win.clamav.net is accessed via a DNS query (port 53), and returns the IP of the nearest least busy ClamAV definitions server. Keep an eye on the up to date icon in the bottom right of Immunet’s interface and if it’s not a green check-mark click update now and if it still doesn’t change to a green check-mark after the update finishes then likely Immunet can’t reach the appropriate ClamAV definitions sever. 

Unfortunately the direct IP addresses Immunet connects to aren’t necessarily long lived and can’t reliably be whitelisted. They're generally only used in the case of DNS lookups failing continuously.

Best wishes, Ritchie...