dl.delivery.mp.microsoft.com cache site marked as harmfull

Jan-Eric · 2024-05-13T04:34:01+00:00

There was an error rendering this rich post.

Microsoft seems to have outsourced their updates distribution and this gets blocked.

How do I allow this traffic as it's a IP address that's changing?

Find more posts tagged with

Accepted answers

Jan-Eric

No problem so far after I added IPs (url) from 151.139.186.x subnet to allowed sites.

I would be nice a nice feature to be able to add IP subnets to Browsing protection/Allowed sites.

All comments

JamesC

Hi @Jan-Eric ,

Glad to hear there are no further issues. You may refer the below to submit a Feature Request:

If you are using our business security products you can directly raise a feature request aka ideas directly via Elements Security Center > Profile logo( top right corner)> My Feedback functionality. which takes the portal user to .
Or get in touch with sales contact. If you do not know who your WithSecure sales contact is or are unable to reach them, please open a support ticket and your feature request will be relayed to the developers:

https://ideas.withsecure.com/ https://www.withsecure.com/us-en/support/contact-support/email-support

Jan-Eric

No problem so far after I added IPs (url) from 151.139.186.x subnet to allowed sites.

I would be nice a nice feature to be able to add IP subnets to Browsing protection/Allowed sites.

JamesC

Hi @Jan-Eric

If you are still having issues, we suggest to use the Submit-a-Sample feature so our detection team can investigate further

Jan-Eric

There are more IPs and cacheOriginHosts but Microsoft doesn't publicly list their cache IPs. But fot thr moment they all seems to originate from 151.139.186.x subnet.
hxxp://151.139.186.28
hxxp://151.139.186.38
hxxp://151.139.186.41
hxxp://151.139.186.42
hxxp://151.139.186.71
hxxp://151.139.186.74
cacheHostOrigin=msedge.f.dl.delivery.mp.microsoft.com|
cacheHostOrigin=officecdn.microsoft.com
cacheHostOrigin=download.windowsupdate.com

JamesC

Hi @Jan-Eric

My sincere apologies for the inconvenience and thank you for reaching out to WithSecure Community.

Our detection team have now fixed the URL to be clean.

Do check this and let us know if issue persists.