{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels/",
        "slug": "apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels",
        "url": "https://update.dsesecurity.com/updates/apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels/"
        },
        "title": "Apply the IDNA bidirectional rule before accepting right-to-left labels",
        "summary": "Use RFC 5893 — Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA) to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "explainer",
            "name": "Explainer"
        },
        "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": "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-27T12:17:53+00:00",
        "modified_at": "2026-08-27T12:18:09+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 587,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of RFC 5893 — Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)",
        "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": "RFC 5893 — Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)",
            "url": "https://www.rfc-editor.org/rfc/rfc5893.html",
            "published_on": null,
            "authority": "www.rfc-editor.org"
        },
        "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>Frame this document as a source-led configuration and assurance check: Apply the IDNA bidirectional rule before accepting right-to-left labels. 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://www.rfc-editor.org/rfc/rfc5893.html\" target=\"_blank\" rel=\"noopener noreferrer\">RFC 5893 — Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)</a> from RFC Editor / Internet Engineering Task Force supports the following bounded statements:</p>\n<ul>\n<li>An IDNA label passes the Bidi Rule only if all six conditions in the rule are satisfied. The research record locates this support at <strong>Section 2 (The Bidi Rule)</strong>.</li>\n<li>The first character determines direction: R or AL makes an RTL label, while L makes an LTR label. The research record locates this support at <strong>Section 2 (The Bidi Rule), condition 1</strong>.</li>\n<li>An RTL label cannot contain both European-number and Arabic-number Bidi properties. The research record locates this support at <strong>Section 2 (The Bidi Rule), condition 4</strong>.</li>\n</ul>\n<p>Keep the evidence boundary at these traced claims. They support a review of authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers; they do not support conclusions outside the source&#8217;s stated conditions.</p>\n<h2>What the source does not establish</h2>\n<p>This RFC evidence supports only the named DNS protocol decision; it does not prove Windows implementation support or a safe production configuration. It does not establish a deployment&#8217;s current state, authorize a production change, prove compliance, or show that Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state are healthy. Documented options are review inputs, not universal mandates.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Section 2 (The Bidi Rule)</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Section 2 (The Bidi Rule), condition 1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 3 at <strong>Section 2 (The Bidi Rule), condition 4</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Within authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, which versions, roles, and configuration states define the review population?</li>\n<li>Could Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state invalidate the test, hide a failure, or change applicability?</li>\n<li>Who owns the decision, and which observation requires stopping, escalation, or rollback?</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 authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, observed and expected states, owner, and reason for deviation.</p>\n<p>Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state, while excluding secrets and sensitive personal or topology data from ordinary tickets.</p>\n<h2>Verification and evidence</h2>\n<p>Keep the source locations <strong>Section 2 (The Bidi Rule)</strong>; <strong>Section 2 (The Bidi Rule), condition 1</strong>; <strong>Section 2 (The Bidi Rule), condition 4</strong> adjacent to the sanitized artifacts used for comparison. Prefer zone data, packet captures, query transcripts, delegation checks, resolver configuration, and negative-answer behavior, with enough identity and timing data for an independent recheck.</p>\n<p>Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.rfc-editor.org/rfc/rfc5893.html\" target=\"_blank\" rel=\"noopener noreferrer\">RFC 5893 — Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)</a> — RFC Editor / Internet Engineering Task Force</li>\n</ul>",
        "content_text": "Frame this document as a source-led configuration and assurance check: Apply the IDNA bidirectional rule before accepting right-to-left labels. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official RFC 5893 — Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nAn IDNA label passes the Bidi Rule only if all six conditions in the rule are satisfied. The research record locates this support at Section 2 (The Bidi Rule).\nThe first character determines direction: R or AL makes an RTL label, while L makes an LTR label. The research record locates this support at Section 2 (The Bidi Rule), condition 1.\nAn RTL label cannot contain both European-number and Arabic-number Bidi properties. The research record locates this support at Section 2 (The Bidi Rule), condition 4.\n\nKeep the evidence boundary at these traced claims. They support a review of authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers; they do not support conclusions outside the source’s stated conditions.\nWhat the source does not establish\nThis RFC evidence supports only the named DNS protocol decision; it does not prove Windows implementation support or a safe production configuration. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state are healthy. Documented options are review inputs, not universal mandates.\nApplicability questions\n\nFor source statement 1 at Section 2 (The Bidi Rule), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Section 2 (The Bidi Rule), condition 1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 2 (The Bidi Rule), condition 4, which observable configuration, record, or test can confirm applicability here?\nWithin authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, which versions, roles, and configuration states define the review population?\nCould Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state invalidate the test, hide a failure, or change applicability?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\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 authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, observed and expected states, owner, and reason for deviation.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nKeep the source locations Section 2 (The Bidi Rule); Section 2 (The Bidi Rule), condition 1; Section 2 (The Bidi Rule), condition 4 adjacent to the sanitized artifacts used for comparison. Prefer zone data, packet captures, query transcripts, delegation checks, resolver configuration, and negative-answer behavior, with enough identity and timing data for an independent recheck.\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\nOfficial references\n\nRFC 5893 — Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA) — RFC Editor / Internet Engineering Task Force",
        "content_markdown": "Frame this document as a source-led configuration and assurance check: Apply the IDNA bidirectional rule before accepting right-to-left labels. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [RFC 5893 — Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)](https://www.rfc-editor.org/rfc/rfc5893.html) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\n- An IDNA label passes the Bidi Rule only if all six conditions in the rule are satisfied. The research record locates this support at Section 2 (The Bidi Rule).\n\n- The first character determines direction: R or AL makes an RTL label, while L makes an LTR label. The research record locates this support at Section 2 (The Bidi Rule), condition 1.\n\n- An RTL label cannot contain both European-number and Arabic-number Bidi properties. The research record locates this support at Section 2 (The Bidi Rule), condition 4.\n\nKeep the evidence boundary at these traced claims. They support a review of authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers; they do not support conclusions outside the source’s stated conditions.\n\n## What the source does not establish\n\nThis RFC evidence supports only the named DNS protocol decision; it does not prove Windows implementation support or a safe production configuration. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state are healthy. Documented options are review inputs, not universal mandates.\n\n## Applicability questions\n\n- For source statement 1 at Section 2 (The Bidi Rule), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Section 2 (The Bidi Rule), condition 1, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 3 at Section 2 (The Bidi Rule), condition 4, which observable configuration, record, or test can confirm applicability here?\n\n- Within authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, which versions, roles, and configuration states define the review population?\n\n- Could Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state invalidate the test, hide a failure, or change applicability?\n\n- Who owns the decision, and which observation requires stopping, escalation, or rollback?\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 authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, observed and expected states, owner, and reason for deviation.\n\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state, while excluding secrets and sensitive personal or topology data from ordinary tickets.\n\n## Verification and evidence\n\nKeep the source locations Section 2 (The Bidi Rule); Section 2 (The Bidi Rule), condition 1; Section 2 (The Bidi Rule), condition 4 adjacent to the sanitized artifacts used for comparison. Prefer zone data, packet captures, query transcripts, delegation checks, resolver configuration, and negative-answer behavior, with enough identity and timing data for an independent recheck.\n\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\n\n## Official references\n\n- [RFC 5893 — Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)](https://www.rfc-editor.org/rfc/rfc5893.html) — RFC Editor / Internet Engineering Task Force"
    },
    "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/apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels/",
                "url": "https://update.dsesecurity.com/updates/apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Apply the IDNA bidirectional rule before accepting right-to-left labels",
                        "item": "https://update.dsesecurity.com/updates/apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels/#article",
                "identifier": "https://update.dsesecurity.com/updates/apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels/",
                "url": "https://update.dsesecurity.com/updates/apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels/",
                "headline": "Apply the IDNA bidirectional rule before accepting right-to-left labels",
                "description": "Use RFC 5893 — Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA) to review this narrow operational decision without…",
                "abstract": "Use RFC 5893 — Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA) to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Frame this document as a source-led configuration and assurance check: Apply the IDNA bidirectional rule before accepting right-to-left labels. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official RFC 5893 — Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nAn IDNA label passes the Bidi Rule only if all six conditions in the rule are satisfied. The research record locates this support at Section 2 (The Bidi Rule).\nThe first character determines direction: R or AL makes an RTL label, while L makes an LTR label. The research record locates this support at Section 2 (The Bidi Rule), condition 1.\nAn RTL label cannot contain both European-number and Arabic-number Bidi properties. The research record locates this support at Section 2 (The Bidi Rule), condition 4.\n\nKeep the evidence boundary at these traced claims. They support a review of authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers; they do not support conclusions outside the source’s stated conditions.\nWhat the source does not establish\nThis RFC evidence supports only the named DNS protocol decision; it does not prove Windows implementation support or a safe production configuration. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state are healthy. Documented options are review inputs, not universal mandates.\nApplicability questions\n\nFor source statement 1 at Section 2 (The Bidi Rule), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Section 2 (The Bidi Rule), condition 1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 2 (The Bidi Rule), condition 4, which observable configuration, record, or test can confirm applicability here?\nWithin authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, which versions, roles, and configuration states define the review population?\nCould Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state invalidate the test, hide a failure, or change applicability?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\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 authoritative zones, delegations, resolvers, caches, record owners, and the clients that consume the resulting answers, observed and expected states, owner, and reason for deviation.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Windows DNS roles, Active Directory-integrated data, forwarding paths, time, routing, firewalls, and registrar or registry state, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nKeep the source locations Section 2 (The Bidi Rule); Section 2 (The Bidi Rule), condition 1; Section 2 (The Bidi Rule), condition 4 adjacent to the sanitized artifacts used for comparison. Prefer zone data, packet captures, query transcripts, delegation checks, resolver configuration, and negative-answer behavior, with enough identity and timing data for an independent recheck.\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\nOfficial references\n\nRFC 5893 — Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA) — RFC Editor / Internet Engineering Task Force",
                "datePublished": "2026-08-27T12:17:53+00:00",
                "dateModified": "2026-08-27T12:18:09+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels/"
                },
                "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/apply-the-idna-bidirectional-rule-before-accepting-right-to-left-labels/#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": "Apply the IDNA bidirectional rule before accepting right-to-left labels"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Networks & Infrastructure",
                    "Explainer",
                    "Advisory priority"
                ],
                "genre": "Explainer",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 587,
                "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": "RFC 5893 — Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA)",
                    "url": "https://www.rfc-editor.org/rfc/rfc5893.html"
                }
            }
        ]
    }
}