ACTION_ID: company_asn_lookup NAME: HackerTarget: ASN Lookup CATEGORY: Company Enrichment CREDITS: 1 Find the Autonomous System Numbers registered to a company name, returning each ASN with its registered organization and description. The entry point to IP-based account intelligence. 1. INPUTS company_name (type: string, optional) Company Name 2. OUTPUTS total_asns (number) — ASNs asns (structured_array) Columns — reference as {{.asns.}}: asn (string) — Autonomous System Number company_name (string) — Company Name organization (string) — Organization asn_description (string) — ASN Description company_domain (string) — Company Domain 3. HOW TO CONFIGURE Configure Action body: { "inputs": { "company_name": "{{input.company_name}}" } } Field-by-field: - company_name The name to match against ASN registration records. Use the legal entity name where you have it — registrations rarely use the trading name. 4. KEY NOTES - ASN registrations use legal entity names, so a trading name often misses. Try the legal name from `floqer_company_firmographics` when the first lookup returns zero. - Only organisations large enough to hold their own address space appear here. Most SMBs have no ASN at all — a zero result is normal, not an error. - `asns` is a `structured_array`; its `asn` column feeds `company_ip_data_waterfall`'s ASN input. - This action takes no domain input — it matches on name only. 5. WHERE IT FITS IN A WORKFLOW Pattern: company_asn_lookup -> filter (total_asns greater than 0) -> company_ip_data_waterfall (asn wired from the list) for full IP-holdings enrichment. 6. WHEN TO USE Use company_asn_lookup as the first step of IP-based account intelligence, or as a crude proxy for infrastructure scale. 7. WHEN NOT TO USE Need IP holdings across several providers with fallback -> action-detail/company_ip_data_waterfall.txt Need a single-provider IP-holdings lookup -> action-detail/company_ip_resources_lookup.txt Last updated: 2026-08-03.