osintverse-community/ipwhois
Looks up who holds an IP address through RDAP: network, ASN, organisation and contacts
No key · Docker
Summarises what ONYPHE's internet scans know about an IP address: open ports, services, domains, owner, location
Community-packaged from github.com/onyphe/pyonyphe: the registry's community pins the upstream release; the tool is its authors' work. Maintain that project? Claim this package.
Run
Through ot mcp, an agent calls run_tool with this; ot asks you before anything that goes online or touches a target. Set it up: ot mcp install claude (or cursor, vscode, codex, gemini).
{"tool":"osintverse-community/onyphe","target":"8.8.8.8","input_type":"ip"}Or just say: "Run osintverse-community/onyphe on 8.8.8.8 with OTInstaller." The registry's read-only MCP server at api.otinstaller.com/mcp can find tools without installing anything.
ot run osintverse-community/onyphe ip:8.8.8.8 --format tableot install osintverse-community/onypheDocker image in a read-only container · network allowed · needs ONYPHE_API_KEY · up to 2 min. The first ot run installs the tool after asking once. The example value is the registry's own test input, so this command has run. Drop --format table for JSON.
ot? Install it in one linecurl -fsSL https://get.otinstaller.com/ot | shot release for your machine from GitHub Releases.checksums.txt, and the Ed25519 signature on that file against the key built into the script.ot in /usr/local/bin or ~/.local/bin. Nothing else is written. Read the script.irm https://get.otinstaller.com/ot.ps1 | iexot release for your machine from GitHub Releases.checksums.txt, and the Ed25519 signature on that file against the key built into the script.ot in %LOCALAPPDATA%\Programs\ot, and adds it to your PATH. Nothing else is written. Read the script.sha256:5437d922…063a75. The same bytes on every install; ot pulls by digest, never by tag.ot checks the same identity before every install and refuses another signer.ot pulls the same digest from the mirror and checks the same signature.Not health-checked yet; 3.1.1 came out today; nobody has said yet whether it works.
3.1.1 is in its first week. Nobody has said whether it works yet.
Used 3.1.1?It's broken for me
{
"envelope": 1,
"tool": "osintverse-community/onyphe@3.1.1",
"runtime": "docker",
"input": {
"ip": "8.8.8.8"
},
"started_at": "2026-10-21T09:00:00Z",
"duration_ms": 4100,
"exit_code": 0,
"entities": [
{
"type": "ip",
"value": "192.0.2.1"
},
{
"type": "domain",
"value": "example.com"
},
{
"type": "organization",
"value": "Example Ltd"
}
],
"warnings": []
}Every tool returns this shape, shaped here from what this tool declares it finds. --format table to read it; ot extract and ot auto to continue.
This repository packages github.com/onyphe/pyonyphe for the OTInstaller Registry as osintverse-community/onyphe. The tool is the work of its authors, under the MIT license; this repository only holds the manifest and release workflow.
Report problems with the tool upstream, and problems with the packaging here. If you maintain the upstream project and want to publish it yourself, open an issue or run ot claim osintverse-community/onyphe: the package is transferred to you.
The Dockerfile here installs the upstream release from PyPI at a pinned version, and the otinstaller release workflow builds, signs and publishes the image.
The image installs the cli extra (Typer and Rich), which the command needs and the plain wheel leaves out, so this is a Docker wrapper rather than a pipx one.
Runs pyonyphe summary ip, which prints ONYPHE's summary as JSON. Without ONYPHE_API_KEY the CLI says so on stderr and exits with code 2, which is what the registry's smoke test expects.
ot run osintverse-community/onyphe --ip …
Packaged version: 3.1.1.
onyphe finds ip, domain, organization, location, other. Tools that take those:
ip → 10 toolsdomain → 10 toolsorganization → 6 toolsot auto, with a saved result
Alternatives to onyphe that also take an ip address; ot auto runs every installed one on the same value.
Looks up who holds an IP address through RDAP: network, ASN, organisation and contacts
Lists an IP's open ports passively from Shodan InternetDB, without scanning it
Shows what Shodan has seen on an IP: open ports, services, banners, vulnerabilities, location
Looks up an IP address in GreyNoise to see whether it is internet background noise or a known benign service
Checks whether DNS resolvers answer correctly by comparing them with trusted resolvers on a test template