{
  "slug": "dns-domains",
  "topic": "DNS and domains",
  "status": "published",
  "order": 43,
  "capability": "exposure/dns",
  "title": "DNS and domains: could someone hijack your domains or your DNS?",
  "short": "Put phishing-resistant MFA on every registrar and DNS account this month, registry-lock the domains you sign in and mail with, and send all user DNS through a resolver you control.",
  "answer": "This month, put phishing-resistant MFA on every registrar and DNS provider account, registry-lock the few domains that sign-in, email and your website depend on, and publish CAA records on every domain. Then send all user DNS through a validating, filtering resolver you control, and sign zones with DNSSEC only where your provider automates the keys.",
  "audience": "IT and security teams in organizations of any size that own domains, run public DNS and resolve DNS for their users",
  "version": "1.2",
  "lastReviewed": "2026-11-05",
  "reviewEveryDays": 30,
  "blocks": [
    {
      "type": "ranked",
      "id": "first",
      "title": "If you only do five things",
      "navTitle": "Five things",
      "items": [
        {
          "title": "Put phishing-resistant MFA on every registrar and DNS account.",
          "text": "In the campaign behind CISA's ED 19-01, attackers used stolen credentials to change DNS records, then got valid certificates to decrypt the redirected traffic[^ed1901]. Use security keys or passkeys."
        },
        {
          "title": "Registry-lock the domains everything depends on.",
          "text": "Anyone in your registrar account can ask to lift a registrar lock. A registry lock is set by the registry and can take longer to remove[^eppcodes]; DENIC's .de lock needs a named contact to confirm each change[^denicrl]. Lock the domains behind sign-in, email, your website and name servers. Test an unlock, since the lock also delays urgent fixes."
        },
        {
          "title": "Make expiry impossible.",
          "text": "Use auto-renew on a company card and two trusted managers per domain[^ncscdomains]. Answer your provider's holder verification requests, or .de domains go offline and are later released[^denicverify]."
        },
        {
          "title": "Publish CAA everywhere and watch CT logs.",
          "text": "Name the CAs you and your SaaS providers use, publish `issue \";\"` on domains that need no certificates[^rfc8659] and monitor CT logs for every domain, parked ones included[^googlecctld]. Parked domains also need the DMARC record from the endpoints and email sheet."
        },
        {
          "title": "Send all user DNS through a resolver you control.",
          "text": "Validate DNSSEC, block known-bad domains with protective DNS, log queries and block DNS that goes around your resolvers[^sp80081]."
        }
      ]
    },
    {
      "type": "steps",
      "id": "hijack",
      "title": "If your domain or DNS is hijacked",
      "navTitle": "Hijack response",
      "items": [
        {
          "title": "Check the delegation at the registry.",
          "text": "Query the TLD's name servers for your NS and DS records. Your DNS provider's console can look normal while the domain points elsewhere."
        },
        {
          "title": "Call your registrar and DNS provider.",
          "text": "Ask both to freeze the domain. If a gTLD domain was transferred away, only the registrars involved can file an ICANN transfer dispute, within 12 months[^tdrp], so push yours to act today."
        },
        {
          "title": "Lock the attacker out and restore.",
          "text": "Change the passwords and MFA of every account that can change DNS records, and audit every public record on all authoritative servers, as ED 19-01 required before CISA retired it in 2026[^ed1901][^cisaed]. Revoke API keys and compare against your last zone export."
        },
        {
          "title": "Hunt down certificates.",
          "text": "Find certificates issued during the hijack in CT logs and report them to the issuing CA[^ed1901]. CAA can't stop issuance during a hijack, but CAA bound to your ACME account stops attackers reusing that validation afterwards[^googlecctld]."
        },
        {
          "title": "Treat redirected traffic as stolen.",
          "text": "Reset passwords of users who signed in during the window, rotate secrets sent by email and check the EU security laws sheet for reporting duties."
        }
      ]
    },
    {
      "type": "list",
      "id": "accounts",
      "title": "Registrar and DNS provider accounts",
      "navTitle": "Accounts",
      "items": [
        "**One owner, several hands.** Move domains out of personal, agency and hosting accounts into ones your organization owns, and have one internal group register every domain[^ncscdomains].",
        "**Scope who can change records.** In Azure DNS, grant DNS Zone Contributor per zone and ReadOnly-lock zones that rarely change. A CanNotDelete lock on the SOA record blocks deleting the zone[^azdns].",
        "**Alert on NS and MX changes** and keep DNS change logs in your SIEM[^ncscdomains]. Export every zone weekly as a known-good copy.",
        "**Report lookalikes to the registrar.** Monitor new registrations[^sp80081]. Registrars of gTLDs must act promptly on actionable evidence of phishing and other DNS abuse[^icannabuse]."
      ]
    },
    {
      "type": "list",
      "id": "dnssec",
      "title": "DNSSEC and CAA",
      "navTitle": "DNSSEC and CAA",
      "items": [
        "**Sign only where your provider automates the keys.** DNSSEC can't stop someone who logs in to your registrar or DNS provider, but it lets CAs detect forged CAA records[^rfc8659]. Use ECDSA P-256 or Ed25519; RSA/SHA-1 is deprecated[^icannalg].",
        "**Know what breaks.** Since 15 March 2026, CAs must validate DNSSEC and may not treat a validation error as permission to issue[^br], so a broken signature also blocks renewals. Moving DNS provider? Pull the DS record and wait out its TTL first, as Route 53's guide does[^awsmigrate].",
        "**Bind CAA to your ACME account.** Let's Encrypt honors `accounturi` now[^lecaa]; list every account you renew with. All CAs must from 15 March 2027, and email validation ends on 15 March 2028[^br]."
      ]
    },
    {
      "type": "list",
      "id": "resolvers",
      "title": "What your resolvers should do",
      "navTitle": "Resolvers",
      "items": [
        "**Recurse only for your own clients.** No internet-facing server should be both authoritative and recursive[^sp80081].",
        "**Validate DNSSEC** with automatic trust anchor updates, two time sources and QNAME minimization[^sp80081].",
        "**Block DNS that goes around them:** outbound ports 53 and 853 except from your resolvers, and known public DoH servers[^sp80081].",
        "**Log queries.** Always log blocked queries, and keep a full log for forensics even if the SIEM gets less[^sp80081]. In Germany, agree per-user logs and their retention with the works council[^betrvg].",
        "**Practice turning off validation for one zone.** A faulty DENIC key rollover on 5 May 2026 broke .de names, signed or not, on validating resolvers; some large operators suspended validation for .de[^denicout]."
      ]
    },
    {
      "type": "list",
      "id": "filtering",
      "title": "Protective DNS and DNS over HTTPS",
      "navTitle": "Protective DNS",
      "items": [
        "**Small teams can start free.** Cloudflare's Zero Trust Free plan, for teams under 50 users, includes its web gateway and keeps logs 24 hours[^cfplans]. Quad9 welcomes business forwarders if it is their only upstream; log queries there yourself[^quad9].",
        "**Otherwise buy one with logs and an API.** Ask for current deny lists, editable allow lists and block logs your SIEM can pull; Cloudflare exports logs only on contract plans[^cfplans]. It doesn't replace your own DNS logs[^ncscpriv].",
        "**Want resolution kept in the EU?** DNS4EU's free resolver is for individuals only; companies use Whalebone Immunity, its commercial version on European infrastructure[^dns4eu].",
        "**Control DoH in browsers.** Chrome sends no DoH on managed devices unless the `DnsOverHttpsMode` policy allows it[^chromedoh]. Lock Firefox's `DNSOverHTTPS` policy to off or to your resolver's `ProviderURL`[^ffdoh]."
      ]
    },
    {
      "type": "list",
      "id": "changed",
      "title": "What changed in 2026",
      "navTitle": "What changed",
      "span": "full",
      "items": [
        "**Three ccTLD registries were hijacked.** Attackers compromised the registries of .gh, .sl and .as, changed DNS records and got certificates for Google and other brands. Google advises restrictive CAA with ACME account bindings[^googlecctld].",
        "**The root zone has a new key.** KSK-2024 (key tag 38696) has signed it since 11 October 2026. Check each validating resolver's trust anchors instead of assuming automatic updates worked[^ksk].",
        "**.de verifies holder data.** Under NIS2, DENIC has risk-checked holder data since December 2025, now including a phone number, and existing domains can be asked to verify too[^denicreg][^denicverify]. Verification runs only through your provider, and DENIC never asks for passwords by email[^denicverify].",
        "**Windows DNS Server speaks DoH.** Since the June 2026 update, Windows Server 2025 accepts DoH from clients, but not toward upstream servers[^kb5094125]. Clients can encrypt DNS without bypassing your resolver."
      ]
    },
    {
      "type": "list",
      "id": "skip",
      "title": "What you can skip",
      "items": [
        "**Buying every typo and new TLD.** Register near-misses of sign-in and payment domains; monitor and report the rest.",
        "**Signing internal zones.** NIST advises against it unless a rule requires it[^sp80081].",
        "**NSEC3 to hide your zone.** It often still reveals every name; NIST calls NSEC the more prudent choice[^sp80081]."
      ]
    },
    {
      "type": "list",
      "id": "mistakes",
      "title": "Mistakes that cost the most",
      "navTitle": "Mistakes",
      "items": [
        "**Domains in an account that can close.** Closing an AWS account suspends its Route 53 domains within 5 days[^awsdomains].",
        "**Recovery email on the domain itself.** A hijacker then gets your password resets. Use an address on another domain.",
        "**Deleting the zone, not the delegation.** An attacker with an account at that DNS host may then take over the name[^sp80081]."
      ]
    },
    {
      "type": "columns",
      "id": "by-size",
      "title": "What this looks like at your size",
      "navTitle": "By team size",
      "span": "full",
      "columns": [
        {
          "title": "Small team, no security staff",
          "items": [
            "Move every domain into a registrar account you own, with two admins on security keys.",
            "Turn on auto-renew and registrar lock everywhere, and publish CAA for the CA you use.",
            "Point your firewall at business-ready protective DNS, such as Cloudflare's free plan or Quad9."
          ]
        },
        {
          "title": "Growing, with IT or security staff",
          "items": [
            "Registry-lock the critical domains, export zones weekly and alert on NS and MX changes.",
            "Run validating resolvers with protective DNS and set browser DoH policies.",
            "Rehearse the hijack steps yearly with your registrar's real contacts."
          ]
        },
        {
          "title": "Enterprise or regulated",
          "items": [
            "Consolidate at one corporate registrar with registry lock and named contacts.",
            "Require two-person approval for registrar and DNS changes.",
            "If you provide DNS for others, check NIS2 scope in the EU security laws sheet."
          ]
        }
      ]
    }
  ],
  "changes": [
    {
      "date": "2026-11-05",
      "version": "1.2",
      "text": "Noted that CISA retired ED 19-01 in January 2026, added that German companies agree per-user DNS logs with the works council, and confirmed the transfer dispute rules still stand after ICANN's June 2026 policy decision."
    },
    {
      "date": "2026-11-05",
      "version": "1.1",
      "text": "Reviewed for company readers: protective DNS now names services businesses may use (Cloudflare's Zero Trust Free plan and Quad9 for small teams, Whalebone Immunity for resolution kept in the EU), since DNS4EU's free resolver is for individuals only, and drops UK government PDNS."
    },
    {
      "date": "2026-11-05",
      "version": "1.0",
      "text": "Published after a copy edit and a source-by-source fact check, which corrected DNS4EU eligibility (its free resolver excludes businesses), made the outbound DNS blocking and DNSSEC migration steps safe and replaced an AWS blog post with AWS documentation."
    },
    {
      "date": "2026-11-05",
      "version": "0.1",
      "text": "First draft, based on NIST SP 800-81r3, the CA/Browser Forum Baseline Requirements 2.3.1, the FDIC OIG audit of CISA ED 19-01, NCSC guidance, ICANN and DENIC documentation and Google's report on the 2026 ccTLD hijacks."
    }
  ],
  "sources": [
    {
      "id": "ed1901",
      "title": "The FDIC's Actions to Mitigate the Risk of DNS Infrastructure Tampering (on CISA ED 19-01)",
      "publisher": "FDIC OIG",
      "date": "24 Sep 2019",
      "url": "https://www.fdicoig.gov/sites/default/files/reports/2022-08/19-006AUD.pdf"
    },
    {
      "id": "cisaed",
      "title": "CISA Retires Ten Emergency Directives",
      "publisher": "CISA",
      "date": "8 Jan 2026",
      "url": "https://www.cisa.gov/news-events/news/cisa-retires-ten-emergency-directives-marking-era-federal-cybersecurity"
    },
    {
      "id": "sp80081",
      "title": "SP 800-81r3, Secure Domain Name System (DNS) Deployment Guide",
      "publisher": "NIST",
      "date": "Mar 2026",
      "url": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-81r3.pdf"
    },
    {
      "id": "ncscdomains",
      "title": "Managing public domain names",
      "publisher": "NCSC (UK)",
      "date": "25 Sep 2019",
      "url": "https://www.ncsc.gov.uk/guidance/managing-public-domain-names"
    },
    {
      "id": "eppcodes",
      "title": "EPP status codes",
      "publisher": "ICANN",
      "date": "checked 5 Nov 2026",
      "url": "https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en"
    },
    {
      "id": "denicrl",
      "title": ".de Registry Lock",
      "publisher": "DENIC",
      "date": "checked 5 Nov 2026",
      "url": "https://www.denic.de/en/products/de-registry-lock/"
    },
    {
      "id": "denicverify",
      "title": "Domain holder verification",
      "publisher": "DENIC",
      "date": "checked 5 Nov 2026",
      "url": "https://www.denic.de/en/products/holder-data-verification/general-information/"
    },
    {
      "id": "denicreg",
      "title": "What is changing about the registration of .de domains",
      "publisher": "DENIC",
      "date": "19 Dec 2025",
      "url": "https://blog.denic.de/en/new-legislation-what-is-changing-about-the-registration-of-de-domains/"
    },
    {
      "id": "tdrp",
      "title": "Registrar Transfer Dispute Resolution Policy",
      "publisher": "ICANN",
      "date": "updated 21 Feb 2024",
      "url": "https://www.icann.org/en/contracted-parties/accredited-registrars/registrar-transfer-dispute-resolution-policy-21-02-2024-en"
    },
    {
      "id": "icannabuse",
      "title": "2013 RAA amendment on DNS abuse, Section 3.18",
      "publisher": "ICANN",
      "date": "effective 5 Apr 2024",
      "url": "https://itp.cdn.icann.org/en/files/accredited-registrars/registrar-accreditation-agreement-global-amendment-05apr24-en.htm"
    },
    {
      "id": "azdns",
      "title": "Protecting DNS zones and records",
      "publisher": "Microsoft Learn",
      "date": "updated 12 Aug 2026",
      "url": "https://learn.microsoft.com/en-us/azure/dns/dns-protect-zones-recordsets"
    },
    {
      "id": "awsdomains",
      "title": "Route 53 domains when an AWS account is closed",
      "publisher": "AWS Docs",
      "date": "checked 5 Nov 2026",
      "url": "https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/troubleshooting-account-closed.html"
    },
    {
      "id": "awsmigrate",
      "title": "Making Route 53 the DNS service for a domain in use",
      "publisher": "AWS Docs",
      "date": "checked 5 Nov 2026",
      "url": "https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-in-use.html"
    },
    {
      "id": "denicout",
      "title": "Final Report: DNS Outage of 5 May 2026",
      "publisher": "DENIC",
      "date": "11 Jun 2026",
      "url": "https://blog.denic.de/en/final-report-dns-outage-of-5-may-2026/"
    },
    {
      "id": "betrvg",
      "title": "BetrVG, § 87",
      "publisher": "BMJV",
      "date": "checked 5 Nov 2026",
      "url": "https://www.gesetze-im-internet.de/betrvg/__87.html"
    },
    {
      "id": "ksk",
      "title": "Root KSK rollover",
      "publisher": "ICANN",
      "date": "checked 5 Nov 2026",
      "url": "https://www.icann.org/resources/pages/ksk-rollover"
    },
    {
      "id": "icannalg",
      "title": "DNSSEC algorithm guidance for registrars",
      "publisher": "ICANN",
      "date": "20 May 2026",
      "url": "https://itp.cdn.icann.org/en/files/communications/registrars-dnssec-algorithm-recommendations-best-practices-20-05-2026-en.pdf"
    },
    {
      "id": "br",
      "title": "TLS Baseline Requirements, version 2.3.1",
      "publisher": "CA/Browser Forum",
      "date": "4 Oct 2026",
      "url": "https://cabforum.org/working-groups/server/baseline-requirements/requirements/"
    },
    {
      "id": "rfc8659",
      "title": "RFC 8659: DNS Certification Authority Authorization (CAA) Resource Record",
      "publisher": "IETF",
      "date": "Nov 2019",
      "url": "https://www.rfc-editor.org/rfc/rfc8659"
    },
    {
      "id": "lecaa",
      "title": "CAA",
      "publisher": "Let's Encrypt",
      "date": "updated 4 Oct 2026",
      "url": "https://letsencrypt.org/docs/caa/"
    },
    {
      "id": "googlecctld",
      "title": "Chrome's response to recent ccTLD registry hijacks",
      "publisher": "Google",
      "date": "6 Oct 2026",
      "url": "https://blog.google/security/chromes-response-to-recent-cctld-registry-hijacks/"
    },
    {
      "id": "cfplans",
      "title": "SASE and Zero Trust pricing",
      "publisher": "Cloudflare",
      "date": "checked 5 Nov 2026",
      "url": "https://www.cloudflare.com/plans/sase-zero-trust.md"
    },
    {
      "id": "quad9",
      "title": "DNS forwarder best practices",
      "publisher": "Quad9",
      "date": "checked 5 Nov 2026",
      "url": "https://docs.quad9.net/Quad9_For_Organizations/DNS_Forwarder_Best_Practices/"
    },
    {
      "id": "ncscpriv",
      "title": "Protective DNS for the private sector",
      "publisher": "NCSC (UK)",
      "date": "9 Jun 2021",
      "url": "https://www.ncsc.gov.uk/guidance/protective-dns-for-private-sector"
    },
    {
      "id": "dns4eu",
      "title": "Free public DNS resolver for Europe",
      "publisher": "DNS4EU",
      "date": "checked 5 Nov 2026",
      "url": "https://joindns4.eu/for-public"
    },
    {
      "id": "chromedoh",
      "title": "DnsOverHttpsMode policy definition",
      "publisher": "Chromium",
      "date": "checked 5 Nov 2026",
      "url": "https://github.com/chromium/chromium/blob/main/components/policy/resources/templates/policy_definitions/Miscellaneous/DnsOverHttpsMode.yaml"
    },
    {
      "id": "ffdoh",
      "title": "DNSOverHTTPS policy",
      "publisher": "Firefox admin docs",
      "date": "checked 5 Nov 2026",
      "url": "https://firefox-admin-docs.mozilla.org/reference/policies/dnsoverhttps/"
    },
    {
      "id": "kb5094125",
      "title": "KB5094125 (OS Build 26100.32995)",
      "publisher": "Microsoft Support",
      "date": "9 Jun 2026",
      "url": "https://support.microsoft.com/kb/5094125"
    }
  ]
}