Ask HN: Should ICANN be allowed to run example.com

The domains example.com and example.org are reserved in RFC 2606 and RFC 6761 for documentation purposes, however they're resolvable, hosted on AWS, and serve web content on http and https protocols.

The SSL certificates are issued to ICANN: https://crt.sh/?Identity=%.example.com

However sometimes SSL certificates for example domains issued to other entities: https://crt.sh/?id=24560621 but this is tangential.

The amount of accidental traffic and queries directed at these domains could be substantial. Some of these requests may contain confidential information. Is this a possible conflict/risk or should ICANN be absolved?