{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting/",
        "slug": "add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting",
        "url": "https://update.dsesecurity.com/updates/add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting/"
        },
        "title": "Add-DnsServerResponseRateLimitingExceptionlist: stage additions to dns server response rate limiting exceptionlist with bounded evidence",
        "summary": "Use Add-DnsServerResponseRateLimitingExceptionlist to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "playbook",
            "name": "Playbook"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "microsoft-365-identity",
                "name": "Microsoft 365 & Identity",
                "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-27T17:03:51+00:00",
        "modified_at": "2026-08-27T17:22:19+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 556,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Add-DnsServerResponseRateLimitingExceptionlist",
        "dse_recommendation": "Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.",
        "primary_source": {
            "name": "Add-DnsServerResponseRateLimitingExceptionlist",
            "url": "https://learn.microsoft.com/en-us/powershell/module/dnsserver/add-dnsserverresponseratelimitingexceptionlist?view=windowsserver2025-ps",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>Keep this document to one review outcome: Add-DnsServerResponseRateLimitingExceptionlist: stage additions to dns server response rate limiting exceptionlist with bounded evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://learn.microsoft.com/en-us/powershell/module/dnsserver/add-dnsserverresponseratelimitingexceptionlist?view=windowsserver2025-ps\" target=\"_blank\" rel=\"noopener noreferrer\">Add-DnsServerResponseRateLimitingExceptionlist</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At DESCRIPTION, Microsoft states: “The Add-DnsServerResponseRateLimiting cmdlet adds a Response Rate Limiting (RRL) exception list on the DNS server.” The research record locates this support at <strong>DESCRIPTION</strong>.</li>\n<li>At Example 1: Add a domain to an RRL exception list, Microsoft states: “This command adds an RRL exception for the domain contoso.com.” The research record locates this support at <strong>Example 1: Add a domain to an RRL exception list</strong>.</li>\n</ul>\n<p>Keep the evidence boundary at these traced claims. They support a review of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles; they do not support conclusions outside the source&#8217;s stated conditions.</p>\n<h2>What the source does not establish</h2>\n<p>The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution and the environment&#8217;s recorded constraints.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>DESCRIPTION</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Example 1: Add a domain to an RRL exception list</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>What inventory proves which parts of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles are in and out of scope?</li>\n<li>Which condition in Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution must be healthy before evidence is trustworthy?</li>\n<li>What result would disprove the working assumption and return the issue to the owner?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, observed and expected states, owner, and reason for deviation.</p>\n<p>If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution and sanitize protected material before retention.</p>\n<h2>Verification and evidence</h2>\n<p>A reviewer should be able to retrace the decision from <strong>DESCRIPTION</strong>; <strong>Example 1: Add a domain to an RRL exception list</strong> through PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands. Record what was collected, where, when, by whom, and which system or role it represents.</p>\n<p>Label this evidence set <strong>DSE-20260827-215</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/powershell/module/dnsserver/add-dnsserverresponseratelimitingexceptionlist?view=windowsserver2025-ps\" target=\"_blank\" rel=\"noopener noreferrer\">Add-DnsServerResponseRateLimitingExceptionlist</a> — Microsoft</li>\n</ul>",
        "content_text": "Keep this document to one review outcome: Add-DnsServerResponseRateLimitingExceptionlist: stage additions to dns server response rate limiting exceptionlist with bounded evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Add-DnsServerResponseRateLimitingExceptionlist from Microsoft supports the following bounded statements:\n\nAt DESCRIPTION, Microsoft states: “The Add-DnsServerResponseRateLimiting cmdlet adds a Response Rate Limiting (RRL) exception list on the DNS server.” The research record locates this support at DESCRIPTION.\nAt Example 1: Add a domain to an RRL exception list, Microsoft states: “This command adds an RRL exception for the domain contoso.com.” The research record locates this support at Example 1: Add a domain to an RRL exception list.\n\nKeep the evidence boundary at these traced claims. They support a review of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles; they do not support conclusions outside the source’s stated conditions.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Example 1: Add a domain to an RRL exception list, which observable configuration, record, or test can confirm applicability here?\nWhat inventory proves which parts of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles are in and out of scope?\nWhich condition in Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution must be healthy before evidence is trustworthy?\nWhat result would disprove the working assumption and return the issue to the owner?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, observed and expected states, owner, and reason for deviation.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution and sanitize protected material before retention.\nVerification and evidence\nA reviewer should be able to retrace the decision from DESCRIPTION; Example 1: Add a domain to an RRL exception list through PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands. Record what was collected, where, when, by whom, and which system or role it represents.\nLabel this evidence set DSE-20260827-215 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\nOfficial references\n\nAdd-DnsServerResponseRateLimitingExceptionlist — Microsoft",
        "content_markdown": "Keep this document to one review outcome: Add-DnsServerResponseRateLimitingExceptionlist: stage additions to dns server response rate limiting exceptionlist with bounded evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Add-DnsServerResponseRateLimitingExceptionlist](https://learn.microsoft.com/en-us/powershell/module/dnsserver/add-dnsserverresponseratelimitingexceptionlist?view=windowsserver2025-ps) from Microsoft supports the following bounded statements:\n\n- At DESCRIPTION, Microsoft states: “The Add-DnsServerResponseRateLimiting cmdlet adds a Response Rate Limiting (RRL) exception list on the DNS server.” The research record locates this support at DESCRIPTION.\n\n- At Example 1: Add a domain to an RRL exception list, Microsoft states: “This command adds an RRL exception for the domain contoso.com.” The research record locates this support at Example 1: Add a domain to an RRL exception list.\n\nKeep the evidence boundary at these traced claims. They support a review of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles; they do not support conclusions outside the source’s stated conditions.\n\n## What the source does not establish\n\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution and the environment’s recorded constraints.\n\n## Applicability questions\n\n- For source statement 1 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Example 1: Add a domain to an RRL exception list, which observable configuration, record, or test can confirm applicability here?\n\n- What inventory proves which parts of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles are in and out of scope?\n\n- Which condition in Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution must be healthy before evidence is trustworthy?\n\n- What result would disprove the working assumption and return the issue to the owner?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, observed and expected states, owner, and reason for deviation.\n\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution and sanitize protected material before retention.\n\n## Verification and evidence\n\nA reviewer should be able to retrace the decision from DESCRIPTION; Example 1: Add a domain to an RRL exception list through PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands. Record what was collected, where, when, by whom, and which system or role it represents.\n\nLabel this evidence set DSE-20260827-215 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\n\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\n\n## Official references\n\n- [Add-DnsServerResponseRateLimitingExceptionlist](https://learn.microsoft.com/en-us/powershell/module/dnsserver/add-dnsserverresponseratelimitingexceptionlist?view=windowsserver2025-ps) — Microsoft"
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting/",
                "url": "https://update.dsesecurity.com/updates/add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Add-DnsServerResponseRateLimitingExceptionlist: stage additions to dns server response rate limiting exceptionlist with bounded evidence",
                        "item": "https://update.dsesecurity.com/updates/add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting/#article",
                "identifier": "https://update.dsesecurity.com/updates/add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting/",
                "url": "https://update.dsesecurity.com/updates/add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting/",
                "headline": "Add-DnsServerResponseRateLimitingExceptionlist: stage additions to dns server response rate limiting exceptionlist with bounded evidence",
                "description": "Use Add-DnsServerResponseRateLimitingExceptionlist to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use Add-DnsServerResponseRateLimitingExceptionlist to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Keep this document to one review outcome: Add-DnsServerResponseRateLimitingExceptionlist: stage additions to dns server response rate limiting exceptionlist with bounded evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Add-DnsServerResponseRateLimitingExceptionlist from Microsoft supports the following bounded statements:\n\nAt DESCRIPTION, Microsoft states: “The Add-DnsServerResponseRateLimiting cmdlet adds a Response Rate Limiting (RRL) exception list on the DNS server.” The research record locates this support at DESCRIPTION.\nAt Example 1: Add a domain to an RRL exception list, Microsoft states: “This command adds an RRL exception for the domain contoso.com.” The research record locates this support at Example 1: Add a domain to an RRL exception list.\n\nKeep the evidence boundary at these traced claims. They support a review of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles; they do not support conclusions outside the source’s stated conditions.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Example 1: Add a domain to an RRL exception list, which observable configuration, record, or test can confirm applicability here?\nWhat inventory proves which parts of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles are in and out of scope?\nWhich condition in Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution must be healthy before evidence is trustworthy?\nWhat result would disprove the working assumption and return the issue to the owner?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, observed and expected states, owner, and reason for deviation.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution and sanitize protected material before retention.\nVerification and evidence\nA reviewer should be able to retrace the decision from DESCRIPTION; Example 1: Add a domain to an RRL exception list through PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands. Record what was collected, where, when, by whom, and which system or role it represents.\nLabel this evidence set DSE-20260827-215 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\nOfficial references\n\nAdd-DnsServerResponseRateLimitingExceptionlist — Microsoft",
                "datePublished": "2026-08-27T17:03:51+00:00",
                "dateModified": "2026-08-27T17:22:19+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/add-dnsserverresponseratelimitingexceptionlist-stage-additions-to-dns-server-response-rate-limiting/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Add-DnsServerResponseRateLimitingExceptionlist: stage additions to dns server response rate limiting exceptionlist with bounded evidence"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Playbook",
                    "Advisory priority"
                ],
                "genre": "Playbook",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Microsoft 365 & Identity",
                        "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 556,
                "timeRequired": "PT3M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Add-DnsServerResponseRateLimitingExceptionlist",
                    "url": "https://learn.microsoft.com/en-us/powershell/module/dnsserver/add-dnsserverresponseratelimitingexceptionlist?view=windowsserver2025-ps"
                }
            }
        ]
    }
}