Monitor DNS and domain security drift with DNSSEC, expiry checks and alerts
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 14 nodes and runs on a schedule (cron 0 * * * *) (plus 1 other trigger). It uses only n8n's built-in nodes.
How it runs
Trigger: On a schedule (cron 0 * * * *) (plus 1 other trigger).
- Set Configuration Parameters (Edit Fields (Set)): sets 6 fields: domains, allowedIpCidrPrefixes, domainExpiryWarningDays…
- Resolve Current DNS Records & DNSSEC (Code): runs custom JavaScript code
- Check Domain Expiry via RDAP (HTTP Request): calls an HTTP API
- Parse Expiry & Compute Days Remaining (Code): runs custom JavaScript code
- Compare Against Baseline & Compute Drift Score (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Classify Severity & Build Security Alert (Code): runs custom JavaScript code
- No Risk Detected - No Action (Edit Fields (Set)): sets 1 field: note
- If: checks a condition and branches into true / false
- Wait: pauses before continuing
…plus 2 more steps. See the full node list below.
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - Wait
n8n-nodes-base.wait - If
n8n-nodes-base.if
From the author
Quick overview This workflow runs hourly (or manually) to resolve DNS records for configured domains using Node.js DNS lookups, compares them to an expected baseline, and classifies detected changes as standard logs or critical security alerts with a short…