Domain search modifiers
Google Threat Intelligence allows you to perform advanced faceted searches over the historical collection of domains seen by Google Threat Intelligence. These searches can act on basically all the metadata generated for domains: categories, popularity ranks, SSL certificates, Whois lookup, resolutions, detections, relationships, etc. For example, you can pivot on the registrant (Whois) of a given domain to try to identify other network infrastructure set up by a given adversary.
Google Threat Intelligence searches by default over the historical collection of files, in order to search over domains you need to add the facet condition entity:domain. For example, let's ask for all those domains that have been detected by more than 5 blocklists and were created after February 10th 2020:
entity:domain positives:5+ creation_date:2020-02-10+
You can click on the filter icon inside the main search box in order to navigate to a domain search assistant:
Note that the assistant will not allow you to build complex searches combining AND, OR and NOT conditions. For example:
(entity:domain positives:5+ creation_date:2020-02-10+) AND (domain:*chase* OR domain:*paypal*)
The following table describes all the search modifiers (facets) that can be used, you can combine any number of them:
| Modifier | Description |
|---|---|
| domain | Search for domains containing a word or fulltext sequence. Accepts wildcard notation. Examples: entity:domain domain:chase p:5+, entity:domain domain:"*chase*" p:5+ |
| tld | Fix a condition based on the domain's TLD. Example: entity:domain tld:ru |
| depth | Fix a condition on how many levels the domains matching your search should have. Accepts less than and greater than syntax. Example: entity:domain p:5+ depth:3+ depth:7- |
| a_record a | Search for domains that resolve to a given IP address (range). Note that this is not the recommended way to leverage Google Threat Intelligence passive DNS data, if you want to know all domains observed behind a given IP address you should be looking up such IP address in Google Threat Intelligence, making use of the relations tab. This modifier should only be used for IP address ranges. Example: entity:domain a_record:"127.0.0.1/24" |
| a_ttl a_record_ttl | Search for domains whose resolution have a given TTL, accepts less than and greater than syntax. This can be useful in identifying fast flux. Example: entity:domain a_record_ttl:1+ a_record_ttl:5- category:malware |
| aaaa aaaa_record | Same as a_record but for IPv6. Please refer to the a_record description. |
| aaaa_ttl aaaa_record_ttl | Same as a_record_ttl but for IPv6, please refer to the aforementioned description. |
| caa caa_record | DNS Certification Authority Authorization is an Internet security policy mechanism which allows domain name holders to indicate to certificate authorities whether they are authorized to issue digital certificates for a particular domain name. This modifier allows you to search for any word or phrase contained in the DNS CAA record. Example: entity:domain caa_record:google |
| cname cname_record | CNAME is a Canonical Name Record or Alias Record. A type of resource record in the Domain Name System (DNS), that specifies that one domain name is an alias of another canonical domain name. This modifier allows you to search for any word or phrase contained in the DNS CNAME record. Example: entity:domain cname:appspot.com |
| cname_ttl cname_record_ttl | Same as a_record_ttl but for the CNAME DNS record. |
| dname dname_record | DNS record to perform redirection at the DNS level. This modifier allows you to search for any word or phrase contained in DNAME records. Example: entity:domain dname:"apple.com" |
| dname_ttl dname_record_ttl | Same as a_record_ttl but for the DNAME DNS record. |
| mx mx_record | An MX record is used to tell the world which mail servers accept incoming mail for your domain and where emails sent to your domain should be routed to. This modifier allows you to search for any word or phrase contained in MX records. Example: entity:domain mx_record:"francedns.com" |
| mx_ttl mx_record_ttl | Same as a_record_ttl but for the MX DNS record. |
| ns ns_record | DNS NS records indicate which DNS server is authoritative for that domain (which server contains the actual DNS records). This modifier allows you to search for any word or phrase contained in an NS record. Example: entity:domain ns_record:ekiptech.com |
| ns_ttl ns_record_ttl | Same as a_record_ttl but for the NS DNS record. |
| soa soa_record | A Start of Authority DNS record is a type of resource record in the Domain Name System containing administrative information about the zone, especially regarding zone transfers. This modifier allows you to search for any word or phrase contained in domain SOA records. Example: entity:domain soa_record:google.com |
| txt txt_record | A TXT record is a type of DNS resource record used to provide the ability to associate arbitrary text with a host or other name, such as human readable information about a server, network, data center, or other accounting information. Example: entity:domain txt_record:"topdns.com" |
| txt_ttl txt_record_ttl | Same as a_record_ttl but for TXT DNS record. |
| ttl | Focus on domains that have at least one DNS record TTL matching your criteria. Accepts less than and greater than syntax. Example: entity:domain ttl:1+ ttl:5- |
| category | Filter domains according to their content category, as displayed in the details section of a domain report. Example: entity:domain category:"malware command and control" |
| comment | Search for domains that have a Google Threat Intelligence Community comment containing the word or phrase provided. Example: entity:domain comment:phishing |
| comment_author | Search for domains that have been commented by the user with the username provided. Example: entity:domain comment_author:hugoklugman |
| creation_date | Filter domains based on the creation date as reported by the registration details. Accepts less than and greater than syntax. Examples: entity:domain creation_date:2020-02-10+, entity:domain creation_date:2020-02-10-, entity:domain creation_date:3d- |
| last_update_date | Filter domains based on the latest registration update. Accepts less than and greater than syntax. Examples: entity:domain p:5+ last_update_date:2020-02-10+, entity:domain last_update_date:3d- |
| main_icon_dhash | Search for domains with a favicon which is visually similar to another favicon, a visual similarity hash is used for this purpose. This search can be triggered by clicking on the favicon preview of the domain in the search listings. Can be useful to discover phishing sites targeting a given company. However, note that this search will work better for URL entities, as phishing kits are often deployed and subpaths and hence the favicon will not be globally tied to the bare domain. Example: entity:domain main_icon_dhash:"cc8cccccaae070b2" NOT domain:"dropbox.com" NOT domain:"dropboxforum.com" |
| popularity_rank | Filter domains according to their popularity rank. Accepts less than and greater than syntax. A popularity rank of 1 means that it is the most popular domain as reported by one of the ranks aggregated. Example: entity:domain popularity_rank:10- |
| p positives | Filter domains according to the number of engines/blocklists that detect them. Less than and greater than syntax is allowed. Examples: entity:domain p:5+ |
| engines | Focus on domains that have a given detection label by at least one blocklist/scanner. Example: entity:domain engines:phishing |
| <engine name> | Focus on domains that are detected with a given label by a given blocklist/scanner. Example: entity:domain fortinet:malware |
| reputation | Filter domains according to their reputation among the Google Threat Intelligence user base. Example: entity:domain reputation:-20- |
| detected_communicating_files_count | Fix a condition based on how many detected files have been seen contacting the given domain when executed in a sandbox. Less than and greater than syntax is allowed but the count saturates at 100. Example: entity:domain detected_communicating_files_count:5+ |
| communicating_files_max_detections | Fix a condition based on the maximum number of detections observed for files that communicate with a given domain. Example: entity:domain communicating_files_max_detections:30+ detected_communicating_files_count:5+ |
| detected_downloaded_files_count | Fix a condition based on how many detected files Google Threat Intelligence has downloaded from a URL hosted under a given domain. Example: entity:domain detected_downloaded_files_count:10+ |
| downloaded_files_max_detections | Fix a condition based on the maximum number of detections observed for files that were downloaded by Google Threat Intelligence from a given domain. Example: entity:domain downloaded_files_max_detections:20+ |
| detected_referring_files_count | Fix a condition based on how many detected files have been seen containing the given domain in their strings. Example: entity:domain detected_referring_files_count:10+ |
| referring_files_max_detections | Fix a condition based on the maximum number of detections observed for files that contain a given domain in their strings. Example: entity:domain referring_files_max_detections:30+ detected_referring_files_count:10+ |
| detected_urls_count | Fix a condition based on how many detected URLs have been seen hosted under a given domain. Example: entity:domain detected_urls_count:10+ |
| urls_max_detections | Fix a condition based on the maximum number of detections observed for URLs hosted under a given domain. Example: entity:domain urls_max_detections:5+ detected_urls_count:10+ |
| tag | Filter domains according to their tags. Example: entity:domain tag:dga category:bot List of available tags: - dga: bigram frequency analysis suggests that this could be an algorithmically generated domain. - hex: domain name contains a long hex character sequence, often used in rock phish campaigns. - non-ascii: domain name contains non-ascii characters, e.g. punycode. - dynamic-dns: domain set up with a dynamic DNS provider. - nxdomain: domain that cannot be resolved to an IP Address. |
| registrar | Filter domains according to the entity in which they were registered. This is a narrow search with respect to the broader whois search described below Example: entity:domain registrar:markmonitor |
| ssl_issuer | Focus on domains that contain a given string or fulltext pattern within their SSL certificate issuer field. Example: entity:domain ssl_issuer:"DigiCert Baltimore CA-2 G2" |
| ssl_serial | Focus on domains that share a given SSL certificate serial field. Example: entity:domain ssl_serial:"4648f925c65eea8795a81cfe87d971e" |
| ssl_subject | Focus on domains that contain a given string or fulltext pattern within their subject field. Example: entity:domain ssl_subject:"*.s3.amazonaws.com" |
| ssl_thumbprint | Focus on domains sharing a given SSL certificate thumbprint field. Example: entity:domain ssl_thumbprint:"17e0a93e58af0a068d6c2db6c180b3e7e352d48e" |
| whois | Filter domains according to any word or phrase contained within their Whois record, as redacted by Google Threat Intelligence to respect personal information. Example: entity:domain whois:"1ecd1739ef269eacs@" |
| have | Allows you to fix a condition that the domain’s indexed metadata should meet, it accepts any of the modifiers above and it means that the domain should have data for a given modifier. Example: entity:domain p:3+ have:whois |
| last_modification_date lm | Filter Domains based on the latest update on Google Threat Intelligence for Domain. Example: entity:domain last_modification_date:3d+ |
| jarm | Filter Domains based on the JARM fingerprint. Example: entity:domain jarm:29d3fd00029d29d21c42d43d00041d188e8965256b2536432a9bd447ae607f |
| parent_domain | Filter Domains based on the parent Domain. Example:entity:domain parent_domain:dropbox.com |
| domain_regex | Search for domains using a regular expression. Example: entity:domain domain_regex:"[b-y]{12}.(biz|pw|space|us)" |
| fuzzy_domain | Search for fuzzy domains. Example: entity:domain fuzzy_domain:www.santander.com not domain:www.santander.com |
| ssl_not_before | Filter Domains based on the start date of the last SSL certificates' validity. Example: entity:domain ssl_not_before:2023-10-01 |
| ssl_not_after | Filter Domains based on the end date of the last SSL certificates' validity. Example: entity:domain ssl_not_after:2023-10-01 |
| threat_actor related_actor | Searches for IoCs which have that related threat actor. Example: entity:domain threat_actor:"Lazarus Group" |
| gti_score | Google Threat Intelligence assessment threat score. Example: entity:domain gti_score:30+" |
| gti_severity | Google Threat Intelligence assessment severity of the IOC. Example: entity:domain gti_severity:high" |
| gti_verdict | Google Threat Intelligence assessment verdict of the IOC. Example: entity:domain gti_verdict:benign" |
| attribution | Filter Domains by malware family based on the verdicts provided by the data sources available in VirusTotal. Attribution can be of 3 types: malwares , actors or campaigns Example: entity:domain attribution:emotet |
Updated 22 days ago