Threat Intel Look deeper. Find everything.

Threat Intelligence

Enrich findings with context from external providers. Bring-your-own-key model — Intreys never re-sells API access. Free tiers of every supported provider work out of the box.

Supported providers

ProviderWhat you getFree tier?
AbuseCH (URLhaus, ThreatFox, MalwareBazaar)Malicious URLs, IOCs, malware samplesYes (no key for URLhaus)
VirusTotalDomain / IP / hash / URL reputation, AV consensusYes (4 req/min)
GreyNoiseInternet-wide noise classification (benign / malicious / unknown)Yes (Community)
AlienVault OTXPulses, IOCs, indicator historyYes
ShodanOpen ports, banners, vulns on an IPYes (limited)
URLScan.ioURL submission, sandboxed render, screenshot, IOCsYes
CensysInternet asset search, certificate historyYes
SecurityTrailsDNS history, passive DNS, WHOISYes
SpurVPN/proxy/anonymizer attributionPaid only

Configuring API keys

  1. Sign up with each provider (free tiers fine for most workloads).
  2. Open Settings → API Keys.
  3. Paste each key into the corresponding field.
  4. Click Test next to each key — Intreys verifies the key works.

Keys are encrypted at rest using a key derived from your machine fingerprint.

How enrichment works

When you click an IP, domain, URL, or hash in any view, the right-rail enrichment panel queries every configured provider. Results are cached locally for 24 hours so you don’t burn rate limits on repeated lookups.

Rate limits and caching

Bulk enrichment

Pro+: select N indicators (Cmd/Ctrl-click in DPI), right-click → Enrich selection. Results land in a sortable table you can export to CSV.

Threat-intel feeds (offline / on-prem)

Mature security teams often want offline indicator matching against a curated feed. Intreys supports:

Feeds are matched in stage 15 (match_iocs) without any external API call. Useful for air-gapped environments.

Bring-your-own-key, no resale

Intreys never proxies your queries through our infrastructure and never re-sells provider access. Your key, your quota, your account. This means:

Privacy considerations

Some providers log lookups. Submitting a sensitive internal IP to a public TI provider may leak that IP existed and someone investigated it. Use the Sanitize toggle to redact RFC1918 and known-internal ranges before any external query.