{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence/",
        "slug": "export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence",
        "url": "https://update.dsesecurity.com/updates/export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence/"
        },
        "title": "Export-DnsServerDnsSecPublicKey: export dns server dns sec public key with before-and-after evidence",
        "summary": "Use Export-DnsServerDnsSecPublicKey to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "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:47+00:00",
        "modified_at": "2026-08-27T17:22:19+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 579,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Export-DnsServerDnsSecPublicKey",
        "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": "Export-DnsServerDnsSecPublicKey",
            "url": "https://learn.microsoft.com/en-us/powershell/module/dnsserver/export-dnsserverdnssecpublickey?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>Use this document to connect an official requirement or behavior to observable evidence: Export-DnsServerDnsSecPublicKey: export dns server dns sec public key with before-and-after 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/export-dnsserverdnssecpublickey?view=windowsserver2025-ps\" target=\"_blank\" rel=\"noopener noreferrer\">Export-DnsServerDnsSecPublicKey</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At DESCRIPTION, Microsoft states: “The Export-DnsServerDnsSecPublicKey cmdlet exports delegation signer (DS) or Domain Name System public key (DNSKEY) information for a Domain Name System Security Extensions (DNSSEC)-signed zone.” The research record locates this support at <strong>DESCRIPTION</strong>.</li>\n<li>At Example 1: Export a trust anchor to a file share, Microsoft states: “This command exports the trust anchor (DS record) for Contoso.com to a file share.” The research record locates this support at <strong>Example 1: Export a trust anchor to a file share</strong>.</li>\n</ul>\n<p>The source support ends with the statements listed above. Use them to examine Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles in the applicable environment, not to imply a wider guarantee.</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: Export a trust anchor to a file share</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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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>Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution. Handle credentials, keys, recovery data, and personal information through approved secure channels.</p>\n<h2>Verification and evidence</h2>\n<p>Tie each conclusion back to <strong>DESCRIPTION</strong>; <strong>Example 1: Export a trust anchor to a file share</strong> and to observable material such as PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands. Preserve provenance and stable identifiers without copying secrets into the evidence set.</p>\n<p>Label this evidence set <strong>DSE-20260827-219</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/export-dnsserverdnssecpublickey?view=windowsserver2025-ps\" target=\"_blank\" rel=\"noopener noreferrer\">Export-DnsServerDnsSecPublicKey</a> — Microsoft</li>\n</ul>",
        "content_text": "Use this document to connect an official requirement or behavior to observable evidence: Export-DnsServerDnsSecPublicKey: export dns server dns sec public key with before-and-after evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Export-DnsServerDnsSecPublicKey from Microsoft supports the following bounded statements:\n\nAt DESCRIPTION, Microsoft states: “The Export-DnsServerDnsSecPublicKey cmdlet exports delegation signer (DS) or Domain Name System public key (DNSKEY) information for a Domain Name System Security Extensions (DNSSEC)-signed zone.” The research record locates this support at DESCRIPTION.\nAt Example 1: Export a trust anchor to a file share, Microsoft states: “This command exports the trust anchor (DS record) for Contoso.com to a file share.” The research record locates this support at Example 1: Export a trust anchor to a file share.\n\nThe source support ends with the statements listed above. Use them to examine Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles in the applicable environment, not to imply a wider guarantee.\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: Export a trust anchor to a file share, 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nTie each conclusion back to DESCRIPTION; Example 1: Export a trust anchor to a file share and to observable material such as PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands. Preserve provenance and stable identifiers without copying secrets into the evidence set.\nLabel this evidence set DSE-20260827-219 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\nExport-DnsServerDnsSecPublicKey — Microsoft",
        "content_markdown": "Use this document to connect an official requirement or behavior to observable evidence: Export-DnsServerDnsSecPublicKey: export dns server dns sec public key with before-and-after evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Export-DnsServerDnsSecPublicKey](https://learn.microsoft.com/en-us/powershell/module/dnsserver/export-dnsserverdnssecpublickey?view=windowsserver2025-ps) from Microsoft supports the following bounded statements:\n\n- At DESCRIPTION, Microsoft states: “The Export-DnsServerDnsSecPublicKey cmdlet exports delegation signer (DS) or Domain Name System public key (DNSKEY) information for a Domain Name System Security Extensions (DNSSEC)-signed zone.” The research record locates this support at DESCRIPTION.\n\n- At Example 1: Export a trust anchor to a file share, Microsoft states: “This command exports the trust anchor (DS record) for Contoso.com to a file share.” The research record locates this support at Example 1: Export a trust anchor to a file share.\n\nThe source support ends with the statements listed above. Use them to examine Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles in the applicable environment, not to imply a wider guarantee.\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: Export a trust anchor to a file share, 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution. Handle credentials, keys, recovery data, and personal information through approved secure channels.\n\n## Verification and evidence\n\nTie each conclusion back to DESCRIPTION; Example 1: Export a trust anchor to a file share and to observable material such as PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands. Preserve provenance and stable identifiers without copying secrets into the evidence set.\n\nLabel this evidence set DSE-20260827-219 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- [Export-DnsServerDnsSecPublicKey](https://learn.microsoft.com/en-us/powershell/module/dnsserver/export-dnsserverdnssecpublickey?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/export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence/",
                "url": "https://update.dsesecurity.com/updates/export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Export-DnsServerDnsSecPublicKey: export dns server dns sec public key with before-and-after evidence",
                        "item": "https://update.dsesecurity.com/updates/export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence/#article",
                "identifier": "https://update.dsesecurity.com/updates/export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence/",
                "url": "https://update.dsesecurity.com/updates/export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence/",
                "headline": "Export-DnsServerDnsSecPublicKey: export dns server dns sec public key with before-and-after evidence",
                "description": "Use Export-DnsServerDnsSecPublicKey to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use Export-DnsServerDnsSecPublicKey to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Use this document to connect an official requirement or behavior to observable evidence: Export-DnsServerDnsSecPublicKey: export dns server dns sec public key with before-and-after evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Export-DnsServerDnsSecPublicKey from Microsoft supports the following bounded statements:\n\nAt DESCRIPTION, Microsoft states: “The Export-DnsServerDnsSecPublicKey cmdlet exports delegation signer (DS) or Domain Name System public key (DNSKEY) information for a Domain Name System Security Extensions (DNSSEC)-signed zone.” The research record locates this support at DESCRIPTION.\nAt Example 1: Export a trust anchor to a file share, Microsoft states: “This command exports the trust anchor (DS record) for Contoso.com to a file share.” The research record locates this support at Example 1: Export a trust anchor to a file share.\n\nThe source support ends with the statements listed above. Use them to examine Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles in the applicable environment, not to imply a wider guarantee.\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: Export a trust anchor to a file share, 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nTie each conclusion back to DESCRIPTION; Example 1: Export a trust anchor to a file share and to observable material such as PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands. Preserve provenance and stable identifiers without copying secrets into the evidence set.\nLabel this evidence set DSE-20260827-219 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\nExport-DnsServerDnsSecPublicKey — Microsoft",
                "datePublished": "2026-08-27T17:03:47+00:00",
                "dateModified": "2026-08-27T17:22:19+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence/"
                },
                "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/export-dnsserverdnssecpublickey-export-dns-server-dns-sec-public-key-with-before-and-after-evidence/#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": "Export-DnsServerDnsSecPublicKey: export dns server dns sec public key with before-and-after evidence"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Guide",
                    "Advisory priority"
                ],
                "genre": "Guide",
                "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": 579,
                "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": "Export-DnsServerDnsSecPublicKey",
                    "url": "https://learn.microsoft.com/en-us/powershell/module/dnsserver/export-dnsserverdnssecpublickey?view=windowsserver2025-ps"
                }
            }
        ]
    }
}