SecurityTrails API

42 D

Metadata Score Metadata estimate · not endpoint-tested

Visit Official Site Compare Alternatives

Overview

SecurityTrails provides detailed DNS and WHOIS history for domains and IP addresses, letting you trace how a domain's configuration has changed over time. You can look up current and historical A records, MX records, nameservers, and registration data. It's valuable for threat hunting, domain investigations, and competitive research.

Beginner Tip

Start with the /v1/domain/{hostname} endpoint to get a quick snapshot of any domain's current DNS records and WHOIS data in one call.

Available Data

The kind of data this API exposes, based on its documentation. We could not call the endpoint to confirm the exact field names.

IP address information

geographic location

ASN and ISP data

Example Response

Illustrative shape only — we were not able to call this endpoint (it requires credentials or exposes no public sample URL), so the fields below show the kind of data this API returns rather than a recorded response.

JSON Response · Illustrative

{
  "route": "Line 1",
  "origin": "Station A",
  "destination": "Station B",
  "departure": "08:30",
  "arrival": "09:15",
  "status": "On Time",
  "delays_min": 0
}

Field Reference

hostname The domain name that was queried.

current_dns Present DNS records grouped by type (a, aaaa, mx, ns, soa, txt).

current_dns.a.values List of current A record IP addresses for the domain.

alexa_rank Domain popularity rank (if available).

apex_domain The root domain, useful when you query a subdomain.

subdomain_count Number of known subdomains discovered for this domain.

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request

const url = "https://api.securitytrails.com/v1/domain/google.com";
// Replace headers or query params with the values required by this API.
const response = await fetch(url, {
  headers: {
  "X-API-Key": "YOUR_API_KEY"
  }
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

401 Unauthorized The API key is missing or passed in the wrong header.

✓ SecurityTrails uses the APIKEY header (not Authorization) — ensure it is set correctly in every request.

429 Rate Limit Exceeded Free plans have strict monthly quota limits.

✓ Cache responses for domains you check frequently, and check your usage at securitytrails.com/app/account/usage.

Empty results for some DNS record types Not all domains have all record types (e.g., MX, TXT may be absent).

✓ Check the type field in the response to confirm which record types are present before accessing nested data.

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

How is this scored? →