Skip to content
A fast http and https prober, to check which URLs are alive
Python Shell Makefile
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs Initial Commit Aug 3, 2019
halive Applied pylint to source code Aug 5, 2019
img Added scheme in README Aug 3, 2019
tests Changed GET method to HEAD and fixed a bug on URL parsing Aug 3, 2019
.gitignore Updated loading of URLs to occupy less memory Aug 4, 2019
.travis.yml
AUTHORS Initial Commit Aug 3, 2019
CHANGELOG.rst Initial Commit Aug 3, 2019
CODE_OF_CONDUCT.md Added pull request template and code of conduct Aug 4, 2019
CONTRIBUTING.rst Initial Commit Aug 3, 2019
ISSUE_TEMPLATE.md Added issue template Aug 4, 2019
LICENSE Initial Commit Aug 3, 2019
MANIFEST.in Initial Commit Aug 3, 2019
Makefile Changed GET method to HEAD and fixed a bug on URL parsing Aug 3, 2019
PULL_REQUEST_TEMPLATE.md Added issue template Aug 4, 2019
README.md Added scheme in README Aug 3, 2019
TODO.md Applied pylint to source code Aug 5, 2019
release Initial Commit Aug 3, 2019
requirements-dev.txt Initial Commit Aug 3, 2019
requirements.txt Added requirements Aug 3, 2019
setup.cfg Initial Commit Aug 3, 2019
setup.py Initial Commit Aug 3, 2019

README.md

halive. An http/s prober, to check which URLs are alive.

Author: gnc

Copyright: © 2019, gnc.

Date: 2019-08-03

Version: 0.1.0

PURPOSE

Halive is a software used to get a list of alive hosts starting from a list of hosts whose status is unknown in a short amount of time. It's fast, indeed halive achieve its speed through its asynchronous design.

Once we have a list of domains/subdomains gathered from the reconnaissance phase, (for example through pdlist) we want to check fastly which subdomains are alive and which are not. To this purpose we can use halive and obtain from the initial list of hostnames only the alive subdomains.

INSTALLATION

We can install halive simply by doing:

git clone https://github.com/gnebbia/halive
cd halive
pip install -r requirements.txt
python setup.py install

USAGE

In order to get the list of alive hosts with also the response status code we can do:

halive big_list_of_urls.txt

The default speed is set through the use of 20 (default) workers, we can increase the speed by increasing the number of workers, by doing:

halive big_list_of_urls.txt -t 100
# in this case we use 100 workers

We can also print only URLs without response code and store results in a text file, by doing:

halive big_lists_of_urls.txt -t 100 --only-urls --output report.txt 

We can also only filter URLs which do not reply with 4XX HTTP codes, this can be done by executing halive in this way:

halive big_lists_of_urls.txt -t 100 --only-success --only-urls --output report.txt 

A usage example in the gif below:

COPYRIGHT

Copyright © 2019, gnc. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.

  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

  3. Neither the name of the author of this software nor the names of contributors to this software may be used to endorse or promote products derived from this software without specific prior written consent.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

You can’t perform that action at this time.