In newer products with the Unreal engine of Epic Games, Inc., addresses are increasingly appearing that are initialized at the start of the game and call outside. Here at, depending on the implementation, the games themselves seem to perform the checks or optionally via the windowown "svchost.exe" (exception).
The statement of the already known support employee "Valve, Kal", these IP checks are now firmly integrated because "Steam" wants to know.
These are standard IP checks. IPv6 is going to be basically mandatory soon, and Steam needs to know how many of our users internet connections support the new format.
Again, an example of how a company classifies a product as a buddy and friend. How Microsoft Corporation makes a friend with Windows 10 and 11 so that users trust the system as much as possible.
Unfortunately, "Steam" wants nothing, but the Valve Corporation. And the Valve Corporation demands it. The checks are now mandatory for every start of the client active and regardless of the support statement, it can be said that the IPv6 checks including captive portal queries by the Valve Corporation are a replacement for the old telemetry services from Epic Games, Inc.
In 2017, there was an article called Valve Isn't Your Friend, and Steam isn't healthy for games on Polygon, which has just somewhat lulled the behavior.
Users are left in the dark about this. These will only get to see that a game started by them needs a firewall release.
With the procedure, a targeted block can not hurt. In order to enjoy your own games or even the use of Steam itself, these addresses are not required.
Steam_IPv6_Checks.txt (4.52 KB)
http://ipv6check-http.steamcontent.com/server-status Success
http://ipv6check-http.steamcontent.com/ipv6check
[08.29 00:33:10] Name der Exe (2940) - ipv6check-udp.steamcontent.com resolve via 192.x.x.x:53 : DNS
[08.29 00:33:10] Name der Exe (2940) - ipv6check-http.steamcontent.com resolve via 192.x.x.x:53 : DNS
