AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node integrates with the AvantGuard DNSFilter API to test URLs against specific URL filtering policies. It allows users to verify whether a given URL is allowed or blocked according to a particular policy defined in the DNSFilter system. This is useful for security teams or network administrators who want to programmatically check URL access permissions based on their organization's filtering rules.

Practical examples include:

  • Automatically validating URLs before allowing them through a proxy or firewall.
  • Integrating URL filtering checks into automated workflows for incident response.
  • Testing new or updated policies by verifying URLs against them without manual intervention.

Properties

Name Meaning
Policy Id The numeric identifier of the URL filtering policy to test the URL against.
Url The URL string that you want to test against the specified policy.

Output

The node outputs JSON data representing the result of the URL filter test. This typically includes information about whether the URL is allowed or blocked under the specified policy, along with any relevant metadata returned by the DNSFilter API. The exact structure depends on the API response but generally contains status and reason fields indicating the filtering decision.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard DNSFilter API.
  • The node sends requests to https://api.dnsfilter.com.
  • Proper configuration of the API authentication credential within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Providing an incorrect or non-existent Policy Id may result in errors or empty results.
    • Malformed URLs or unsupported URL formats might lead to request failures.
  • Error messages:

    • Authentication failures usually indicate invalid API keys; ensure the correct key is configured.
    • "Policy not found" or similar errors suggest the Policy Id does not exist or is inaccessible.
    • Network errors could be due to connectivity issues or API downtime.

To resolve these, verify API credentials, confirm the Policy Id is valid, and ensure the URL format is correct.

Links and References

Discussion