Skip to main content

SecurityTrails::Domain - Data collection about a domain from SecurityTrails


Scraper Overview

SecurityTrails is the world's largest repository of historical DNS data Data for security companies, researchers, and teams that need to detail, find suspicious changes in DNS records, and prevent future fraudulent or criminal activity.

The functionality of A-Parser allows you to save parsing settings for future use (presets), set a parsing schedule, and much more. You can use automatic query multiplication, substitution of subqueries from files, iteration over alphanumeric combinations and lists to obtain the maximum possible number of results.

Saving results is possible in the form and structure that you need, thanks to the built-in powerful template engine Template Toolkit which allows you to apply additional logic to the results and output data in various formats, including JSON, SQL, and CSV.

Collected Data

  • Alexa rank
  • Apex domain
  • Host
  • Number of subdomains
  • A records
  • TXT records
  • AAAA records
  • Ns records
  • SOA records
  • MX records
  • CNAME records
  • CNAME records pointed here
  • MX records pointed here
  • NS records pointed here
  • Subdomains
  • historical A
  • historical AAAA
  • historical MX
  • historical NS
  • historical SOA
  • historical TXT





Choose the Mode section from which data is collected:





Use Cases

  • Obtaining subdomains and their Rank
  • Collecting information about the hosting provider of subdomains
  • Obtaining the mail provider of subdomains
  • Collecting history about A, AAAA, MX, NS, SOA, TXT
  • Collecting domain DNS records A, AAAA, MX, NS, SOA, TXT


As queries, it is necessary to specify domains, for example:

Output Results Examples

A-Parser supports flexible formatting of results thanks to the built-in template engine Template Toolkit, which allows it to output results in an arbitrary form, as well as in structured ones, for example CSV or JSON

Default Output

Result format:

$query - $alexa - $apex_domain

Example of result: - 1 -

Output Results for aRecords

Result format:

$aRecords.format('$ip, $stats\n')

Example of result:, 18037

Output Results for txt Records

Result format:


Example of result:

v=spf1 ~all

Output Results for aaaaRecords

Result format:

$aaaaRecords.format('$ip, $stats\n')

Example of result:

2607:f8b0:4004:82a::200e, 17294

Output Results for nsRecords

Result format:

$nsRecords.format('$ns, $stats\n')

Example of result:, 5226, 5233, 5268, 5298

Output Results for mxRecords

Result format:

$mxRecords.format('$p, $host, $stats\n')

Example of result:, 13227170, 10, 7665791, 50, 7726366, 40, 12894431, 30, 12975832, 20

Output Results for soaRecords

Result format:

$soaRecords.format('$ttl, $email, $stats\n')

Example of result:, 147485, 900

Output Results for soaRecords in CSV

Result format:

[% FOREACH soaRecords; 
tools.CSVline(ttl, email, stats);
END %]

Example of result:,147485,900

Output Information about Subdomains

Result format:

$subdomains.format('$domain, $alexa, $hosting, $mail\n')

Example of result:, 4, Google LLC, Google LLC, 11, Google LLC,, 18, Google LLC,, 22, Google LLC,, 24, Google LLC,, 27, Google LLC,, 36, Google LLC,, 40, Google LLC,, 44, Google LLC,, 47, Google LLC,, 57, Google LLC

Output Information about Subdomains in CSV Table

Result format:

[% FOREACH subdomains; 
tools.CSVline(domain, alexa, hosting, mail);
END %]

Example of result:,4,"Google LLC","Google LLC",11,"Google LLC",,18,"Google LLC",,22,"Google LLC",,24,"Google LLC",,27,"Google LLC",,36,"Google LLC",,40,"Google LLC"

Dump Results to JSON

Общий формат результата:

[% IF notFirst;
notFirst = 1;

obj = {};
obj.query = query;
obj.subdomains = [];

FOREACH item IN p1.subdomains;
domain = item.domain
alexa = item.alexa
hosting =
mail = item.mail

obj.json %]

Начальный текст:


Конечный текст:


Example of result:

"query": "",
"subdomains": [
"domain": "",
"mail": "Google LLC",
"hosting": "Google LLC",
"alexa": 4
"domain": "",
"mail": "",
"hosting": "Google LLC",
"alexa": 11
"domain": "",
"mail": "",
"hosting": "Google LLC",
"alexa": 18

To make the "Start text" and "End text" options available in the Task Editor, you need to activate "More options".

Possible Settings

ParameterDefault ValueDescription
ModeHistoryThe section of the website from which data is collected