During the extended validation process for domain names, which certificate feature is not feasible?

The prospect of using a wildcard certificate during the extended validation (EV) process for domain names is not feasible. Wildcard certificates allow for the security of a base domain and its subdomains using a single certificate, which potentially leads to broader usage than the stringent requirements established for EV certificates.

EV certificates are designed to provide the highest level of trust and assurance to users by verifying the legal identity of the entity requesting the certificate. The EV process involves rigorous checks, including validating the organization’s identity, physical location, and legal status, ensuring that the entity requesting the certificate is indeed the legitimate owner and has the authority to operate under that domain.

In contrast, wildcard certificates, by their nature, can secure multiple subdomains but may introduce complexity in confirming the specific subdomain ownership during the EV validation process. This complexity conflicts with the stringent EV requirements, which aim to provide a clear, auditable trail of identity verification for individual domains rather than general coverage across multiple subdomains.

In terms of the other choices, options like subdomains, SSL, and HTTPS are all feasible within the scope of the extended validation process. Subdomains can still be validated independently, SSL is a protocol that enables secure communication, and HTTPS is the secure version of HTTP, utilizing SSL/T