{"id":76594,"date":"2026-06-05T06:07:13","date_gmt":"2026-06-05T06:07:13","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=76594"},"modified":"2026-06-05T06:07:14","modified_gmt":"2026-06-05T06:07:14","slug":"godaddy-how-to-enable-dnssec-in-godaddy-step-by-step-complete-tutorial","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/godaddy-how-to-enable-dnssec-in-godaddy-step-by-step-complete-tutorial\/","title":{"rendered":"Godaddy – How to Enable DNSSEC in GoDaddy: Step-by-Step Complete Tutorial"},"content":{"rendered":"\n
\"\"<\/a><\/figure>\n\n\n\n

What is DNSSEC?<\/h2>\n\n\n\n

DNSSEC stands for Domain Name System Security Extensions<\/strong>. It adds a security layer to DNS by digitally signing DNS records so resolvers can verify that DNS responses are authentic and have not been modified in transit. In simple words, DNSSEC helps protect your domain from attacks like DNS spoofing and cache poisoning, where users could be redirected to a fake or malicious website. GoDaddy describes DNSSEC as a way to verify the origin of DNS across the internet using digital signatures. (GoDaddy<\/a>)<\/p>\n\n\n\n

DNSSEC does not<\/strong> replace SSL\/TLS. SSL secures the browser-to-website connection, while DNSSEC secures the DNS lookup path.<\/p>\n\n\n\n

\n\n\n\n

Before You Enable DNSSEC in GoDaddy<\/h1>\n\n\n\n

First, understand your domain setup. DNSSEC steps depend on where your domain is registered<\/strong> and where your DNS is hosted<\/strong>.<\/p>\n\n\n\n

There are three common cases:<\/p>\n\n\n\n

Scenario<\/th>What to do<\/th><\/tr><\/thead>
Domain registered at GoDaddy and using GoDaddy nameservers<\/td>Enable DNSSEC directly in GoDaddy<\/td><\/tr>
Domain registered at GoDaddy but DNS hosted elsewhere, like Cloudflare, Route 53, etc.<\/td>Enable DNSSEC at DNS provider, then add DS record in GoDaddy<\/td><\/tr>
DNS hosted at GoDaddy but domain registered elsewhere<\/td>Enable DNSSEC in GoDaddy, then copy DS record to your registrar<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

GoDaddy says it manages all DNSSEC settings automatically for domains using GoDaddy nameservers. If the domain is not using GoDaddy nameservers, you must manually add DS records. (GoDaddy<\/a>)<\/p>\n\n\n\n

\n\n\n\n

Important Notes Before Starting<\/h1>\n\n\n\n

GoDaddy currently provides 5 free DNSSEC credits<\/strong> in each account for domains using GoDaddy nameservers. One DNSSEC-enabled domain uses one credit. For more domains, GoDaddy says you may need Premium DNS or additional credits. (GoDaddy<\/a>)<\/p>\n\n\n\n

Also, some domains or country-code TLDs may not support DNSSEC. GoDaddy also warns that incorrect DS records can cause DNS resolution problems. (GoDaddy<\/a>)<\/p>\n\n\n\n

Before enabling DNSSEC, do these checks:<\/p>\n\n\n\n

    \n
  1. Confirm your domain is active and not expired.<\/li>\n\n\n\n
  2. Confirm your current nameservers.<\/li>\n\n\n\n
  3. Avoid changing nameservers during DNSSEC setup.<\/li>\n\n\n\n
  4. Keep a backup\/screenshot of your DNS records.<\/li>\n\n\n\n
  5. Make sure you have access to your DNS provider and registrar account.<\/li>\n\n\n\n
  6. Enable 2-step verification on your GoDaddy account for better domain security.<\/li>\n<\/ol>\n\n\n\n
    \n\n\n\n

    Case 1: Enable DNSSEC When Domain Uses GoDaddy Nameservers<\/h1>\n\n\n\n

    Use this method when your domain is both managed in GoDaddy and using GoDaddy nameservers.<\/p>\n\n\n\n

    Typical GoDaddy nameservers look like:<\/p>\n\n\n

    nsXX<\/span>.domaincontrol<\/span>.com<\/span>\nnsYY<\/span>.domaincontrol<\/span>.com<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
    Step 1: Sign in to GoDaddy<\/h2>\n\n\n\n
    Go to your GoDaddy account and sign in.<\/p>\n\n\n\n
    Then open your Domain Portfolio<\/strong>.<\/p>\n\n\n\n
    Step 2: Select Your Domain<\/h2>\n\n\n\n
    From the domain list, click the domain where you want to enable DNSSEC.<\/p>\n\n\n\n
    Example:<\/p>\n\n\n
    example<\/span>.com<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
    This opens the Domain Settings<\/strong> page.<\/p>\n\n\n\n
    Step 3: Open DNS Settings<\/h2>\n\n\n\n
    Inside the domain settings page:<\/p>\n\n\n
    DNS \u2192 DNSSEC\n<\/code><\/span><\/pre>\n\n\n
    GoDaddy\u2019s official flow is: select the domain, choose DNS<\/strong>, then select DNSSEC<\/strong>. (GoDaddy<\/a>)<\/p>\n\n\n\n
    Step 4: Click \u201cTurn On DNSSEC\u201d<\/h2>\n\n\n\n
    On the DNSSEC screen, choose:<\/p>\n\n\n
    Turn On DNSSEC\n<\/code><\/span><\/pre>\n\n\n
    Step 5: Enter Notification Email<\/h2>\n\n\n\n
    GoDaddy will ask for an email address.<\/p>\n\n\n\n
    This email is used for DNSSEC key-change notifications.<\/p>\n\n\n\n
    Use an email that you or your technical team actively monitors.<\/p>\n\n\n\n
    Example:<\/p>\n\n\n
    admin<\/span>@example<\/span>.com\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
    Step 6: Save the Change<\/h2>\n\n\n\n
    Click:<\/p>\n\n\n
    Save\n<\/code><\/span><\/pre>\n\n\n
    GoDaddy says DNSSEC is turned on immediately, but it may take up to 90 minutes<\/strong> to appear in your account. DNS changes usually take effect within an hour but may take up to 48 hours globally<\/strong>. (GoDaddy<\/a>)<\/p>\n\n\n\n
    Step 7: Wait for Propagation<\/h2>\n\n\n\n
    Do not immediately change nameservers or delete DNS records. Give DNSSEC time to propagate.<\/p>\n\n\n\n
    \n\n\n\n
    Case 2: Domain Registered at GoDaddy but DNS Hosted Elsewhere<\/h1>\n\n\n\n
    This is very common.<\/p>\n\n\n\n
    Example:<\/p>\n\n\n\n
    Registrar<\/th>DNS Provider<\/th><\/tr><\/thead>
    GoDaddy<\/td>Cloudflare<\/td><\/tr>
    GoDaddy<\/td>AWS Route 53<\/td><\/tr>
    GoDaddy<\/td>DigitalOcean<\/td><\/tr>
    GoDaddy<\/td>Namecheap DNS<\/td><\/tr>
    GoDaddy<\/td>Custom DNS server<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    In this case, you do not<\/strong> generate DNSSEC keys inside GoDaddy. You enable DNSSEC in your DNS provider first, then add the DS record in GoDaddy.<\/p>\n\n\n\n
    GoDaddy says if your domain is registered with GoDaddy but is not using GoDaddy nameservers, you must enable DNSSEC with your DNS provider and then manually add DS records in GoDaddy. (GoDaddy<\/a>)<\/p>\n\n\n\n
    Step 1: Enable DNSSEC at Your DNS Provider<\/h2>\n\n\n\n
    Log in to your DNS hosting provider.<\/p>\n\n\n\n
    For example:<\/p>\n\n\n
    Cloudflare\nAWS Route 53\nDigitalOcean\nGoogle Cloud DNS\nAzure DNS\n<\/code><\/span><\/pre>\n\n\n
    Find the DNSSEC option and enable it.<\/p>\n\n\n\n
    Your DNS provider will generate DS record details.<\/p>\n\n\n\n
    A DS record usually contains:<\/p>\n\n\n
    Key Tag\nAlgorithm\nDigest Type\nDigest\n<\/code><\/span><\/pre>\n\n\n
    Step 2: Copy the DS Record Details<\/h2>\n\n\n\n
    Example DS record format:<\/p>\n\n\n
    example<\/span>.com<\/span>. 3600 IN<\/span> DS<\/span> 2371 13 2 7A1B2C3D4E5F<\/span>...\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
    Breakdown:<\/p>\n\n\n\n
    Field<\/th>Meaning<\/th><\/tr><\/thead>
    2371<\/td>Key Tag<\/td><\/tr>
    13<\/td>Algorithm<\/td><\/tr>
    2<\/td>Digest Type<\/td><\/tr>
    7A1B2C…<\/td>Digest<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    Step 3: Go to GoDaddy Domain Portfolio<\/h2>\n\n\n\n
    Sign in to GoDaddy and open:<\/p>\n\n\n
    Domain Portfolio\n<\/code><\/span><\/pre>\n\n\n
    Select your domain.<\/p>\n\n\n\n
    Step 4: Open DS Records<\/h2>\n\n\n\n
    Go to:<\/p>\n\n\n
    DNS \u2192 DS Records\n<\/code><\/span><\/pre>\n\n\n
    GoDaddy\u2019s official DS record flow is: select domain, choose DNS<\/strong>, then select DS Records<\/strong>. (GoDaddy<\/a>)<\/p>\n\n\n\n
    Step 5: Click Add<\/h2>\n\n\n\n
    Click:<\/p>\n\n\n
    Add\n<\/code><\/span><\/pre>\n\n\n
    Step 6: Enter DS Record Details<\/h2>\n\n\n\n
    Enter the values from your DNS provider:<\/p>\n\n\n
    Key Tag: 2371\nAlgorithm: 13\nDigest Type: 2\nDigest: 7A1B2C3D4E5F...\n<\/code><\/span><\/pre>\n\n\n
    GoDaddy defines the fields as Key Tag, Algorithm, Digest Type, and Digest. The Key Tag must be between 1 and 65536, Algorithm must be selected from available options, Digest Type is usually 1 or 2, and Digest is an alphanumeric string. (GoDaddy<\/a>)<\/p>\n\n\n\n
    Step 7: Save<\/h2>\n\n\n\n
    Click:<\/p>\n\n\n
    Save\n<\/code><\/span><\/pre>\n\n\n
    If GoDaddy shows an error, verify the DS record with your DNS provider. GoDaddy says incorrect DS records cannot be saved. (GoDaddy<\/a>)<\/p>\n\n\n\n
    Step 8: Wait and Validate<\/h2>\n\n\n\n
    Wait for DNS propagation. Then validate DNSSEC using commands or online tools.<\/p>\n\n\n\n
    \n\n\n\n
    Case 3: DNS Hosted at GoDaddy but Domain Registered Elsewhere<\/h1>\n\n\n\n
    This case happens when:<\/p>\n\n\n\n
    Registrar<\/th>DNS Provider<\/th><\/tr><\/thead>
    Namecheap<\/td>GoDaddy DNS<\/td><\/tr>
    Google Domains\/Squarespace<\/td>GoDaddy DNS<\/td><\/tr>
    Porkbun<\/td>GoDaddy DNS<\/td><\/tr>
    Any registrar<\/td>GoDaddy nameservers<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    In this case, GoDaddy signs the zone, but your registrar must publish the DS record at the parent registry.<\/p>\n\n\n\n
    Step 1: Enable DNSSEC in GoDaddy<\/h2>\n\n\n\n
    Go to:<\/p>\n\n\n
    GoDaddy \u2192 Domain Portfolio \u2192 Select Domain \u2192 DNS \u2192 DNSSEC\n<\/code><\/span><\/pre>\n\n\n
    Click:<\/p>\n\n\n
    Turn On DNSSEC\n<\/code><\/span><\/pre>\n\n\n
    Enter your email and save.<\/p>\n\n\n\n
    Step 2: Copy DS Record from GoDaddy<\/h2>\n\n\n\n
    GoDaddy says if your domain uses GoDaddy nameservers but is not registered with GoDaddy, you need to copy the DS record and enter it at your domain registrar. (GoDaddy<\/a>)<\/p>\n\n\n\n
    Copy the DS record details.<\/p>\n\n\n\n
    Step 3: Add DS Record at Your Registrar<\/h2>\n\n\n\n
    Log in to your registrar account.<\/p>\n\n\n\n
    Find:<\/p>\n\n\n
    DNSSEC\nDS Records\nDelegation Signer\nSecurity\n<\/code><\/span><\/pre>\n\n\n
    Add the DS values provided by GoDaddy.<\/p>\n\n\n\n
    Step 4: Save and Wait<\/h2>\n\n\n\n
    After saving, allow propagation.<\/p>\n\n\n\n
    \n\n\n\n
    How to Verify DNSSEC<\/h1>\n\n\n\n
    After enabling DNSSEC, verify that your domain is properly signed.<\/p>\n\n\n\n
    Method 1: Use dig<\/code><\/h2>\n\n\n\n
    Run:<\/p>\n\n\n
    dig<\/span> DS<\/span> example<\/span>.com<\/span> +short<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
    Expected output should show a DS record:<\/p>\n\n\n
    2371 13 2 7A1B2C3D4E5F...\n<\/code><\/span><\/pre>\n\n\n
    Check DNSKEY:<\/p>\n\n\n
    dig<\/span> DNSKEY<\/span> example<\/span>.com<\/span> +dnssec<\/span> +multi<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
    Check A record with DNSSEC:<\/p>\n\n\n
    dig<\/span> A<\/span> example<\/span>.com<\/span> +dnssec<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
    Look for:<\/p>\n\n\n
    ad\n<\/code><\/span><\/pre>\n\n\n
    The ad<\/code> flag means authenticated data, but it depends on the resolver used.<\/p>\n\n\n\n
    Method 2: Use delv<\/code><\/h2>\n\n\n
    delv<\/span> example<\/span>.com<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
    If DNSSEC is valid, you should see successful validation.<\/p>\n\n\n\n
    Method 3: Use Online Tools<\/h2>\n\n\n\n
    You can check with tools like:<\/p>\n\n\n
    DNSViz\nVerisign DNSSEC Debugger\nZoneCheck\n<\/code><\/span><\/pre>\n\n\n
    GoDaddy also mentions these types of online DNSSEC checking tools, though it does not provide support for their results. (GoDaddy<\/a>)<\/p>\n\n\n\n
    \n\n\n\n
    How to Disable DNSSEC in GoDaddy<\/h1>\n\n\n\n
    Disabling DNSSEC may be needed when:<\/p>\n\n\n\n
      \n
    1. You are moving DNS providers.<\/li>\n\n\n\n
    2. You are changing nameservers.<\/li>\n\n\n\n
    3. You accidentally added the wrong DS record.<\/li>\n\n\n\n
    4. Your domain is failing DNSSEC validation.<\/li>\n\n\n\n
    5. You want to use Secondary DNS, because GoDaddy notes DNSSEC may need to be turned off if using Secondary DNS. (GoDaddy<\/a>)<\/li>\n<\/ol>\n\n\n\n
      Steps to Disable DNSSEC<\/h2>\n\n\n\n
      Go to:<\/p>\n\n\n
      GoDaddy \u2192 Domain Portfolio \u2192 Select Domain \u2192 DNS \u2192 DNSSEC\n<\/code><\/span><\/pre>\n\n\n
      Click:<\/p>\n\n\n
      Turn Off DNSSEC\n<\/code><\/span><\/pre>\n\n\n
      Then select:<\/p>\n\n\n
      Remove\n<\/code><\/span><\/pre>\n\n\n
      GoDaddy says DNSSEC is turned off immediately, but it may take up to 90 minutes to reflect in the account. (GoDaddy<\/a>)<\/p>\n\n\n\n
      \n\n\n\n
      Common DNSSEC Problems and Fixes<\/h1>\n\n\n\n
      Problem 1: Website Not Opening After Enabling DNSSEC<\/h2>\n\n\n\n
      Most likely cause:<\/p>\n\n\n
      DS record mismatch\n<\/code><\/span><\/pre>\n\n\n
      This means the DS record at the registrar does not match the DNSKEY at the DNS provider.<\/p>\n\n\n\n
      Fix:<\/p>\n\n\n\n
        \n
      1. Check DS record at registrar.<\/li>\n\n\n\n
      2. Check DNSKEY at DNS provider.<\/li>\n\n\n\n
      3. Remove wrong DS record.<\/li>\n\n\n\n
      4. Add correct DS record.<\/li>\n\n\n\n
      5. Wait for propagation.<\/li>\n<\/ol>\n\n\n\n
        GoDaddy says DNSSEC issues are often related to digital signatures on nameservers, and if DS records do not match those signatures, the domain may not resolve properly. (GoDaddy<\/a>)<\/p>\n\n\n\n
        Problem 2: DNSSEC Option Not Visible<\/h2>\n\n\n\n
        Possible reasons:<\/p>\n\n\n\n
          \n
        1. Domain does not support DNSSEC.<\/li>\n\n\n\n
        2. Domain is using unsupported TLD.<\/li>\n\n\n\n
        3. Domain is not using GoDaddy nameservers.<\/li>\n\n\n\n
        4. DNSSEC credits are not available.<\/li>\n\n\n\n
        5. You are looking in DNS Records instead of DNSSEC\/DS Records.<\/li>\n<\/ol>\n\n\n\n
          Problem 3: GoDaddy Rejects DS Record<\/h2>\n\n\n\n
          Possible reasons:<\/p>\n\n\n\n
            \n
          1. Wrong Key Tag.<\/li>\n\n\n\n
          2. Wrong Algorithm.<\/li>\n\n\n\n
          3. Wrong Digest Type.<\/li>\n\n\n\n
          4. Extra spaces in Digest.<\/li>\n\n\n\n
          5. Copied incomplete Digest.<\/li>\n\n\n\n
          6. DS record belongs to an old DNSSEC key.<\/li>\n<\/ol>\n\n\n\n
            Fix:<\/p>\n\n\n\n
            Copy the DS record again from your DNS provider and re-enter it carefully.<\/p>\n\n\n\n
            Problem 4: You Changed Nameservers Without Removing Old DS Record<\/h2>\n\n\n\n
            This is a very common DNSSEC mistake.<\/p>\n\n\n\n
            If you move DNS from Cloudflare to GoDaddy, or GoDaddy to Route 53, remove the old DS record before or during migration. Otherwise, the parent zone may still point to an old DNSSEC key, causing validation failure.<\/p>\n\n\n\n
            Recommended migration flow:<\/p>\n\n\n
            1.<\/span> Lower DNS TTL\n2.<\/span> Disable DNSSEC or remove old DS record\n3.<\/span> Wait for<\/span> propagation\n4.<\/span> Change nameservers\n5.<\/span> Enable DNSSEC at new<\/span> DNS provider\n6.<\/span> Add new<\/span> DS record\n7.<\/span> Validate\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
            \n\n\n\n
            DNSSEC Best Practices<\/h1>\n\n\n\n
            1. Do Not Enable DNSSEC Blindly<\/h2>\n\n\n\n
            DNSSEC is powerful, but mistakes can break DNS resolution. Always understand where your DNS is hosted.<\/p>\n\n\n\n
            2. Keep Registrar and DNS Provider Access Ready<\/h2>\n\n\n\n
            If DNSSEC breaks, you may need urgent access to both accounts.<\/p>\n\n\n\n
            3. Avoid Nameserver Changes During DNSSEC Setup<\/h2>\n\n\n\n
            Nameserver changes and DNSSEC changes together can create troubleshooting hell. Tiny DNS chaos goblin, basically.<\/p>\n\n\n\n
            4. Use One DNS Provider Clearly<\/h2>\n\n\n\n
            Avoid confusion like:<\/p>\n\n\n
            Registrar: GoDaddy\nNameservers: Cloudflare\nOld DS Record: Route 53\n<\/code><\/span><\/pre>\n\n\n
            This is how domains disappear from the internet for some users.<\/p>\n\n\n\n
            5. Monitor After Enabling<\/h2>\n\n\n\n
            Check:<\/p>\n\n\n
            dig<\/span> DS<\/span> yourdomain<\/span>.com<\/span> +short<\/span>\ndig<\/span> DNSKEY<\/span> yourdomain<\/span>.com<\/span> +dnssec<\/span> +multi<\/span>\ndelv<\/span> yourdomain<\/span>.com<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
            6. Document Your DS Record<\/h2>\n\n\n\n
            Keep a record of:<\/p>\n\n\n
            Provider\nKey Tag\nAlgorithm\nDigest Type\nDigest\nDate<\/span> enabled\nAdmin email\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
            \n\n\n\n
            Final Recommended GoDaddy DNSSEC Checklist<\/h1>\n\n\n\n
            Use this checklist before you enable DNSSEC:<\/p>\n\n\n
            [ ]<\/span> Domain<\/span> is<\/span> active<\/span>\n[ ]<\/span> Nameservers<\/span> confirmed<\/span>\n[ ]<\/span> DNS<\/span> provider<\/span> confirmed<\/span>\n[ ]<\/span> DNS<\/span> records<\/span> backed<\/span> up<\/span>\n[ ]<\/span> GoDaddy<\/span> account<\/span> secured<\/span> with<\/span> 2FA<\/span>\n[ ]<\/span> DNSSEC<\/span> credits<\/span> available<\/span> if<\/span> using<\/span> GoDaddy<\/span> nameservers<\/span>\n[ ]<\/span> DS<\/span> record<\/span> copied<\/span> correctly<\/span> if<\/span> using<\/span> external<\/span> DNS<\/span>\n[ ]<\/span> No<\/span> old<\/span> DS<\/span> records<\/span> remain<\/span>\n[ ]<\/span> Validation<\/span> completed<\/span> after<\/span> setup<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
            \n\n\n\n
            Conclusion<\/h1>\n\n\n\n
            Enabling DNSSEC in GoDaddy is simple if your domain uses GoDaddy nameservers: go to Domain Portfolio \u2192 Domain \u2192 DNS \u2192 DNSSEC \u2192 Turn On DNSSEC<\/strong>, enter your notification email, and save.<\/p>\n\n\n\n
            If your DNS is hosted outside GoDaddy, the process is different: enable DNSSEC at your DNS provider first, copy the DS record, then add that DS record inside GoDaddy under DNS \u2192 DS Records<\/strong>.<\/p>\n\n\n\n
            The most important rule is this: the DS record at the registrar must match the DNSSEC key at the DNS provider<\/strong>. If they do not match, your domain can stop resolving for DNSSEC-validating users.<\/p>\n","protected":false},"excerpt":{"rendered":"
            What is DNSSEC? DNSSEC stands for Domain Name System Security Extensions. It adds a security layer to DNS by digitally signing DNS records so resolvers can verify… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[11138],"tags":[],"class_list":["post-76594","post","type-post","status-publish","format-standard","hentry","category-best-tools"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/76594","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=76594"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/76594\/revisions"}],"predecessor-version":[{"id":76596,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/76594\/revisions\/76596"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=76594"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=76594"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=76594"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}