The Chrome Root Program and the CA/Browser Forum are implementing new security requirements for HTTPS certificate issuers to enhance internet security. They are phasing out 11 outdated Domain Control Validation methods that rely on weak verification signals such as physical mail, phone calls, or emails. This change aims to close loopholes that attackers could exploit to obtain fraudulent certificates. The transition will be gradual, with the full impact expected by March 2028. Domain Control Validation is critical for ensuring that only legitimate domain operators receive certificates. Attackers could misuse valid certificates to impersonate websites or intercept traffic if these checks are weak. The new approach uses robust, automated methods, like challenge-response mechanisms, instead of relying on outdated practices like WHOIS lookups or email confirmations, which have proven vulnerable. The changes will be largely invisible to users, but they significantly strengthen the security framework behind certificate issuance. By promoting modern validation methods, the initiative aims to create a safer browsing experience for everyone. It also encourages faster and more efficient certificate management through automation, which improves the overall resilience of the web ecosystem.