Tim Herzog II wrote:
I’ve noticed the same thing init.ess.apple.com checking into china. My regional blocking is stopping it. Hasn’t seemed to affect the operation of my apple devices however. Just started within the last week for me.
You will want to contact the app vendor that provided the blocking app you are using. (They're the best to discuss blocks and not-blocks, as (hopefully) they're collecting and curating a list. Otherwise, you get to do that.)
For most cases where details are required, log URL access and related for subsequent breach investigations, and that can be done at either at some local DNS resolver probably in the local network router, in a local DNS server if you're running one or more of those, or some DNS hosting providers almost certainly offer logging and nanny capabilities, with no added local software.
Implementing blocking means you own a whole lot more of the issues that this blocking inevitably causes, and a whole lot more about determining what is normal and what is not, and what network access Apple can and does use can and does change over time and across updates.
This host is Apple, and is apparently a content delivery network, and there are enough discussions around the 'net to imply this domain access is normal:
init.ess.apple.com. 289 IN CNAME init-cdn-lb.ess-apple.com.akadns.net.
init-cdn-lb.ess-apple.com.akadns.net. 19 IN CNAME appledownload.qtlcdn.com.
appledownload.qtlcdn.com. 20 IN A 113.5.170.192
appledownload.qtlcdn.com. 20 IN A 61.161.1.46
Per whois, qtlcdn.com is "Wangsu is a China-based company that provides content delivery network (CDN) and Internet data center (IDC) services."
More generally when considering these classes of network access reports: if the Apple DNS services are serving unauthorized domains and you're then catching access requests to unauthorized domains with local or network-monitoring tools, then there are seemingly two issues in your network:
1: your local or ISP DNS services are either compromised and providing additional translations for known domains, or there's a serious security event happening at Apple and its DNS servers.
2: your local macOS system is somehow also compromised, and is accessing these nefarious translations.
That seems unlikely. Which usually means it's the add-on security apps mis-detecting or otherwise blocking normal access.
To be absolutely clear, allowing or blocking access is entirely your choice, and entirely your prerogative. Installing and maintaining tools to perform that, too. Endpoint security can be useful. But you'll need to have your own or your own contracted IT monitoring determining the validity and necessity of that activity for each domain. You and your IT entirely own these determinations and the associated research and risks, too.
If you should find a necessary-for-normal-operations DNS host entry captured in your tooling that's not listed in Apple's published list, have a chat directly with Apple.
Here is Apple's published list: Use Apple products on enterprise networks - Apple Support
And yes, it appears this host is not listed by Apple. Accordingly, check with Apple Support.