Short answer: there is a lot more wrong with that site than just dropping ping packets, so I'm not sure that is a valid test
Longer answer:
1.) I noticed the question in this thread is starting to take a turn. Originally, the question / goal as I read it was merely ~
I would like to test if an internet connection is available from a stack.
Ping satisfies that question fairly quickly,
*if* you just want to know if your connected, and while pinging google certainly works, there are other options (such as a dns server, etc). In fact, IF I really want to know if i'm connected using ping, I'd probably pick 3 sites known to respond to ping for the 1 ping test, as the likelyhood that 3 sites would be down simultaneously is not very high.
2.) In what I am going to call part 2 of this thread, the question is shifting to
'how do you tell if a particular website is online if it drops ping packets'. Your example site,
"durandexpertises.com" brings up some interesting challenges, but I am not sure they are due to ping, per se.
Other testing tools give at best mixed results. Normally when I am looking for blockage on the network, I resort to one of the various forms of traceroute (tracerrt on Win, traceroute or mtr on Lin and probably on OSX).
Traceroute literally traces every hop it takes you to get somewhere, but of course, it takes longer than ping normally. For your example site, the last hop letting it run unrestricted wasn't very informative, but I do know it connected at 13 hops -
Code: Select all
MTR.0.92,1585739064,OK,durandexpertises.com,13,???,100.00,10,10,0.00,0.00,0.00,0.00,0.00
Telnet is another good way to tell if something is up, but your example apparently isn't setup to answer on the default port(s) tested by telnet. Go figure.
Code: Select all
~$ telnet durandexpertises.com
Trying 136.0.165.69... <-- resolved the host name to an IP address, anyway...
telnet: Unable to connect to remote host: Connection timed out
3.) Things I sometimes use to test off the cli, which I did in this case, using an actual browser to check the url, and using " Is It Down Right Now".
First, the web browser -
Firefox wrote:
Warning: Potential Security Risk Ahead
Firefox detected an issue and did not continue to www.durandexpertises.com.
The website is either misconfigured or your computer clock is set to the wrong time.
It’s likely the website’s certificate is expired, which prevents Firefox from connecting securely. If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details.
What can you do about it?
Your computer clock is set to 4/1/2020. Make sure your computer is set to the correct date, time, and time zone in your system settings, and then refresh
www.durandexpertises.com.
-->> If your clock is already set to the right time,
the website is likely misconfigured, and there is nothing you can do to resolve the issue. You can notify the website’s administrator about the problem.
Since my computer is set (as probably most are) to an ntp server, I'm relatively certain my clock and date are right. This brought me to my last test, the "is it down" site.
Website Name:Durandexpertises
durandexpertises.comURL Checked:
no responseResponse Time:
unknownLast Down:
DOWN
Durandexpertises.com is DOWN
It is not just you. The server is not responding...
Considering the results I received outside of 'ping', again, I'm not really sure this site is a good example site even for the 2nd part of the thread. At best, you can only tell that the dns resolves, and that it can be reached in 13 hops, but you won't get much more than that from standard testing methods.