Microsoft Edge is making Suspicious Connection?

Based on the Technical Contact Name of "MSN Hostmaster" in that Whois Registration record that _AW_ referenced, I suspect this was a legacy service being used by Microsoft's MSN group for trouble-shooting browser connectivity issues. Likely it's a service they've dropped that is referenced internally by the browser itself but doesn't create an error message because it operates in the background, while the unrelated security feature in Bitdefender is detecting it due to the certificate issue.

The reason I say this is that there have apparently been previous instances of reporting by Bitdefender of similar issues with MSEdge and other services that were either dropped or malfunctioning, so it's not new, just a new site/service triggering this Bitdefender "protection", while no one else is even aware it's happening.

Here's an old thread about the EBooks reading feature that was triggering this error in 2019:

MicrosoftEdge.exe Suspicious Connection? - Microsoft Community

Here's another back in 2021 where a few were having issues with what appears to be the Store's extensions database service, which based on the posts was likely transiently malfunctioning in some way at least for these users.

Microsoft Edge - Bitdefender Blocking Suspicious Connection On Load - Microsoft Q&A

I think a saw a couple others, but I'll stop there and let you look for those yourself if you wish.

Based on all of this and the history I found of these relatively useless Bitdefender detections in general, I'd at least set an exception for this current error likely relating to MSN and if it was me, I'd turn off what's obviously not a useful security feature in todays' world, since MSEdge itself warns quite effectively when websites I browse normally don't contain a valid certificate. In fact, Edge has become rather aggressive about making me aware of websites that aren't properly SSL secured by making them difficult to access.

Rob

< EDIT > Minor wording or spelling errors fixed. Following section added.

To see how Microsoft Edge or any other browser handles these and other types of SSL (Certificate) errors, the following page has the most common of these displayed in red lettering immediately below the 'Certificate' title in the left-hand column.

badssl.com

When Edge displays one of these certificate errors, there's a button titled 'Advanced' immediately below the error message on the lower left-hand side of the page. Pressing this provides a more complete and somewhat more readable description of what the particular error message actually means.

To further clarify what I meant in my first paragraph by "trouble-shooting browser connectivity issues", see the following documents that describe the W3C's Network Error Logging (NEL) first briefly and then in excruciating detail. Note that I included the first document from NELReports,com due to it's simple description of the purpose, while the others provide technical reference both from the Mozilla (MDN) developer network and the W3C itself relating to NEL.

Network Error Logging - NEL Reports

Network Error Logging - HTTP | MDN

Network Error Logging - W3C

A more focused description of what I believe happened is that as another thread here discovered, the certificate related to this domain had expired the previous day, which is obviously why the Bitdefender detection is occurring. However, whether this is truly an issue or not depends upon whether Microsoft MSN intends to continue using the NEL reporting service or not, since another way to eventually 'fix' the issue is to simply remove the code which is calling this, whether that's internal to MS Edge or contained on various web pages displayed by the MSN News Feed some in that other thread some feel might be involved.

In either case, leaving the detection in place and complaining about it will change nothing, since it's a weekend and likely no one with the ability to update the certificate is in the office, so the obvious fix is to at least temporarily exclude the site[s] creating the issues for you personally. If MSN is planning to remove the NEL calls from their pages and no longer support it, then it may never truly be fixed and only disappear over time as the pages involved are either updated or exit the site by attrition.

No one here knows the answer to that and until we either get confirmation from someone at MSN, the certificate is renewed, or the problem disappears for another reason like code modification, we have no way of knowing. Since the site(s) and code involved are all within Microsoft's control, it doesn't really matter that this error is occurring, so leaving the detection intact and letting it annoy you is simply foolish, so turn it off or exclude it until you hear otherwise.

it happend to me now deff.nelre.net like you said please help us

Report the potential false positive detection to Bitdefender:

https://www.bitdefender.com.au/consumer/support/answer/88562/

Then add the site to Bitdefender's exclusions:

How to stop Bitdefender from blocking a safe website or an online app

This is interesting as I am having the same issue. I also utilize Bitdefender. However, when I used Bitdefender VPN for the free time of about 200MB they give I don't get that. In a previous message could this be something Bitdefender should look into....or is anyone in this thread NOT using Bitdefender.