Checking Health
Checking Health is a command-line tool for performing HTTP/HTTPS endpoint health checks with clean, real-time, and highly readable output.
It helps you quickly validate APIs, services, and environments with useful diagnostics like latency, response size, content type, and more.
✨ Features
-
⚡ Real-time execution (results printed as they complete)
-
🎯 Endpoint identification via URL path (
TYPE) -
📊 Rich metrics per request:
- Status (OK / FAIL)
- HTTP status code
- Domain & IP
- Content-Type
- Response size
- Request time (
REQ) - Total time (
TIME) - HTML
<title>(when available)
-
🎨 Clean and colorful terminal output
-
📈 Summary with aggregated metrics
-
🧪 Fully testable with
pytest -
📦 Distributed via PyPI
📦 Installation
Install directly from PyPI:
pip install checking-health
🔗 https://pypi.org/project/checking-health
▶️ Usage
checking-health endpoints.txt --timeout 3
📄 Input File Format
Provide a .txt file with one endpoint per line:
# success example
google.com
# failure example
google.comm
https://api.example.com/status
Rules
- Empty lines are ignored
- Lines starting with
#are ignored - URLs without scheme default to
https://
📊 Example Output
TYPE STATUS HTTP DOMAIN IP CONTENT-TYPE SIZE REQ(ms) TIME(ms) TITLE
-------------------------------------------------------------------------------------------------------------------------------
health OK 200 google.com 142.250.191.78 text/html 17.4KB 31 53 Google
status FAIL - google.comm - - 0B 14 14 -
Summary
------------------------------
Total : 2
Success : 1
Failure : 1
REQ average : 22ms
TIME average : 33ms
🧠 Concepts
TYPE
Derived from the last segment of the URL path:
| URL | TYPE |
|---|---|
/healthcheck |
healthcheck |
/healthcheck/status |
status |
/ |
root |
REQ(ms)
Time until the server starts responding (latency).
TIME(ms)
Total time including response download.
SIZE
Actual size of the response body.
TITLE
Extracted from HTML responses (<title> tag), when available.
🔍 Use Cases
- API health validation
- Deployment smoke tests
- Environment verification (dev/staging/prod)
- Quick debugging of network or DNS issues
- Bulk endpoint checking
⚠️ Limitations
- Does not break down DNS / TCP / TLS timings
- Downloads full response body (can impact large responses)
- Runs sequentially (no parallel execution)
🧪 Testing
Install pytest:
pip install pytest
Run tests:
pytest -q
👤 Author
André Argôlo CTO • Software Architect • DevOps
- 🌐 Website: https://argolo.dev
- 🐙 GitHub: https://github.com/argolo
📜 Licença
MIT License
Release files for checking-health 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| checking_health-1.0.0.tar.gz | 6.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| checking_health-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.8 kB
Release files / checking_health-1.0.0.tar.gz
| Download URL | checking_health-1.0.0.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f2b5c64f333fa028c89edcdbdfb5f712e86e884e52ca29af8618618d4d3827d
|
|
BLAKE2b-256 checksum How to use checksums |
364767503a71e03486dd960c3e8b53756621bf5f92e883e30c73cb6806a6a7a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 14, 2026.
Transparency logRelease files / checking_health-1.0.0-py3-none-any.whl
| Download URL | checking_health-1.0.0-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
24395f0f67e593b78097c8d0c0605dd986f0ff7cc35ff458fbae71e85d965159
|
|
BLAKE2b-256 checksum How to use checksums |
c9fd5402343d2d3c00fcd032dd1630d840ff7e39d8969ca0b0f576d9ed0288c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 14, 2026.
Transparency log