asnmap

asnmap requires Go 1.21 or later. You can install it using go install or by downloading pre-compiled binaries from the GitHub releases page.

go install github.com/projectdiscovery/asnmap/cmd/asnmap@latest

asnmap can take various input types to resolve CIDR ranges. It supports single values, multiple comma-separated values, or reading from a file. It also supports STDIN for piping data.

Supported input types:

• ASN: e.g., AS14421
• DNS/Domain: e.g., example.com
• IP: e.g., 93.184.216.34
• ORG: e.g., GOOGLE

# Using specific flags
asnmap -a AS45596 -silent
asnmap -i 100.19.12.21 -silent
asnmap -d hackerone.com -silent
asnmap -org GOOGLE -silent

# Using STDIN
echo GOOGLE | ./asnmap -silent

Since asnmap supports STDIN and provides CIDR ranges, its output can be piped directly into other ProjectDiscovery tools to expand attack surfaces.

Common patterns include:

• Piping CIDRs to tlsx for TLS inspection.
• Piping CIDRs to dnsx for DNS resolution.
• Piping CIDRs to naabu for port scanning.
• Piping naabu results into httpx or nuclei.

echo AS54115 | asnmap | naabu -p 443 | httpx | nuclei -id tech-detect

The ASNMap CLI requires an API Token from the ProjectDiscovery Cloud Platform. You can authenticate using one of two methods:

1. Environment Variable: Set the PDCP_API_KEY variable.
2. Interactive Auth: Run the -auth flag to enter your key manually.

# Method 1: Environment Variable
export PDCP_API_KEY=*************

# Method 2: Interactive
asnmap -auth

The asnmap client requires an API key to interact with the ProjectDiscovery cloud API.

Authentication Methods:

1. Environment Variable: Set the PDCP_API_KEY environment variable. This is the recommended method for programmatic use.
2. Credential Handler: The client automatically attempts to retrieve credentials using the pdcp.PDCPCredHandler during initialization.

Errors:

• If the API key is missing or invalid, the client returns ErrUnAuthorized (which corresponds to a 401 Unauthorized HTTP status).

# Set the API key in your environment
export PDCP_API_KEY="your_api_key_here"

Use the -csv flag to output data in a pipe-delimited CSV format. The fields included are timestamp|input|as_number|as_name|as_country|as_range.

echo hackerone.com | ./asnmap -csv -silent

For automation and post-processing, use the -json flag. This returns a structured JSON object containing the timestamp, input, ASN number, ASN name, country, and an array of CIDR ranges.

echo hackerone.com | ./asnmap -json -silent | jq

To use asnmap as a library, initialize a new Client using NewClient(). The client automatically determines the base server URL from the SERVER_URL environment variable or defaults to https://asn.projectdiscovery.io/. The client is configured to ignore expired SSL certificates by default.

Note: You must provide a valid API key via the PDCP_API_KEY environment variable or through the ProjectDiscovery credential handler for requests to succeed.

package main

import (
	"fmt"
	"github.com/projectdiscovery/asnmap"
)

func main() {
	client, err := asnmap.NewClient()
	if err != nil {
		panic(err)
	}
	fmt.Printf("Client initialized: %+v\n", client)
}

The GetData method is the primary way to perform ASN, IP, or Organization lookups. It automatically identifies the input type (ASN, ASNID, IP, or Org) and constructs the appropriate API request.

Input Types Supported:

• ASN: e.g., AS1234 (the method will strip the as prefix internally).
• ASNID: e.g., 1234.
• IP: e.g., 8.8.8.8.
• Org: e.g., Google.

Parameters:

• input string: The value to query.
• medatadas ...string: Optional metadata parameters (variadic).

Returns:

• []*Response: A slice of response objects containing the lookup results.
• error: An error if the input type is unknown, the request fails, or the API returns an error (e.g., ErrUnAuthorized).

// Example: Lookup an IP
results, err := client.GetData("8.8.8.8")
if err != nil {
	// handle error
}

// Example: Lookup an ASN
results, err := client.GetData("AS15169")

You can route asnmap client requests through a proxy using the SetProxy method. This method supports both direct proxy strings and proxy lists (which can include file paths).

Supported Proxy Schemes:

• http / https
• socks5

Usage Patterns:

1. Single Proxy String: Pass a URL-formatted proxy string.
2. Proxy List/File: Pass a slice of strings. If a string is a valid file path, the client will read the file and attempt to use the first valid proxy found within it.

If no valid proxy can be established, SetProxy returns an error.

// Using a single proxy string
_, err := client.SetProxy([]string{"http://proxy.example.com:8080"})

// Using a file containing a list of proxies
_, err := client.SetProxy([]string{"/path/to/proxies.txt"})

If you need the Input field in the returned Response objects to match a specific string rather than the automatically identified input, use GetDataWithCustomInput. This is useful when you want to preserve the exact formatting of your original query in the results.

// The 'inputToUseInResponse' will be assigned to the 'Input' field of every result
results, err := client.GetDataWithCustomInput("AS15169", "google_asn")