Kindly be advised we cannot cancel subscriptions or issue refunds on the forum.
You may cancel your Bitdefender subscription from Bitdefender Central or by contacting Customer Support at: https://www.bitdefender.com/consumer/support/help/

Thank you for your understanding.

Bitdefender Requesting Access to 40+ Connections

Options


Using Little Snitch coupled with Bitdefender for Mac.  Running El Capitan 10.11.4 on iMac with Retina, using Firefox 55.0.3 (64-bit).  Bitdefender asks to connect to the following servers ROUTINELY (i.e., every day), via the listed ports and protocols.  Are these all legit?  If they are, isn't this extremely inefficient?  To say the least, it's annoying.


 


A.  bdagentd:


(1) 54.210.126.134 (TCP 443);


(2) 216.xx.xxx.3 (UDP 53); 


(3) 216.xx.xxx.2 (UDP 53);


(4) 81.161.59.90 (TCP 80);


(5) nimbus.bitdefender.net (TCP 443);


(6) elb-nvi-amz.nimbus.bitdefender.net (TCP 443);


(7) elb-tky-amz.nimbus.bitdefender.net (TCP 443);


(8) elb-fra-amz.nimbus.bitdefender.net (TCP 443);


(9) elb-iri-amz.nimbus.bitdefender,net (TCP 443);


(10) 35.167.28.164 in domain nimbus.bitdefender.net (TCP 443);


(11) 54.213.119.76 in domain nimbus.bitdefender.net (TCP 443)


 


B.  BDCoreIssues:


(12) 52.45.110.161 (TCP 443);


(13) 216.xx.xxx.2 (UDP 53);


(14) 81.161.59.89 (TCP 80);


(15) nimbus.bitdefender.net (TCP 443);


(16) elb-fra-amz.nimbus.bitdefender.net (TCP 443);


(17) 216.xx.xxx.3 (UDP 53);


(18) elb-irl-amz.nibus.bitdefender.net (TCP 443);


(19) 52.40.128.18 in domain nimbus.bitdefender.net (TCP 443);


(20) elb-nvi-amz.nimbus.bitdefender.net (TCP 443);


(21) elb-tky-amz.nimbus.bitdefender.net (TCP 443);


(22) 54.70.243.192 9n domain nimbus.bitdefender..... (TCP 443);


(23) elb-nvi-amz.nimbus.bitdefender.net (TCP 80)


 


C.  BDLDaemon:


(24) 52.4.148.25 (TCP 443);


(25) 216.xx.xxx.2 (UDP 53);


(26) 216.xx.xxx.3 (UDP 53);


(27) 52.27.175.34 in domain nimbus.bitdefender.net (TCP 443);


(28) 54.69.9.185 in domain nimbus.bitdefender.net (TCP 443);


(29) elb-ore-amz.nimbus.bitdefender.net (TCP 443);


(30) elb-nvi-amz.nimbus.bitdefender.net (TCP 443);


(31) elb-tky-amz.nimbus.bitdefender.net (TCP 443);


(32) elb-irl-amz.nimbus.bitdefender.net (TCP 443);


(33) elb-fra-amz.nimbus.bitdefender.net (TCP 443);


 


D.  BDUpdDaemon:


(34) upgrade.bitdefender.com (TCP 80);


(35) nimbus.bitdefender.net (TCP 443);


(36) 216.xx.xxx.2 (UDP 53);


(37) 216.xx.xxx.3 (UDP 53);


(38) elb-iri-amz.nimbus.bitdefender.net (TCP 443);


(39) elb-nvi-amz.nimbus.bitdefender.net (TCP 443);


(40) elb.tky.amz.nimbus.bitdefender.net (TCP 443);


(41) elb-fra-amz.nimbus.bitdefender.net (TCP 443);


(42) elb-irl-amz.nimbus.bitdefender.net (TCP 443);


(43) 52.25.136.108 in domain nimbus.bitdefender.net (TCP 443);


 


E.  Antivirus for Mac:


(44) ipm.bitdefender.com (TCP 443).


 


Thanks for your assistance in this annoying and perplexing matter!


 

Comments

  • Roxana G
    Options


    Hello,


    In order for Bitdefender to work properly, you must allow all Bitdefender connections in Little Snitch.


     


  • this is a ridiculous number of connections and I am seeing the same thing. Why in the world would this be necessary for the app to function "properly"?

  • Roxana G
    Options


    Hello Jonny,


    Each Bitdefender process connects to Bitdefender servers in order to ensure a good communication between the product and user's account. The processes also communicate with the cloud for reporting infections and getting a status. All these processes connect to our servers in order to keep the product active and updated.


    The traffic used by these processes is pretty low.