Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

A certificate request fails with a CAA error when the certificate authority (CA) cannot prove that your DNS policy permits it to issue for every requested name, or when DNS itself cannot return a valid CAA answer. Fixing the problem means identifying the CA and all SAN or wildcard names, tracing CAA from each exact hostname through its parent names and any CNAME target, then correcting the authorization or the DNS infrastructure.

CAA is optional: a domain with no CAA record normally permits any CA that passes the other validation checks. A restrictive policy, however, must explicitly authorize the CA you are using. SERVFAIL, NOTIMP, malformed answers and timeouts are DNS failures, not evidence that a particular CA is unauthorized.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What a CAA record does

Certification Authority Authorization (CAA) is a DNS resource record defined by RFC 8659 (Internet Engineering Task Force, November 2019). It lets the holder of a DNS name publish which certificate authorities are authorized to issue certificates for that name. The policy is an additional control against unintended certificate issuance; it does not replace domain validation, account checks, certificate-profile rules or any other requirement imposed by the CA.

CAA conformance is therefore necessary when a policy exists, but it is not sufficient for issuance. A CA can find an authorized CAA record and still reject a request because a challenge failed, an organization review is incomplete, a requested identifier is not allowed, or a certificate profile has another restriction.

#1 Best Overall
Sale
Compressed Air Duster,130000RPM Super Power Cordless Air Duster,Rechargeable Brushless Blower,3 Gear Adjustable Blower with LED Light,Dust Remover for Computer/House/Outdoor/Car
  • Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
  • With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
  • Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
  • Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
  • Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.

When a CA checks a name, it looks for a CAA record set at the fully qualified domain name (FQDN) being certified. If no set is found, it moves to the parent label and continues toward the DNS root. A record on example.com can consequently govern www.example.com and other descendants until a closer name publishes its own CAA set. A CNAME is followed during this process, so the target name’s policy can authorize or block issuance.

Does a domain need a CAA record?

No. DigiCert states that a CAA record is not required for TLS/SSL or Secure Email (S/MIME) issuance. If no CAA record is found and all other checks pass, any CA may be able to issue. Let’s Encrypt likewise checks CAA before every issuance, which means an error can sometimes arise from DNS behavior even when the domain owner has never intentionally configured CAA.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Adding CAA is a policy decision. Leaving it absent maximizes compatibility with different CAs but provides no DNS-level restriction on which CA can issue. Publishing a restrictive set narrows the allowed issuers and can reduce the chance of an unintended certificate, but every future CA change, wildcard request and delegated hostname must be reflected in DNS.

  • Use no CAA records when you deliberately accept issuance by any CA that meets the CA’s ordinary validation rules.
  • Use restrictive CAA when you have selected an issuing CA and want DNS to enforce that choice.
  • Review the policy before migrations, renewals, new SANs, wildcard certificates and changes to CNAME-based hosting.

How a CA evaluates CAA

1. It checks every requested name

A certificate request can contain one common name and several Subject Alternative Names (SANs). The CA evaluates each name separately. A policy that authorizes the CA for www.example.com does not automatically prove that the same CA is authorized for an unrelated SAN such as api.example.net. List every name in the order shown by the CA’s error, including names hidden in automation.

2. It searches the name and its ancestors

The search starts at the exact FQDN and moves up one label at a time until it finds a CAA set. A closer record overrides a parent policy for that branch. For example, a policy at example.com can cover shop.example.com, while a separate set at secure.shop.example.com controls that deeper name.

Rank #2
EVEO® Screen Cleaner Spray Kit (Streak-Free) TV Screen Cleaner for Smart TV, Lcd, LEd, Oled | Computer Screen Cleaner Spray and Wipe Microfiber Cloth - TV, Monitor, Laptop, iPad, Car - 6.7oz 1 Pack
  • Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
  • Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
  • Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
  • Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
  • Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth

3. It follows CNAMEs

If the requested name is an alias, CAA processing follows the CNAME to its target. The target’s CAA policy can therefore decide whether issuance is allowed. An alias that points into a service provider’s domain may be affected by records outside the zone you normally edit. A CNAME loop or an unreachable target can prevent the CA from obtaining a usable policy.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

4. It interprets the matching tags

The usual authorization tags are issue for ordinary certificates, issuewild for wildcard certificates and iodef for a reporting destination. A record consists of a flag, a tag and a value.

Component Meaning Example
Flag 0 is non-critical. 1 is issuer-critical; a CA that does not understand a critical property must reject issuance. 0
issue Authorizes a named CA to issue non-wildcard certificates. issue "letsencrypt.org"
issuewild Sets authorization for wildcard issuance and should be checked deliberately for a request such as *.example.com. issuewild "letsencrypt.org"
iodef Publishes a reporting contact or endpoint for policy violation reports; it does not itself authorize issuance. iodef "mailto:security@example.com"

