The new gTLDs that are being implemented have a few security
    concerns already. One of the major concerns is Name Collision, which
    results from a single domain name being used in different places.

    An example of this would be a company that uses .corp in an internal
    domain name. Under the new gTLD processes, the .corp gTLD could be
    bought by a different company for their use on the internet. If that
    happens, when a user tries to go to internal locations on a company
    network using .corp, there is a chance that they could actually get
    data back from the now legitimate .corp servers on the Internet.

    Using an internal domain name like this is a very common practice
    among businesses, so any issues that may come up dealing with .corp
    could be widespread. In the case of these new gTLD's, the owners of
    those servers could also manipulate their records, redirecting
    wayward queries. This opens the door to possible malware or phishing
    attacks on unsuspecting systems.

  via [1]New gTLD security implications.
    __________________________________________________________________

  My original entry is here: [2]New gTLD security implications. It posted
  Wed, 11 Sep 2013 22:13:29 +0000.
  Filed under: dns, InfoSec,

References

  1. http://www.net-security.org/article.php?id=1880&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+HelpNetSecurity+%28Help+Net+Security%29
  2. https://www.prjorgensen.com/2013/09/11/new-gtld-security-implications/

You are viewing proxied material from sdf.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.