For Agents
Configure DNS security profiles, manage blocklists and allowlists, track threat analytics, and monitor DNS queries in real-time.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the , or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with API.
Create and manage DNS security profiles with custom threat protection rules
Configure blocklists and allowlists for domain-level access control
Enable threat intelligence feeds for malware, phishing, and cryptojacking detection
Set up parental control policies with content category filtering and SafeSearch enforcement
GET STARTED
Use for: I need to block a malicious domain across all devices, Check whether a specific domain is being blocked by security policies, List all DNS queries that were blocked in the last 24 hours, I want to enable parental controls for a device profile
Not supported: Does not handle upstream DNS resolution, certificate management, or VPN services — use for DNS filtering policy configuration only.
NextDNS API enables programmatic control of DNS security profiles, privacy filters, and parental controls for network-level threat protection. Configure blocklists, allowlists, security policies, and privacy settings across DNS profiles, then monitor queries through real-time analytics and historical logs. Track blocked threats, analyze domain patterns, and enforce content filtering policies for devices and networks.
Track DNS query analytics by status, domain, device, protocol, and geographic destination
Monitor real-time DNS logs via Server-Sent Events with filtering by status and device
Configure privacy blocklists to block trackers and native tracking protection
Patterns agents use API for, with concrete tasks.
★ Network-Wide Malware Protection
Deploy DNS-level threat protection to block malware, phishing, cryptojacking, and ransomware domains before they reach endpoints. NextDNS analyzes DNS queries against threat intelligence feeds and AI-powered detection, automatically blocking suspicious domains. Supports customizable security policies across thousands of devices with per-profile configuration. Typical deployment protects an entire network in under 30 minutes by updating DNS settings.
Enable threat intelligence feeds and AI threat detection for profile abc123, then retrieve blocked threat domains from the last 7 days
Privacy-Focused DNS Filtering
Block trackers, advertising domains, and native tracking mechanisms across all devices at the DNS layer. NextDNS provides curated privacy blocklists covering ad networks, analytics trackers, and disguised tracking techniques like CNAME cloaking. Configure per-profile policies with allowlist exceptions for required services. Integration requires no client-side software changes — only DNS resolver configuration. Typical setup filters 30-50% of tracking requests immediately.
Add privacy blocklists oisd and energized to profile abc123, then retrieve analytics showing the percentage of blocked tracker queries
Parental Control and Content Filtering
Enforce content policies for homes, schools, or organizations by blocking categories like adult content, gambling, social media, or streaming services. NextDNS supports granular category controls, SafeSearch enforcement for search engines, and YouTube Restricted Mode activation via DNS. Policies apply instantly across all connected devices without requiring endpoint agents. Monitor compliance through detailed logs showing blocked content attempts by device and timestamp.
Enable parental control categories for adult content and gambling on profile abc123, activate SafeSearch, and list all blocked attempts in the last 24 hours
DNS Query Monitoring and Threat Intelligence
Analyze DNS traffic patterns to detect compromised devices, data exfiltration attempts, or command-and-control communication. NextDNS logs all queries with status (allowed, blocked, default), encryption protocol, device information, and geographic destination. Analytics endpoints provide aggregated views by domain, IP, query type, and block reason. Real-time streaming via Server-Sent Events enables immediate threat response. Logs retain for configurable periods with privacy options to drop IP or domain data.
Stream real-time DNS logs for profile abc123 filtered by status=blocked, analyze the top 10 blocked domains, and identify any DGA (domain generation algorithm) patterns
AI Agent DNS Security Automation
AI agents integrate with NextDNS through Jentic to automate threat response workflows. An agent monitoring security alerts searches Jentic for 'block malicious domain', loads the NextDNS denylist schema, and executes the block within seconds — no manual policy updates required. Agents can correlate threat intelligence feeds with DNS logs, automatically add high-confidence threats to denylists, and generate reports on blocked attack attempts. Through Jentic, agents access NextDNS operations via natural language intent rather than endpoint documentation.
Search Jentic for 'block a malicious domain', load the NextDNS add_denylist operation, and execute it to block example-malware.com on profile abc123
36 endpoints — nextdns api enables programmatic control of dns security profiles, privacy filters, and parental controls for network-level threat protection.
METHOD
PATH
DESCRIPTION
/profiles
List all DNS profiles
/profiles
Create a new DNS profile
/profiles/{profileId}/security
Update security settings for threat protection
/profiles/{profileId}/denylist
Add domain to blocklist
/profiles/{profileId}/analytics/domains
Retrieve domain query analytics
/profiles/{profileId}/logs
Fetch DNS query logs with filtering
/profiles/{profileId}/logs/stream
Stream real-time DNS query events via SSE
/profiles
List all DNS profiles
/profiles
Create a new DNS profile
/profiles/{profileId}/security
Update security settings for threat protection
/profiles/{profileId}/denylist
Add domain to blocklist
/profiles/{profileId}/analytics/domains
Retrieve domain query analytics
Three things that make agents converge on Jentic-routed access.
Credential isolation
NextDNS API keys are stored encrypted in the Jentic vault. Agents receive scoped access tokens — raw API keys never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'block a malicious domain') and Jentic returns matching NextDNS operations with their input schemas, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct NextDNS integration: 1-3 days for auth, profile management, and log parsing. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Cloudflare API
Enterprise DNS management with DDoS protection and CDN — broader infrastructure scope
Choose Cloudflare for full-stack DNS, CDN, and firewall control. Choose NextDNS for focused DNS security and content filtering without infrastructure management.
ClouDNS API
Managed DNS hosting with GeoDNS and DNSSEC — optimized for DNS hosting providers
Choose ClouDNS for authoritative DNS hosting and GeoDNS routing. Choose NextDNS for recursive DNS security filtering and threat protection.
AbuseIPDB API
IP reputation and abuse reporting database for threat intelligence
Use AbuseIPDB to check IP reputation from NextDNS logs. Correlate blocked DNS queries with known abusive IPs to enhance threat detection accuracy.
LuaDNS API
Programmable DNS hosting with Lua scripting — developer-focused DNS automation
Choose LuaDNS for custom DNS logic and scripting. Choose NextDNS for pre-built security, privacy, and parental control policies without custom code.
Specific to using API through Jentic.
What authentication does the NextDNS API use?
The NextDNS API uses API key authentication with the X-Api-Key header. Generate an API key from your NextDNS account dashboard, then include it in every request header as X-Api-Key: your_key. Through Jentic, API keys are stored encrypted in the vault and agents receive scoped access tokens — raw keys never enter agent context. Install Jentic with pip install jentic and connect via https://app.jentic.com/sign-up.
Can I block specific domains programmatically with the NextDNS API?
Yes, use the POST /profiles/{profileId}/denylist endpoint to add domains to a profile's blocklist. The request body includes the domain ID (the domain name itself) and an active boolean. Blocked domains return NXDOMAIN responses to DNS queries. You can also retrieve the current denylist with GET /profiles/{profileId}/denylist and remove entries with DELETE /profiles/{profileId}/denylist/{domainId}. Through Jentic, agents search for 'block a malicious domain', load the schema, and execute in one flow.
What are the rate limits for the NextDNS API?
The NextDNS API documentation does not specify explicit rate limits in the OpenAPI spec. Typical usage should stay within reasonable query volumes per profile. For high-frequency analytics queries or real-time log streaming, use cursor-based pagination (limit parameter with maximum 500 for most endpoints, 1000 for logs) and implement backoff strategies. Contact NextDNS support if you need higher throughput for enterprise deployments.
How do I retrieve DNS query logs for a specific device with the NextDNS API?
Use the GET /profiles/{profileId}/logs endpoint with the device query parameter set to the device ID. NextDNS logs include device information (ID, name, model) for identified devices. Filter logs by status (default, blocked, allowed, error), time range (from and to parameters supporting ISO 8601 or relative like -6h), and search patterns. Logs support cursor-based pagination with up to 1000 entries per request. For real-time monitoring, use the GET /profiles/{profileId}/logs/stream endpoint which returns Server-Sent Events.
Can I enable threat intelligence feeds through the NextDNS API?
Yes, update security settings using PATCH /profiles/{profileId}/security. The SecuritySettings schema includes boolean flags for threatIntelligenceFeeds, aiThreatDetection, googleSafeBrowsing, cryptojacking, dnsRebinding, typosquatting, and other threat categories. Set the desired protections to true in the request body. Enabled feeds automatically block known malicious domains without requiring manual denylist updates. Retrieve current settings with GET /profiles/{profileId}/security.
Does the NextDNS API support real-time log streaming?
Yes, the GET /profiles/{profileId}/logs/stream endpoint returns DNS query logs as Server-Sent Events (text/event-stream). This enables real-time monitoring of DNS traffic with filtering by device, status, and search patterns. The stream supports resumption using the id query parameter to continue from a specific event. Combine with Jentic agent workflows to trigger automated responses when specific query patterns or blocked threats are detected.
How do I configure parental control policies with the NextDNS API?
Use PATCH /profiles/{profileId}/parentalControl to update parental control settings. The ParentalControlSettings schema includes services and categories arrays (each with id and active fields), plus booleans for safeSearch, youtubeRestrictedMode, and blockBypass. Enable content categories like adult content or gambling by setting their active flag to true. SafeSearch enforcement modifies DNS responses for search engines to filter results. Retrieve current settings with GET /profiles/{profileId}/parentalControl.
/profiles/{profileId}/logs
Fetch DNS query logs with filtering
/profiles/{profileId}/logs/stream
Stream real-time DNS query events via SSE