DigiCert’s syntax example is example.com. CAA 0 issue "quovadisglobal.com". The trailing dot identifies the DNS name as fully qualified; DNS control panels may add it automatically.

Correct CAA examples for common issuers

Let’s Encrypt

The documented Let’s Encrypt issuer value is letsencrypt.org. A basic record is:

example.com. CAA 0 issue "letsencrypt.org"

For a wildcard request, publish and verify the wildcard policy explicitly:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Rank #3
BladeHawks RGB Gaming Mouse Pad Extra Large Extended 31.5x12 Inch-Black
  • 【Large size】:Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
  • 【LED backlight mouse pad】:Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
  • 【Anti-slip rubber base】:Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
  • 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
  • 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
example.com. CAA 0 issuewild "letsencrypt.org"

Keep an ordinary issue record if you also issue non-wildcard names. Confirm that the exact requested name does not have a closer CAA set that excludes Let’s Encrypt.

DigiCert

DigiCert documentation uses issuer identifiers including digicert.com. A corresponding ordinary-certificate record is:

example.com. CAA 0 issue "digicert.com"

Use the issuer value specified by the DigiCert product or account documentation for your request; different services can document related identifiers. Do not substitute a brand name from memory, because CAA matching uses the identifier published by the CA.

Step-by-step workflow for fixing an issuance error

  1. Capture the complete request. Write down the CA, the common name, every SAN, and whether the request contains a wildcard. Automated clients often request more names than the visible website address.
  2. Start with the exact hostname. Query CAA at each requested FQDN, then query each parent label. With a command-line DNS client, examples are dig CAA www.example.com and dig CAA example.com. Repeat against the authoritative nameservers when possible, not only a local recursive resolver.
  3. Identify the authoritative record set. Determine which nameserver is authoritative for the zone and whether a closer subdomain has its own CAA records. A parent record is irrelevant when a child name publishes a restrictive set.
  4. Trace aliases. Query for CNAME at the requested name. Follow the target and inspect its CAA records and ancestors. Resolve any CNAME chain or loop before changing the policy.
  5. Compare the value with the CA’s identifier. A restrictive set must contain the issuer value required by the CA, such as letsencrypt.org or digicert.com. If another CA is the only value, add a separate authorization for the intended CA or remove the restriction only if your security policy allows it.
  6. Check wildcard handling. For *.example.com, inspect issuewild at the effective policy location. Do not assume that a record you intended for ordinary names covers a wildcard request; verify the exact tag and name evaluated by the CA.
  7. Publish the smallest correct change. Add the intended issuer to the existing set rather than deleting unrelated controls. Preserve valid reporting records and any authorizations still needed by other certificates.
  8. Test authoritative answers. Ask every authoritative nameserver for the CAA type. Answers should be consistent and usable. An unsupported CAA type must produce a successful DNS response with an empty answer, not an implementation error.
  9. Check DNSSEC and reachability. For SERVFAIL, validate the DNSSEC chain, signatures and DS records. Check nameserver uptime, firewall rules, anti-DDoS middleware and network paths for dropped CAA queries.
  10. Wait for convergence, then retry. CAA records are cached according to their TTL. Confirm that authoritative and recursive views agree before retrying. If the CA offers a staging environment, use it to distinguish a transient CAA failure from a persistent policy or DNS problem.

Diagnosing SERVFAIL, NOTIMP and timeouts

SERVFAIL

SERVFAIL usually indicates DNS infrastructure trouble rather than a missing authorization. DNSSEC validation failure is the most common cause: an expired signature, a mismatched DS record, a broken chain of trust or an unsigned-to-signed transition can make validators reject the answer. Inspect DNSSEC status at the parent and zone, and query more than one validating resolver.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Also test each authoritative nameserver directly. One server with stale data, a broken zone load or an intermittent network path can cause a CA to receive SERVFAIL even while another resolver appears healthy. Correct the zone or DNSSEC configuration, wait for the corrected data to propagate, and then repeat the CAA query.

Rank #4
Sale
Vaydeer Wrist Rest for Keyboard and Mouse, Computer Ergonomic Wrist Support Pad, Soft Memory Foam Arm Cushion for Desk, Palm Hand Office Laptop Typing
  • 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
  • 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
  • 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
  • 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
  • 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.

NOTIMP or another error for CAA

NOTIMP means “not implemented.” An authoritative server that does not recognize the CAA record type may return this error, but RFC guidance requires an unsupported type to return NOERROR with an empty answer. A CA cannot safely treat NOTIMP as proof that no policy exists. Escalate the behavior to the DNS provider or move the zone to authoritative service that correctly handles CAA queries.

Timeouts

A timeout means the CA did not receive a usable response. Investigate firewalls, rate limits, middleboxes, anti-DDoS systems and unreachable or overloaded authoritative nameservers. Permit ordinary DNS traffic to every authoritative server and test from outside your own network. A local successful lookup does not prove that all public resolvers and CA networks can reach the zone.

CNAME loop or target conflict

A CNAME loop prevents the CA from reaching a final name. A valid target can still block issuance when its CAA set authorizes a different CA. Break loops, confirm the intended target, and arrange policy at the effective target or at a closer name that the CA will evaluate.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Wildcard mismatch

Wildcard requests have their own policy check through issuewild. A record that authorizes a CA for ordinary names may not satisfy a wildcard request if the effective wildcard policy names another issuer or does not contain the required authorization. Inspect the wildcard FQDN and its parent chain rather than checking only the apex record.

Reading common error messages

Error pattern Likely meaning Corrective action
CAA records forbid the requested CA An effective issue or issuewild set names another issuer. Add the intended CA as a separate authorization, or remove the restriction only when policy permits.
SERVFAIL while checking CAA DNSSEC validation, an unhealthy authoritative server or malformed DNS behavior is preventing a valid answer. Validate DNSSEC, query every authoritative server and repair zone or nameserver health.
NOTIMP or unsupported-type error The authoritative implementation mishandles an unknown or unsupported CAA type. Ask the DNS provider to return NOERROR with an empty answer or use a compliant authoritative service.
CAA query timeout Network filtering, middleware or an unavailable nameserver dropped the query. Check reachability, firewall policy, rate limits and nameserver uptime from external networks.
Alias or CNAME-related failure The CNAME chain loops, is unreachable or leads to a policy that excludes the CA. Resolve the chain and inspect CAA at the final target and its ancestors.
Wildcard authorization failure The effective wildcard policy does not authorize the requested CA. Check and correct the issuewild record for the exact wildcard name.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

TTL, caching and safe retries

CAA changes are not visible everywhere immediately. The record’s TTL controls how long recursive resolvers may cache the previous answer. After publishing a correction, verify the authoritative response first, then check representative recursive resolvers and wait for old TTLs to expire. Repeated retries before convergence can produce the same error and make a fixed policy appear broken.

Best Value
Sale
Under Desk Cable Management Tray No Drill, Metal Mesh Cable Management Under Desk with Clamp Mount, 2 Hole Cable Tray with Wire Management and Cord Organizer for Home Office Standing Desk
  • 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
  • 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
  • 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
  • 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
  • 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.

Use the CA’s staging or test environment when available. A successful staging check suggests that the DNS policy and infrastructure are now readable, while a continuing production failure may involve a separate account, validation or certificate-profile rule. A failed staging check keeps the investigation focused on DNS and CAA rather than production issuance quotas.

Operational practices that prevent future failures

  • Record the approved issuer identifier next to each certificate automation configuration; do not rely on a remembered brand name.
  • Track every SAN and wildcard in certificate inventory so a new name does not silently fall under a conflicting child policy.
  • Test CAA responses from all authoritative nameservers after DNS migrations, DNSSEC changes and provider incidents.
  • Keep ordinary and wildcard authorizations intentional. Review issuewild whenever wildcard automation is introduced or retired.
  • Document CNAME ownership. A service-controlled target can impose a CAA policy that your primary zone cannot override.
  • Monitor DNSSEC expiration, DS changes and nameserver availability; these failures can surface as CAA errors even when the records themselves are correct.
  • Use a non-critical flag unless you intentionally require every evaluating CA to understand a property. Flag 1 causes an issuer that does not understand the property to reject issuance.
  • Keep a rollback record of the prior CAA set, including TTL, so an accidental restriction can be restored without guessing.

CAA and S/MIME: a date-specific qualification

DigiCert began applying a CAA-checking change to S/MIME mailbox-domain processing on March 13, 2025 at 16:00 UTC. That operational change is specific to S/MIME processing. It does not make CAA mandatory for ordinary TLS certificates, for which DigiCert continues to state that CAA is not required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

When the CAA record is correct but issuance still fails

CAA only answers the question “Is this CA authorized by DNS?” Once that check succeeds, investigate the separate validation path reported by the CA: HTTP or DNS challenge reachability, email approval, organization documentation, account permissions, rate limits, identifier syntax and certificate-profile restrictions. Confirm that the error still names CAA before changing DNS again; deleting a valid policy will not repair a non-CAA validation failure.

For a persistent incident, preserve the exact timestamp, queried names, authoritative responses, DNSSEC status, CNAME chain and CA error text. Supplying that evidence to the DNS operator or CA support team avoids a generic “add a CAA record” response and makes it possible to isolate a broken nameserver, an unexpected parent policy or a CA-specific identifier mismatch.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.