MasterCard DNS Error Exposed for Years | Domain Clout News

The error was caused by a misconfigured DNS server, which was supposed to end in **akam.net** but instead relied on the domain **akam.ne**. This tiny typo could have allowed anyone to register the domain and intercept Internet traffic for **MasterCard**. The incident has sparked debate about the company's security practices and the need for greater transparency. [[information-security|Information security]] experts are calling for **MasterCard** to provide more information about the incident and to take steps to prevent similar errors in the future. For more information on information security, see [[information-security-best-practices|Information Security Best Practices]].

• The DNS error could have allowed anyone to intercept Internet traffic for **MasterCard**
• The error was caused by a misconfigured DNS server
• The error was discovered by security researcher **Philippe Caturegli**
• The incident highlights the importance of [[dns-security|DNS security]] and regular security audits
• The incident raises questions about the effectiveness of **MasterCard**'s security practices

The DNS error is a reminder that even large organizations like **MasterCard** can make mistakes. The fact that the error went undetected for nearly **five years** highlights the need for regular security audits and reviews of DNS settings. The incident also raises questions about the effectiveness of **MasterCard**'s security practices and the need for greater transparency. While the company has corrected the error, it is unclear what steps are being taken to prevent similar incidents in the future. For more information on security audits, see [[security-audits|Security Audits]].

The discovery and correction of the DNS error is a positive development for **MasterCard** and its customers. The fact that the error was discovered by a security researcher and not by cybercriminals is a testament to the importance of responsible disclosure and the role of security researchers in identifying and reporting vulnerabilities. **MasterCard**'s prompt response to the issue and correction of the error demonstrates the company's commitment to [[cybersecurity|cybersecurity]] and the protection of its customers' data. For more information on responsible disclosure, see [[responsible-disclosure|Responsible Disclosure]].

The DNS error is a serious concern for **MasterCard** and its customers. The fact that the error could have allowed anyone to intercept Internet traffic for the company raises significant questions about the security of **MasterCard**'s systems. The incident highlights the need for greater investment in [[cybersecurity|cybersecurity]] and the importance of regular security audits and reviews of DNS settings. The fact that the error was discovered by a security researcher and not by **MasterCard** itself raises concerns about the company's ability to detect and respond to security incidents. For more information on cybersecurity investment, see [[cybersecurity-investment|Cybersecurity Investment]].

Originally reported by Krebs on Security