JS CLI from blaming your internet
source link: https://www.tuicool.com/articles/hit/ANVJj2F
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
blame-my-network
Check whether a website is up or down only for your network
Installation
One time usage,
$ npx blame-my-network http://theanubhav.com output: Connection successful from both, internal and external network.
Installing as global package
$ npm i -g blame-my-network $ blamemynetwork http://theanubhav.com output: Connection successful from both, internal and external network.
Usage
-
Connection available for both outside world and on your network
$ blamemynetwork http://theanubhav.com Connection successful from both, internal and external network.
-
Connection available for only your network and not to external network. In case site is either not public, or you are on VPN, or accessing organisation internal site, or manually entry for DNS on host machine/router.
$ blamemynetwork https://someinternalsite.com Only internal network could access the site.
-
Your network couldn't access the site while external network could access the site and you should
blame your network
for this.$ blamemynetwork https://blamethenetworksite.com Blame you network. The external network can acess the site.
-
Neither your network nor external network could access the site. Either site doesn't exists or is down for now
$ blamemynetwork https://blamethenetworksite.com Connection failure from both, internal and external network.
Known Issues
- For URL with explicit port : eg, 9080, 8080 will be reported as not available from external network
- Domains not respondind to http(or port 80, returning 302 or HSTS header) would be reported as not available from external network
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK