Microsoft’s new Edge web browser tries to connect to various resources automatically when it is installed and/or running on a system. It is not uncommon for a browser to do so; a very common automated task is to check for program updates that may be downloaded and installed then on the local system.
Browsers tend to do so automatically to push new program versions to user systems. While that is desired most of the time, some users may prefer more control over the process.
Sometimes, it may be useful to know about the specific URLs that a browser tries to connect to. For one, it may be required if Edge is run in a network that sits behind a firewall and other security protections. The requests would simply be blocked automatically if security is configured to allow only access to certain resources on the Internet.
Some users may want to know about these URLs to block them right away. A user could block update requests to update Microsoft Edge manually when it is appropriate, or disable the experimentation and configuration service to avoid configuration or functionality changes made by Microsoft.
Administrators who don’t want Edge to connect to the Internet automatically could block all of these URLs in a firewall or security application.
Here is the master list of connections that Microsoft Edge may make or require to function properly:
- Run update checks
- HTTP download locations for Microsoft Edge
- HTTPS download locations for Microsoft Edge
- HTTP download locations for Microsoft Edge extensions
- HTTPS download locations for Microsoft Edge extensions
- Experimentation and configuration service
- Provide data for browser features such as tracking protection, certification recovation list, spellcheck dictionaries and more
- Download delivery optimization
- Client to server: *.do.dsp.mp.microsoft.com (HTTP Port 80, HTTPS Port 443)
- Client to client: TCP port 7680 should be open for inbound traffic