Website subdomain with dashes shows as not secure, when the same shows as a secure connection on Chrome

[life777eternal]

Description of the issue:
Created a new subdomain with dashes and then got a free Cert from SSLForFree.com and applied the Cert. So the right Cert shows on Brave and as Valid, but Brave still shows “Not Secure” beside the address. But when I opened the same pages on Google Chrome, it shows that the Connection is Secure.

Test

How can this issue be reproduced?

1. Create a subdomain with dashes.
2. Obtain a Cert for your new subdomain from SSLForFree.com
3. Apply the Cert to the Subdomain.

Expected result:
Should show that the connection is secure, like it does on my main website.

To All Churches

Brave Version( check About Brave):

Version 1.16.72 Chromium: 86.0.4240.183 (Official Build) (64-bit)

Additional Information:

Thank you.

[fanboynz]

Showing as secure here, not sure if showing the cert is instant. Creating a new sub/domain may not update the ssl certs straight away. But it’s looking good

@life777eternal

[life777eternal]

Ok, I see that now too, I just updated Brave after I posted this. Maybe the update fixed that, it was showing as not secure before.

Thank you.