3 ms·
The problem with that concept is: Bad guys steal your domain (e.g. break into the DNS provider and change the A records). They go to Google, request a cert, and
by Someone1234 12y ago
The problem with that concept is: Bad guys steal your domain (e.g. break into the DNS provider and change the A records). They go to Google, request a cert, and Google checks the domain for the verification code (like Google Apps).
Google generates you a new certificate, you then install the certificate, and now users are even less suspecting that the domain has been compromised. It even defeats a Strict Transport Security policy.
- nucleardog 12y agoAs opposed to something like RapidSSL which would require an MX record change? Point the MX record to an intermediary server which forwards all non-RapidSSL e-mail (so no one notices an interruption) and captures the RapidSSL messages for you. Generate certificate. Once you have the certificate, you can swap the A record over to your own machine and no one would be any wiser.