<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: shehabmedhat1</title>
    <description>The latest articles on DEV Community by shehabmedhat1 (@shehabmedhat1).</description>
    <link>https://dev.to/shehabmedhat1</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4247733%2F95f07867-7ae8-4f1b-921c-c54b85c1feef.png</url>
      <title>DEV Community: shehabmedhat1</title>
      <link>https://dev.to/shehabmedhat1</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shehabmedhat1"/>
    <language>en</language>
    <item>
      <title>How to Generate Free Wildcard SSL Certificates Without Using CLI (ACME v2 Web Guide</title>
      <dc:creator>shehabmedhat1</dc:creator>
      <pubDate>Mon, 16 Nov 2026 12:18:17 +0000</pubDate>
      <link>https://dev.to/shehabmedhat1/how-to-generate-free-wildcard-ssl-certificates-without-using-cli-acme-v2-web-guide-4np6</link>
      <guid>https://dev.to/shehabmedhat1/how-to-generate-free-wildcard-ssl-certificates-without-using-cli-acme-v2-web-guide-4np6</guid>
      <description>&lt;p&gt;Securing a root domain along with all its subdomains (&lt;code&gt;*.example.com&lt;/code&gt;) usually means SSH-ing into a server, installing Certbot, and wrestling with terminal flags or DNS plugins.&lt;/p&gt;

&lt;p&gt;While CLI tools are great for automated pipelines, sometimes you just need a quick Wildcard certificate for a staging environment, shared hosting (cPanel), or a custom appliance where installing ACME clients isn't practical.&lt;/p&gt;

&lt;p&gt;Here is a straightforward, browser-based workflow to issue a free &lt;strong&gt;Let's Encrypt Wildcard SSL certificate&lt;/strong&gt; using the ACME v2 protocol without touching the command line.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why Wildcard Certificates Require &lt;code&gt;DNS-01&lt;/code&gt; Verification
&lt;/h2&gt;

&lt;p&gt;Standard single-domain certificates can be verified via &lt;code&gt;HTTP-01&lt;/code&gt; (placing a file in &lt;code&gt;/.well-known/acme-challenge/&lt;/code&gt;). However, Let's Encrypt strictly requires &lt;strong&gt;&lt;code&gt;DNS-01&lt;/code&gt; challenge verification&lt;/strong&gt; for Wildcard domains (&lt;code&gt;*.yourdomain.com&lt;/code&gt;) to prove you control the entire DNS zone.&lt;/p&gt;




&lt;h2&gt;
  
  
  Step-by-Step: Issuing a Wildcard SSL via Web ACME v2
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Define Your Domain Scope
&lt;/h3&gt;

&lt;p&gt;When generating your certificate request, include both the bare root domain and the wildcard entry so browsers trust both:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;example.com&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;*.example.com&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can follow the complete visual walkthrough on the &lt;a href="https://sslfree.site/guides.php" rel="noopener noreferrer"&gt;SSL Free Site Guides&lt;/a&gt; if you want to see how each ACME step behaves under the hood.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Add the &lt;code&gt;_acme-challenge&lt;/code&gt; TXT Record
&lt;/h3&gt;

&lt;p&gt;Once the ACME server generates your challenge token, log into your DNS provider (Cloudflare, Namecheap, Route53, etc.) and create a new &lt;strong&gt;TXT record&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Type:&lt;/strong&gt; &lt;code&gt;TXT&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Host / Name:&lt;/strong&gt; &lt;code&gt;_acme-challenge&lt;/code&gt; &lt;em&gt;(Note: Most DNS panels automatically append &lt;code&gt;.example.com&lt;/code&gt;)&lt;/em&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Value:&lt;/strong&gt; &lt;code&gt;&amp;lt;the-verification-token-provided&amp;gt;&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;TTL:&lt;/strong&gt; Lowest possible (e.g., &lt;code&gt;60&lt;/code&gt; seconds or &lt;code&gt;Auto&lt;/code&gt;)&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  3. Wait for DNS Propagation &amp;amp; Verify
&lt;/h3&gt;

&lt;p&gt;Before triggering the ACME validation check, make sure the TXT record is globally visible. You can verify this via &lt;code&gt;dig&lt;/code&gt; or any DNS lookup tool:&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
bash
dig -t TXT _acme-challenge.example.com +short
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
      <category>ssl</category>
      <category>devops</category>
      <category>security</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
