There is a check of your domain, ~ 2,5 hours old - https://check-your-website.server-daten.de/?q=design.tufftoe.com#html-content
There are two https + ip address:
| img | src | https://146.148.39.87/wp-content/uploads/2019/04/Man.jpg | 1 | Ip addresses found, use domain name. | |||
|---|---|---|---|---|---|---|---|
| img | src | https://146.148.39.87/wp-content/uploads/2019/04/Man2-1.jpg | 1 | Ip addresses found, use domain name. |
Are these fixed?
The whynopadlock - error: Ignore it. You have a valid certificate
CN=design.tufftoe.com
29.05.2019
27.08.2019
expires in 89 days design.tufftoe.com - 1 entry
Keyalgorithm EC Public Key (384 bit, secp384r1)
but whynopadlock doesn't understand EC certificates with 384 bit.
That's a known error - same with my domain ( https://check-your-website.server-daten.de/?q=server-daten.de ):
CN=*.server-daten.de
02.04.2019
01.07.2019
expires in 32 days *.server-daten.de, server-daten.de - 2 entries
Keyalgorithm EC Public Key (384 bit, secp384r1)
Check it with whynopadlock, you will see the same result.
That's the reason of this notice:
Online:
Has one limit: Doesn’t understand my own Letsencrypt EC-384 bit certificate. EC-256 works.
2019-10 I've wrote a mail to whynopadlock with the problem, it's not fixed.