SecurityTrails

Install corsair and @corsair-dev/securitytrails, add the SecurityTrails plugin, and connect with an API key. Then call methods like corsair.securitytrails.api.account.ping() from your app. Corsair syncs data per tenant.

Yes. SecurityTrails requires an API key from your SecurityTrails account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit SecurityTrails, GitHub, Notion, Stripe, and the rest. Trigger SecurityTrails from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for dns and domain intelligence api for historical records, subdomains, and security research. Common builds include sync jobs, admin tooling, and agents that call SecurityTrails APIs from your backend. Local DB entities let you query synced SecurityTrails records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per SecurityTrails API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/securitytrails in the open repo. When SecurityTrails ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your SecurityTrails data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store SecurityTrails data on your behalf.