RFC 2606 is a "best current practices" document, which is less stringent than a standard. I'd say it gives them flexibility. Even updated by RFC 6761, the prac

RFC 2606 is a "best current practices" document, which is less stringent than a standard. I'd say it gives them flexibility. Even updated by RFC 6761, the practices surrounding example.com only go so far as SHOULD and SHOULD NOT. That said, I think it's a horrible idea to treat example.com differently, but that's just because I can't think of a single reason why you would want to do so. :)