Security Issue due to communication with localhost when checking certificateSolved

Our software uses limeLM licensing so when we activate the app, we check for a certificate with WyDay.com. When we do, logs in TCPViewer showed that we communicate through a localhost server (DNS, Standard query 0xcf7c A wyday.com). We also see that there are http connections (HTTP, CONNECT qyday.com:442 HTTP/1.1). Can you tell us what you transmit via localhost? Is there any way we can avoid using this? It raises security issues that our client brought up.

Thank you for all your hard work. We appreciate your support, and look forward to hearing from you soon.

K Yasui

Use the latest version of TurboActivate (which only ever communicated over TLS). Currently 4.3.3: https://wyday.com/limelm/api/#turboactivate

Also, if the customer is changing their DNS or "localhosts" file then you will see weirdness like this. So... don't mess with those files.