Skip to content
Check whether a website is up or down only for your network
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib
.babelrc added babel configuration for future use Nov 11, 2018
.gitignore Initial commit Nov 10, 2018
.travis.yml build(fix) : added temporary fix for travis build Mar 14, 2019
LICENSE Initial commit Nov 10, 2018
README.md Fixed type Mar 8, 2019
index.js removed unexpected unicorn string Nov 12, 2018
package-lock.json added notifier plugin Nov 11, 2018
package.json Release 0.1.4 Mar 8, 2019

README.md

blame-my-network

Check whether a website is up or down only for your network

Build Status Coverage Status PRs Welcome GitHub issues

NPM

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

  1. Connection available for both outside world and on your network

    $ blamemynetwork http://theanubhav.com
    Connection successful from both, internal and external network.
    
  2. 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.
    
  3. 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 your network. The external network can acess the site.
    
  4. 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

  1. For URL with explicit port : eg, abc.com:9080, xyz.pqr.com:8080 will be reported as not available from external network
  2. Domains not responding to http(or port 80, returning 302 or HSTS header) would be reported as not available from external network

Contribution

Suggestions and PRs are welcome!

Please create issue or open PR request for contribution.

License

Open Source Love

refer LICENSE file in this repository.

You can’t perform that action at this time.