Timeout using checkhost.unboundtest.com

I received an email from you on March 3rd indicating that one of my domains (nthos.com) was affected by the recent bug you found. I renewed the certificate and then checked it using https://checkhost.unboundtest.com/. The response I got was:

unknown: nthos.com: dial tcp 45.79.181.36:443: i/o timeout

I rechecked multiple times over an extended period, and always got the same response. Out of curiosity, I then checked all my other domains using the above URL and found that two more of them (nthos.net and nthos.org) got the same timeout response.

I then created new certificates for all three, but upon testing using the above URL, still get the timeout response.

What exactly is the tool checking, and should I be concerned about the response?

Thanks!

1 Like

Hi @jeff_harp

if you have created a new certificate and if the critical certificate is replaced, the old certificate isn’t longer active.

So your job is done, there is no check required.

Ah - checking your domain - https://check-your-website.server-daten.de/?q=nthos.com

There are only timeouts.

Domainname Http-Status redirect Sec. G
• http://nthos.com/ 45.79.181.36 -14 10.037 T
Timeout - The operation has timed out
• http://www.nthos.com/ 45.79.181.36 -14 10.034 T
Timeout - The operation has timed out
• https://nthos.com/ 45.79.181.36 -14 10.037 T
Timeout - The operation has timed out
• https://www.nthos.com/ 45.79.181.36 -14 10.030 T
Timeout - The operation has timed out

So the tool you use can’t check your domain -> that’s the error.

1 Like

Hi @JuergenAuer

Thank you for your fast response and the link to your site, which is impressive and provides a great deal of useful information.

As soon as I looked at your site and thought about the fact that the three domains in question all share the same IP address, I realized what the problem was. I had been debugging some server-side issues and was looking at log files the same day the certificate problems surfaced.

There was so much unwanted traffic in the logs from people/bots sniffing for vulnerabilities that I restricted access in the firewall to a limited set of IPs. Unfortunately, I forgot to remove the restrictions when I was done! Too little sleep and too many distractions…

I sincerely apologize for wasting your time on this. But I am glad I learned about your site. I’m sure I will use it again in the future.

2 Likes

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