SecurityTrails
May 28th, 2020 update commercialThe section your link pointed to isn't on SecurityTrails's page any more, so we've brought you to the top.
curl -X GET 'https://api.securitytrails.com/v1/company/example.com/associated-ips' -H 'APIKEY: your_api_key_here' curl \ --request GET \ --url 'https://api.securitytrails.com/v1/feeds/subdomains/type?apikey=YOURAPIKEY' \ --header 'accept: application/gzip' curl https://api.securitytrails.com/v1/domain/example.com/ssl?apikey=YOUR_API_KEY curl https://api.securitytrails.com/v1/ips/8.8.8.8/useragents?apikey=YOUR_API_KEY curl https://api.securitytrails.com/v1/ips/8.8.8.8/whois?apikey=YOUR_API_KEY
Summary
SecurityTrails is a commercial domain history service that indexes historical data for internet assets. It is accessed via a web interface and its functionality is suited for security researchers and threat intelligence teams. The service does not reference any specific comparable tools in its documentation. It has a history of 10 releases within the tracked timeframe, with the last update occurring 2293 days ago.
How SecurityTrails helps
Has this domain been pointed at different infrastructure in the past, even if the current records look clean?
pulls the historical record of DNS values for that domain and shows what it resolved to over time, not just the current answer
Which other domains share infrastructure or ownership traits with one I'm already investigating?
cross-references historical DNS and WHOIS data to surface other hostnames tied to the same IPs, name servers, or registration details
Did the ownership of this domain change hands recently?
compares historical WHOIS snapshots and flags differences in registrant, registrar, or contact details across time
What IP addresses has this hostname resolved to before it moved to its current one?
lists the chain of past resolutions in order, letting a researcher trace infrastructure moves rather than seeing only the present state
Is this subdomain something the organization actually set up, or could it be forgotten infrastructure?
searches indexed historical records for subdomains tied to the parent domain, revealing entries that may not appear in a live scan
Languages
Command line
4 commands for SecurityTrails, each with where it came from. This tool has no source analysis yet, so there is no option reference and no captured run beside them.
No command matches.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for SecurityTrails, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail SecurityTrails puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
9 entries
No entries match these filters.
- May 20202
- April 20202
- March 20202
- February 20202
- January 20201
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.