Securitytrails
for LuumenAI

Domain, DNS, and certificate intelligence, with asset rule changes held for approval

Ask about a domain and get its current DNS records, SSL certificate history, and the IP ranges tied to a company, without leaving the terminal. SecurityTrails connects with an API key. Reads come back right away. When you want to change the static asset rules on an attack surface project, the agent shows the rule set first and waits for your approval.

The Securitytrails toolbox

12 tools: 11 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet Company Associated IPsRetrieve IPs associated with a company domain.
  • ReadGet Domain DetailsRetrieves comprehensive domain information from SecurityTrails including current DNS records, infrastructure details, and statistics.
  • ReadGet Domain SSLFetch current and historical SSL certificate details for a hostname.
  • ReadIP Search StatisticsFetch aggregated statistics for IP addresses matching a DSL query.
  • ReadList ASI ProjectsList ASI projects available to the account.
  • ReadPingTest authentication and connectivity with the SecurityTrails API.
  • ReadScroll ResultsContinue scrolling through DSL search results.
  • ReadSearch IPsSearch IP addresses via SecurityTrails DSL.
  • ReadSQL API Execute QueryExecute SQL-like queries against SecurityTrails data.
  • ReadSQL API Scroll ResultsFetch next page of SQL query results.
  • ReadTemp Scrape Securitytrails UsageRetrieve account usage information from the SecurityTrails API.
  • WriteBulk Static Asset RulesBulk add or remove static asset rules for a SecurityTrails ASI project. Approval by default

One prompt, start to finish

What a governed Securitytrails run looks like inside Luumen.

Questions

How does LuumenAI connect to Securitytrails?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Securitytrails on its own?

Read actions answer immediately. Anything that writes — bulk static asset rules — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Securitytrails — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Securitytrails to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.