Agent recipe · Procurement, security, and due-diligence teams
Vet a vendor's domain before you sign
Find out who registered a supplier's domain, what else they own, and which staff addresses are public, before a contract or a payment.
Paste into your AI app
Use OSINTverse to vet the domain <vendor-domain.com> for a new supplier. Budget $3. Quote first, then tell me who registered it and when, what other domains share their details, its DNS and hosting history, and which staff email addresses are public. File it in a case called "Vendor check".Swap the part in angle brackets. Needs the OSINTverse MCP server connected (how to connect). In sandbox mode it runs on sample data for free.
What your AI does
quote_bulk_search: Prices the three lookups and checks the wallet and your daily cap.create_case: Opens a case so the results stay together.run_bulk_search: Runs WHOIS history, DNS history, and the email finder in one call.get_search: Reads each result, or its summary, to write the answer.
What it costs
One lookup per source at today's prices, about $0.85 in total. Your AI quotes the exact price before it spends anything, and every charge counts toward the daily cap you set.
- Whoxy$0.15
- SecurityTrails$0.50
- Hunter.io$0.20
A sample answer
Illustrative only: real answers depend on what the sources return.
Registered in 2016 through a privacy service; the registrant email also appears on 4 other domains, two of them parked. DNS moved hosting providers twice, last in 2024. Hunter lists 6 public staff addresses in first.last format. Nothing here proves wrongdoing; the shared registrant details are worth asking the supplier about.
Good to know
- Registrant details are often hidden by privacy services; history can still show who registered it before.
- Shared registrant details mean the same contact appears, not that the same company owns everything.
- Use OSINTverse only for lawful investigations you are entitled to run.