I think "apple-id-2.com" is a high risk domain that must be blocked to issue DV 
SSL to those domains.

Here is the list of some high risk domains related to Microsoft and Google that 
Let's Encrypt issued DV SSL certificates to those domains:
https://crt.sh/?id=77034583  for microsoftonline.us.com, a fake Office 365 
login site   
https://crt.sh/?id=71789336  for mail.google-androids.ru
https://crt.sh/?id=82075006  for marketgoogle.xyz
https://crt.sh/?id=65208905  for google.ligboy.org


Best Regards,

Richard

-----Original Message-----
From: dev-security-policy 
[mailto:[email protected]] On 
Behalf Of Gervase Markham via dev-security-policy
Sent: Thursday, February 23, 2017 8:30 AM
To: Tony Zhaocheng Tan <[email protected]>; 
[email protected]
Subject: Re: Let's Encrypt appears to issue a certificate for a domain that 
doesn't exist

On 22/02/17 14:42, Tony Zhaocheng Tan wrote:
> On 2017-01-03, Let's Encrypt issued a certificate for apple-id-2.com.
> However, until today, the domain apple-id-2.com has apparently never 
> been registered. How was the certificate issued?

On Hacker News, Josh Aas writes:

"Head of Let's Encrypt here. Our team is looking into this and so far we don't 
see any evidence of mis-issuance in our logs. It looks like the domain in 
question, 'apple-id-2.com', was registered and DNS resolved for it successfully 
at time of issuance. Here is the valid authorization record including the 
resolved IP addresses for 'apple-id-2.com':

https://acme-v01.api.letsencrypt.org/acme/authz/uZGv2KXUJ6Hl...

We can't be sure why the reporter was unable to find a WHOIS record, we can 
only confirm that validation properly succeeded at time of issuance.

Update: Squarespace has confirmed that they did register the domain and then 
released it after getting a certificate from us."

There is currently an entry in WHOIS, because some well-meaning but unhelpful 
person registered it today. I assume that if a domain is registered and then 
released, and then re-registered, the "Creation"
date is of the re-registration, not the first ever registration.

So unless someone can show it was unregistered at the time of issuance, I don't 
see an issue here.

Gerv
_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy
_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy

Reply via email to