Coverage & risk · Dangling DNS Sentinel
A CNAME pointing at a deleted Azure resource is a subdomain takeover waiting to happen. Microsoft ships a one-off script; this watches every day.
Deploys as a managed application in your own subscription. No vendor backend, no data egress. Flat monthly fee, billed by Microsoft.
Microsoft documents the risk and provides Get-DanglingDnsRecords, a PowerShell script you run once. Resources are deleted every week. The gap between those two facts is where subdomain takeovers happen.
A serverless function on a schedule, with a system-assigned managed identity, deployed into your subscription by the Azure Marketplace. Roles are granted by you after deployment with the one-line script in the package, so nothing runs until you say so. Every role it asks for, and why:
| Reader | list DNS zones and records |
Alerts go to the Teams Workflows webhook you configure. Nothing is sent anywhere else.
No. The function runs in your subscription and writes only to your configured alert destination. Katabarwa Labs operates no backend and receives nothing.
A flat monthly fee on your Azure bill through the Marketplace, plus the small consumption cost of the function itself. No per-resource or per-user pricing.
Delete the managed application from the Azure portal. Its resource group and identity go with it, and any role you granted can be removed the same way.
support@llmgraph.ai, or the support page.
A CNAME pointing at a deleted Azure resource is a subdomain takeover waiting to happen. Microsoft ships a one-off script; this watches every day.
Deploy from the Azure Marketplace