# Does Encrypted Client Hello blind network monitoring?

Partly. With ECH, a sensor no longer sees the real server name in the handshake, so name-based rules, web filters and simple shadow-IT lists lose precision for the sites that use it. What remains is a lot: the destination IP address and who operates it, the outer public name, usually that of a large content-delivery network, DNS answers when DNS is not encrypted end to end, the timing, volume and direction of every flow, and the client fingerprint. Behavioural detections such as beaconing, scanning, lateral movement and unusual uploads do not depend on the server name and keep working. Internal traffic is rarely affected, because internal servers seldom publish ECH keys. For managed devices you can influence it: point them at your own DNS resolver and use the browser's enterprise policies, which can control ECH and encrypted DNS. Name-based visibility of AI or file-sharing services from any network sensor, NetSenX included, becomes less complete for sites behind ECH.

FAQ: [Encryption and encrypted traffic](https://netsenx.com/en/faq/encryption) · https://netsenx.com/en/faq/does-encrypted-client-hello-blind-network-monitoring

## Read next

- https://netsenx.com/en/encrypted-traffic-analysis
- https://netsenx.com/en/what-is-ndr

## Related questions

- [Do QUIC and HTTP/3 blind firewalls?](https://netsenx.com/en/faq/do-quic-and-http3-blind-firewalls)
- [Can DNS over HTTPS hide traffic from security monitoring?](https://netsenx.com/en/faq/can-dns-over-https-hide-traffic-from-security-monitoring)
- [How do I decrypt TLS traffic for troubleshooting?](https://netsenx.com/en/faq/how-to-decrypt-tls-for-troubleshooting)
- [How does a TLS handshake work?](https://netsenx.com/en/faq/how-does-a-tls-handshake-work)
- [What changed between TLS 1.2 and TLS 1.3?](https://netsenx.com/en/faq/what-changed-between-tls-1-2-and-tls-1-3)