DNSFilter icon

DNSFilter

**Note:** If you are a distributor integrating with DNSFilter, please check out our [Distributors Development Guide](/docs/distributors).### Authentication- Authentication is required for most, but not all, endpoints.- Authentication is done by setting the `Authorization` request header. The header value is the API key itself. For example: `Authorization: eyJ...`- An API key can be obtained through the DNSFilter dashboard under Account Settings. For additional information see [this KB article](https://help.dnsfilter.com/hc/en-us/articles/21169189058323-API-Tokens).### Rate Limiting- All endpoints are rate limited.- The limits may vary by endpoint, but are generally consistent.- When the rate limit is exceeded the API will return the standard `429` HTTP status.- The following headers will also be provided in the response: `Retry-After`, `RateLimit-Policy`, `RateLimit`, `RateLimit-Limit`, `RateLimit-Remaining`, `RateLimit-Reset`. For details on the values of these headers, see the following articles [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Retry-After), [here](https://www.ietf.org/archive/id/draft-ietf-httpapi-ratelimit-headers-08.html), and [here](https://www.ietf.org/archive/id/draft-polli-ratelimit-headers-05.html).- For additional information see [this KB article](https://help.dnsfilter.com/hc/en-us/articles/38202811088403-API-Rate-Limits).### Error Handling- The API uses standard HTTP status codes to indicate success or failure.- For _V1_ endpoints the response format is: ```json { "error": "string", "type": "string(optional)" } ```- For _V2_ endpoints the response format is: ```json { "error": { "message": "string", "type": "string(optional)" } } ```### PaginationFor the _V1_ endpoints, the pagination parameters are nested. That is to say,if passed as JSON they look like this: `{"page[number]": 1, "page[size]": 10}`.To pass this information in the URL query string, it would be formatted likethis: `...?page%5Bnumber%5D=1&page%5Bsize%5D=10`.In this guide, the UI will indicate that `page` is an `object` and if youwant to set values when trying the request, you must enter it as if it wasthe JSON above.### A Quick ExampleThe following will return information about the currentlyauthenticated user.```bash% curl -H 'Authorization: ***' https://api.dnsfilter.com/v1/users/self{ "data": { "id": "12345", "type": "users", "attributes": { "name": "John Doe", "email": "john@example.com", ...additional fields...}}}```

Actions328

Overview

This node performs bulk lookup operations on domains using the DNSFilter API. It allows users to retrieve domain and category information for multiple fully qualified domain names (FQDNs) in a single request. This is useful for scenarios where you need to analyze or categorize a list of domains efficiently, such as in security monitoring, threat analysis, or network filtering.

Use Case Examples

  1. A security analyst wants to check the categories of multiple suspicious domains to determine their threat level.
  2. A network administrator needs to bulk lookup domain information to update firewall or filtering rules based on domain categories.

Properties

Name Meaning
Return All Whether to return all results or only a single page. When disabled, no pagination parameters are sent and only one page of results is returned.
Additional Fields Additional optional fields for the bulk lookup operation, including a comma separated list of FQDNs to lookup.
Options Additional options such as custom request body, headers, query filters, batching settings, debug mode, pagination settings, and timeout.

Output

JSON

  • json - The JSON response from the DNSFilter API containing domain and category information for the specified FQDNs.

Dependencies

  • DNSFilter API key credential

Troubleshooting

  • Ensure the DNSFilter API key is correctly configured and has the necessary permissions.
  • Check that the FQDNs provided in the 'Fqdns' field are valid and properly formatted.
  • If using batching, adjust the batch size and interval to avoid hitting rate limits.
  • Enable debug mode to see detailed request and response information for troubleshooting.
  • Handle API rate limiting errors (HTTP 429) by respecting the 'Retry-After' header and adjusting request frequency.

Links

Discussion