How do I feed it WHOIS data?

Collect first. A whois lookup writes the whois-file; asnmap resolves org or ASN to netblocks. Wire either into this node so it has records to match.

Does it look up ranges by itself?

No. It only verifies ownership of ranges you already collected. Upstream OSINT gathers the pile; this step keeps confirmed-owned CIDRs.

What should run after it?

A port scanner such as naabu or nmap on the confirmed ranges, so open-port discovery stays on org-owned hosts.

How does it differ from asnmap?

asnmap discovers ASN and CIDR mappings. whois-verify-targets filters an existing whois-file against target-org and does not expand netblocks on its own.

Updated Jul 14, 2026

Utilities

Confirm WHOIS ranges belong to the target org

Confirm target-org owns the ranges in a whois-file.

Confirm IP ownership before scanning Scope an engagement cleanly Seed a port-scan workflow

overview

What whois-verify-targets does

Sit this node after a WHOIS or ASN collector and before a port scanner. It takes target-org plus a whois-file and emits only the IP ranges that match the organization you named.

Reach for it when scope is noisy: a string match in WHOIS can pull hosting-provider or unrelated netblocks. Ownership checks keep scans inside authorized address space.

Unlike asnmap or a raw whois lookup, this step does not discover ranges. Feed it collected records; hand confirmed CIDRs to naabu or nmap.

use cases

Where whois-verify-targets fits

Confirm IP ownership before scanning

Match WHOIS records to the target organization so only verified, owned IP ranges flow into the next scanning stage.

Scope an engagement cleanly

Filter out ranges that share a name but belong to a hosting provider or third party, keeping the assessment inside authorized address space.

Seed a port-scan workflow

Hand the verified ranges to a scanner such as naabu or nmap so port discovery runs against confirmed-owned hosts.

Attribute discovered hosts to an org

Tie found hosts back to the organization that owns the range, so external asset-discovery findings carry clear ownership for reporting.

reference

whois-verify-targets inputs and flags

2 inputs

Name	Type	Flag	Description
target-org	STRING	·	Organization name to verify ownership against.
whois-file	FILE	·	WHOIS data file the verification reads its ranges from.

Showing key inputs. whois-verify-targets exposes 2 inputs in total.

example

Run whois-verify-targets

whois-verify-targets · command

# confirm Example Corp owns the IP ranges in the collected WHOIS datawhois-verify-targets 'Example Corp' whois.txt

sample output

[+] target organization: Example Corp[+] parsed 7 netblocks from whois.txt[+] verified 4 ranges owned by Example Corp198.51.100.0/24198.51.100.0/25203.0.113.0/24203.0.113.0/25[-] skipped 3 ranges (registered to hosting providers)

guidance

Choosing whois-verify-targets

Use after a WHOIS or ASN collect and before scanning, when you must prove target-org owns the ranges in whois-file. Pair with asnmap or whois upstream; this node only filters ownership.

asnmap

Maps org or ASN to CIDRs. Run upstream to gather ranges this tool verifies.

whois

Forward WHOIS that produces the whois-file this node consumes.

amass

Broader OSINT that can surface org-linked netblocks during attack-surface mapping.

faq

whois-verify-targets questions

WHOIS name matches often include provider or third-party ranges. Scanning those falls outside scope. Filtering with target-org first keeps the port scan on authorized space.

Run whois-verify-targets yourself

An organization name and a WHOIS file feed whois-verify-targets, which returns the confirmed-owned IP ranges as a queryable output.

Run whois-verify-targets in Trickest Browse the library

Facts on this page come from the live Trickest tool library.