SecurityTrails StrawberryDomain details, historical dns and ips neighbors, worked for you
Hand a companion the outcome. It reads the SecurityTrails domain details, does the 3-operation version of the job, and stops for your click on anything that changes a record.
Open the domain detail. Check it against something else. Write the change. Move to the next one. That is the SecurityTrails afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing changed until you say so.
What it can do is exactly what SecurityTrails exposes to an account you authorise and nothing beyond it: 3 operations, 3 reads and no writes. In practice that means it can get ips neighbors, get historical DNS and get domain details, and work across the domain details, historical dns and ips neighbors.
The SecurityTrails API stops at SecurityTrails. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Where do the domain details come from?
All 3 operations read.
Your account, not a guess at it: a companion can get ips neighbors, get historical DNS and get domain details, and the full list below is the whole list, with nothing inferred from SecurityTrails's documentation.
The domain details are what most of this inventory is about, alongside the historical dns. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of SecurityTrails admin becomes a queue you review.
- Get IPs Neighbors
- Get Historical DNS
- Get Domain Details
How does a companion change a domain detail?
Through the screens you already use.
SecurityTrails exposes no write operation to a connected account, so a companion drives SecurityTrails in the session you are already signed into instead, filling the same forms you would to move a domain detail, and anything consequential stops for an approval card before it happens.
That is the ordinary case rather than the exception. Most of what a domain detail in SecurityTrails touches has no API pointed at it, and a companion is useful precisely because it does not need one.
What does the recurring domain details pass look like?
Yes.
Saved as a routine, the SecurityTrails domain details pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the infrastructure checks, the SecurityTrails domain details sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents