Verify Namecheap SSL Certificate with DNS CNAME Record

by Fahim

HTTP file validation always fails at the worst possible moment—usually when your web server isn’t serving files yet or Cloudflare intercepts the request. You can skip the web server entirely and verify a Namecheap SSL certificate with a DNS CNAME record in less than five minutes.

I ran into this exact headache last week while setting up a standalone Sectigo/PositiveSSL cert for an API subdomain. The HTTP challenge failed with a 404 because the backend reverse proxy wasn’t fully wired up. Switching the domain validation method to DNS CNAME bypasses web server routing completely. You publish a specific hash string into your domain’s DNS zone, Sectigo queries it, and your certificate issues.

Terminal screen verifying a DNS CNAME record for Namecheap SSL validation
Terminal screen verifying a DNS CNAME record for Namecheap SSL validation

Why DNS CNAME Validation Beats HTTP and Email

When you activate an SSL certificate on Namecheap, you pick from three validation types: Email, HTTP-based (uploading a text file to .well-known/pki-validation/), or DNS-based (CNAME). Most developers click HTTP validation by default because it sounds straightforward. It isn’t.

HTTP validation breaks if:

  • Your DNS does not point to the live server yet.
  • You have aggressive redirect rules (forcing HTTPS before the cert exists creates an infinite loop).
  • A firewall or WAF blocks the Sectigo validation bot.
  • You are provisioning a certificate before spinning up the origin instance.

Email validation is just as painful because it sends approval tokens to admin addresses like admin@yourdomain.com or postmaster@yourdomain.com. If your custom mail routing is not active, you won’t get the email. If you need help with MX records, see our guide on how to route subdomain email with custom MX records in Namecheap.

DNS CNAME validation relies entirely on your authoritative nameserver. As long as you can edit DNS records, you can validate the certificate anywhere, anytime.

Step 1: Get Your CNAME Validation Values from Namecheap

Log in to your Namecheap account dashboard and locate your pending SSL certificate under the Product List or SSL Certificates tab. Click Manage next to the pending certificate.

If you already submitted the CSR with HTTP validation and it’s hanging, look for the dropdown menu labeled Edit methods or Validation method. Change it to DNS (CNAME). Namecheap will display two distinct values:

  • Host (or Name): A string starting with an underscore, followed by MD5-like hashes, ending in your domain (e.g., _2F8B7089C942D8E387123456789ABCDE.yourdomain.com.).
  • Target (or Points To / Value): A Comodo/Sectigo validation URL, ending in .sectigo.com. or .comodoca.com. (e.g., _4F123ABCDEF1234567890ABCDEF12345.5a8b7c9d0e.sectigo.com.).

Keep this browser tab open. Do not close it until you copy these strings over.

Step 2: Format the Host Value (The Most Common Pitfall)

Here is where almost everyone messes up. Different DNS managers handle fully qualified domain names (FQDN) differently. Namecheap shows you the full host string, which includes your domain name at the end.

If you use Namecheap BasicDNS or PremiumDNS, Namecheap automatically appends your domain name to any Host field you save. If you paste the full string into Namecheap’s DNS manager, you will end up with this broken record:

# What you pasted:
_2F8B7089C942D8E387123456789ABCDE.yourdomain.com # What Namecheap actually published:
_2F8B7089C942D8E387123456789ABCDE.yourdomain.com.yourdomain.com

When Sectigo queries the DNS server for validation, it looks for the single-domain record. It finds nothing, and your validation stays stuck in “Pending” indefinitely.

Here is the rule:

  • Namecheap DNS: Strip your root domain and the dot. Only paste the underscore and the first hash into the Host field (e.g., _2F8B7089C942D8E387123456789ABCDE).
  • Subdomains: If the cert is for api.yourdomain.com, strip only the root domain, leaving _2F8B7089C942D8E387123456789ABCDE.api in the Host field. Check our tutorial on how to point a Namecheap subdomain for a deeper look at host routing.
  • External DNS (Cloudflare, DigitalOcean, Route53): Most modern DNS panels strip the domain automatically, but always verify before saving.

Step 3: Add the CNAME Record in Namecheap DNS

If your domain’s nameservers are set to Namecheap BasicDNS, you will add the record right inside Namecheap. If you are pointing your root domain using ALIAS or CNAME records elsewhere, make sure you understand the difference by reading our breakdown on A record vs CNAME for root domains in Namecheap DNS.

Here are the steps inside Namecheap:

  1. Go to Domain List and click Manage next to your domain.
  2. Select the Advanced DNS tab at the top.
  3. Scroll down to the Host Records section and click Add New Record.
  4. Set the Type to CNAME Record.
  5. In the Host field, enter the stripped hash string (without .yourdomain.com).
  6. In the Target field, paste the full destination value provided by Namecheap (e.g., _4F123ABCDEF1234567890ABCDEF12345.5a8b7c9d0e.sectigo.com.). Ensure there are no leading or trailing spaces.
  7. Set TTL to Automatic or 1 min (if available) to speed up resolution.
  8. Click the green checkmark icon to save.

If you’re using third-party DNS like Cloudflare, remember to set the proxy status to DNS Only (gray cloud). Cloudflare’s orange-cloud proxy returns its own proxy IPs and can interfere with CNAME validation queries.

Step 4: Verify the Record with Dig Before Waiting on Sectigo

Do not sit around refreshing the Namecheap dashboard hoping it works. You can verify whether the record is live worldwide using your local terminal. Open your terminal and run dig against Google’s public resolver:

# Replace with your actual full host string and domain
dig +short CNAME _2F8B7089C942D8E387123456789ABCDE.yourdomain.com @8.8.8.8

If your record is active, terminal output will print the target address immediately:

# Output should return the Sectigo target:
_4F123ABCDEF1234567890ABCDEF12345.5a8b7c9d0e.sectigo.com.

If the command outputs nothing, your record has not propagated, or you made the duplication error in Step 2. You can test if you accidentally doubled the domain by querying the doubled record:

dig +short CNAME _2F8B7089C942D8E387123456789ABCDE.yourdomain.com.yourdomain.com @8.8.8.8

If that command returns the target, you know you duplicated the domain name inside the Host field. Go back into Advanced DNS, strip .yourdomain.com from the Host field, and save it again.

If you are on Windows without BIND utilities installed, use Resolve-DnsName in PowerShell instead:

Resolve-DnsName -Name "_2F8B7089C942D8E387123456789ABCDE.yourdomain.com" -Type CNAME -Server 8.8.8.8

You can also confirm via web tools like WhatsMyDNS or Google’s Public DNS Lookup if you prefer not to touch the CLI.

Step 5: Trigger the Validation Check

Once dig confirms the record returns the expected Sectigo host, head back to your Namecheap SSL management panel.

Sectigo runs automated checks periodically (usually every 15 to 30 minutes), but you do not need to wait. In the SSL details screen, click the button labeled Resend Validation Email / Retry DCV (or Re-check DCV).

This tells Sectigo’s validation servers to query your DNS record immediately. In my tests, the status flipped from Pending Validation to Issued in approximately 45 seconds.

Once issued, download the certificate archive from Namecheap. It contains two files:

  • yourdomain_com.crt (Your primary SSL certificate)
  • yourdomain_com.ca-bundle (The intermediate and root chain certificates)

Step 6: Combine the Certificate and Bundle (Nginx / Apache Setup)

Before installing your newly issued certificate on your server, you need to combine the primary certificate and the intermediate bundle into a single file if you are using Nginx or Caddy. If you skip this, mobile browsers and older clients will throw SSL trust errors.

Here is what I ran locally to prepare the full-chain certificate before uploading it to my server:

# Move into the folder where you unpacked the Namecheap zip
cd ~/Downloads/ssl_certs # Concatenate the main certificate and the CA bundle into a fullchain file
cat yourdomain_com.crt yourdomain_com.ca-bundle > yourdomain_com_fullchain.crt

Then, verify that the bundle order is correct using openssl. You should see your domain certificate first, followed by Sectigo’s intermediate certs:

openssl crt -in yourdomain_com_fullchain.crt -text -noout | grep -E "Subject:|Issuer:"

In your Nginx configuration, point ssl_certificate to your combined yourdomain_com_fullchain.crt file and ssl_certificate_key to the private key you generated when creating your CSR:

server { listen 443 ssl http2; server_name yourdomain.com; ssl_certificate /etc/ssl/certs/yourdomain_com_fullchain.crt; ssl_certificate_key /etc/ssl/private/yourdomain_com.key; ssl_protocols TLSv1.2 TLSv1.3; ssl_ciphers HIGH:!aNULL:!MD5; location / { proxy_pass http://127.0.0.1:3000; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; }
}

Once your web server is live, verify that internal asset paths match HTTPS so you avoid mixed content errors. If you run into mixed protocol warnings on WordPress, check our guide to fix WordPress mixed content warnings after SSL.

Can You Delete the CNAME Record After Issuance?

Yes. Once your certificate status is Issued and you have downloaded your files, the CNAME record is no longer needed by Sectigo for your certificate to stay active. It only exists to prove ownership at the exact moment of issuance.

However, leaving the CNAME record in place does not hurt anything. If you use auto-renewal features through Namecheap or plan to re-issue the certificate with the exact same key next year, keeping the record intact might save you a step during renewal.

If you prefer a clean DNS zone with zero stale entries, you can safely delete the record from your Advanced DNS tab immediately after downloading your cert.

Frequently Asked Questions

How long does CNAME validation take to issue a Namecheap SSL?

Once the DNS record resolves globally, issuance takes between 1 and 5 minutes. If it takes longer than 15 minutes, your Host field is likely misconfigured or pointing to a duplicated domain name.

Does CNAME verification work for Wildcard SSL certificates?

Yes. In fact, DNS validation (via CNAME or TXT) is the primary method allowed by Certificate Authorities like Sectigo and Let’s Encrypt for Wildcard certificates (*.yourdomain.com). HTTP file validation cannot be used for wildcards under CA/Browser Forum rules. For wildcards, consult our guide on wildcard subdomain DNS in Namecheap.

What should I do if the Namecheap status is stuck on “Processing”?

Click into the certificate details, switch the validation method to Email, wait 10 seconds, and switch it back to DNS (CNAME). This forces Namecheap to generate a fresh token pair. Update your DNS record with the new values, verify with dig, and hit Retry DCV.

Can I validate my SSL via DNS if my domain is hosted on Cloudflare?

Yes. Add the CNAME record in Cloudflare’s DNS tab. You must make sure the proxy toggle is set to DNS Only (gray cloud). If it is proxied (orange cloud), Sectigo’s automated scanners will fail to resolve the underlying CNAME record directly.

Next Steps

Now that your SSL certificate is issued and verified, check that your DNS security records are in order. If you send system emails or transactional receipts from this domain, learn how to add a 2048-bit DKIM TXT record in Namecheap DNS so your messages don’t drop straight into spam filters.

all_in_one_marketing_tool