I'm trying to verify my website I bought the domain through hover.com but I can't find any information on how to make it happen

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: www.davidaste.com

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is: hover.com

I can login to a root shell on my machine (yes or no, or I don't know): I don't know

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): I don't know

1 Like

Welcome to the Let's Encrypt Community, David :slightly_smiling_face:

I'm not exactly sure what you're trying to verify. Here is the WHOIS record for davidaste.com :


As you can probably see, your question is a little bit confusing..

What do you mean by "to verify"? Is this related to Let's Encrypt or SSL/TLS in any way?


I can verify ...:

Name:      davidaste.com

Name:    im-router-service.com
Aliases: www.davidaste.com

Not what you were looking for?

Note: The HTTP WWW site doesn't forward to HTTPS.

And HTTPS the apex fails:


I concur, @rg305, though I do get a 200 for the HTTPS apex.

Using Redirect Checker | Check your Statuscode 301 vs 302...

301 Moved Permanently
200 OK
200 OK
200 OK

There are two apex IPs...
Maybe one works?
Maybe my FW is blocking me from the working one? - LOL


Is there an IPv6?



Just the two IPv4s.


This is concerning too...

www.davidaste.com. 900 IN CNAME im-router-service.com.

It "works".
A "coming soon / landing page" with blah blah "Check back later."

It fails for HTTPS though (not my FW):

openssl s_client -connect
140191993213376:error:0200206F:system library:connect:Connection refused:../crypto/bio/b_sock2.c:110:
140191993213376:error:2008A067:BIO routines:BIO_connect:connect error:../crypto/bio/b_sock2.c:111:

openssl s_client -connect
140291527385536:error:0200206E:system library:connect:Connection timed out:../crypto/bio/b_sock2.c:110:
140291527385536:error:2008A067:BIO routines:BIO_connect:connect error:../crypto/bio/b_sock2.c:111:

One with "Connection refused"
One with "Connection timed out"

The cert doesn't (yet) cover the apex:

A little DNS modification and another run at certbot can get that going.
OR can it?
Won't be able to CNAME the apex [that'll wreak havoc upon the interwebs - LOL].


Thanks for replying! As you can probably tell I'm not too sure about what I'm doing here lol could you tell me why it's concerning?

1 Like

Thanks for replying! As you can probably tell I'm a little out of my depth here. Could you elaborate a little bit? Its just that you could be talking in a foreign language right now

1 Like

What are you trying to do?
What is NOT being done?

I speak geek/nerd and plain old English too - LOL


Yes so basically my whole goal here was to get the "verified" like the screenshot here, that how I found out about this place actually
Screen Shot 2022-01-20 at 12.46.43 AM

Connect to:


There you should see a similar lock (and verification).


The "problem" comes in with the insecure site:


It doesn't forward to HTTPS [and remains insecure].

1 Like

Let me step back a couple of paces ...
There are basically four common ways to reach any web site:

  • http://example.com
  • https://example.com
  • http://www.example.com
  • https://www.example.com

Generally speaking, only one of the four is considered the "active" / "main site".
The other three are expected to direct the browsing client onward in that direction.
The HTTP sites forward to the HTTPS sites
And the base domain forwards to "www" [or in the other direction]

In your case, the base domain is being hosted by a parking page site, so it can't be set to forward and it doesn't support HTTPS.
So that covers two of the four.
The other two, the insecure should forward to the secure [but it doesn't (yet)].


Ok so I can't "verify it" aka stop showing it's an "insecure site" ? or what should I do?

Cover all four cases (as best you can).
They may involve separate providers.
May require you to update the HTML or add an .htaccess file.
[YMMV - speak with the providers about what you want and they may be able to help or point you in the right direction]

But technically you already do have a validated site.


Who provides the hosting for the WWW site?
Is that GoDaddy?


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.