<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Coder Legion - Recent posts tagged domain</title>
<link>https://coderlegion.com/tag/domain</link>
<description>Powered by Question2Answer</description>
<item>
<title>Filters and reports: Semrush metrics (AS, backlinks, traffic)</title>
<link>https://coderlegion.com/23622/filters-and-reports-semrush-metrics-as-backlinks-traffic</link>
<description>&lt;p&gt;&lt;a rel=&quot;nofollow&quot; href=&quot;https://karma.domains/&quot;&gt;Karma.Domains&lt;/a&gt; base filters now include a Semrush tab with two panels: Backlinks — Authority Score (AS) (0–100), backlinks, referring domains and IPs, plus EDU/GOV links — and Traffic Analytics — visits, unique visitors, desktop/mobile share, and channel volumes (Direct, Search Organic/Paid, Referral, Social, Mail). The same Semrush signals are available in the Combined SEO filter (AS, backlinks, referring domains, and visits alongside other providers).&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://karma.domains/assets/images/updates/semrush-filters.avif&quot; alt=&quot;&quot;&gt;&lt;/p&gt;
&lt;p&gt;Each domain report includes a Semrush tab with the full backlink block and Traffic Analytics summary (KPIs, month-over-month changes, and traffic sources). List tables offer AS, BL, RD, and traffic columns for sorting and quick comparison. The AI filter also understands Semrush when you name the vendor or ask for AS in natural language.&lt;/p&gt;
&lt;p&gt;The &lt;a rel=&quot;nofollow&quot; href=&quot;https://karma.domains/en/domain-authority-checker/&quot;&gt;free Domain Authority Checker&lt;/a&gt; now returns Semrush data as well: Authority Score (AS), backlinks, and referring domains — up to 10 domains per run, no sign-up required — so you can screen candidates side by side with Ahrefs, Moz, Open PageRank, and Karma Domain Metric.&lt;/p&gt;
</description>
<category>Articles</category>
<guid isPermaLink="true">https://coderlegion.com/23622/filters-and-reports-semrush-metrics-as-backlinks-traffic</guid>
<pubDate>Tue, 28 Jul 2026 07:10:41 +0000</pubDate>
</item>
<item>
<title>Do You Own Your Website? Code &amp; Domain Ownership Explained</title>
<link>https://coderlegion.com/21099/do-you-own-your-website-code-domain-ownership-explained</link>
<description>
&lt;h1&gt;Do You Own Your Website? Code, Domain &amp;amp; Hosting Ownership Explained&lt;/h1&gt;
&lt;p class=&quot;post-byline&quot;&gt;
    &lt;span&gt; Ownership Guide&lt;/span&gt; &amp;middot;     Updated June 2026     &amp;middot; 10 min read    &amp;middot; by Jacob Campbell
&lt;/p&gt;

&lt;p class=&quot;article-intro&quot;&gt;&lt;/p&gt;&lt;p&gt;I'm Jacob Campbell, and I've watched this exact scenario play out too many times: a business owner discovers, usually at the worst possible moment, that they don't actually own the website they've been paying for. With most website builders and a surprising number of agency contracts, you're not buying a site &amp;mdash; you're renting access to one. Stop paying, and it can vanish overnight. Real ownership means you hold three things outright: the code, the domain, and the hosting account, with the freedom to move or change any of them without asking permission. This guide explains precisely what ownership means in 2026, the red flags that you don't have it, and how a custom flat-fee build puts you back in control of your most important marketing asset.&lt;/p&gt;

&lt;h2&gt;Key facts&lt;/h2&gt;
&lt;div class=&quot;post-stats&quot;&gt;
        &lt;div class=&quot;post-stat&quot;&gt;&lt;div class=&quot;v&quot;&gt;100%&lt;/div&gt;&lt;div class=&quot;l&quot;&gt;Code ownership, flat fee&lt;/div&gt;&lt;/div&gt;
        &lt;div class=&quot;post-stat&quot;&gt;&lt;div class=&quot;v&quot;&gt;$0&lt;/div&gt;&lt;div class=&quot;l&quot;&gt;Locked-in platform fees&lt;/div&gt;&lt;/div&gt;
        &lt;div class=&quot;post-stat&quot;&gt;&lt;div class=&quot;v&quot;&gt;You&lt;/div&gt;&lt;div class=&quot;l&quot;&gt;Hold domain &amp;amp; hosting&lt;/div&gt;&lt;/div&gt;
        &lt;div class=&quot;post-stat&quot;&gt;&lt;div class=&quot;v&quot;&gt;Anytime&lt;/div&gt;&lt;div class=&quot;l&quot;&gt;Move or edit freely&lt;/div&gt;&lt;/div&gt;
    &lt;/div&gt;

&lt;h2&gt;The three things real ownership requires&lt;/h2&gt;
&lt;p&gt;Owning your website means three assets are genuinely yours. The &lt;strong&gt;code&lt;/strong&gt; &amp;mdash; the actual files that make the site run, in a form you can download and deploy elsewhere. The &lt;strong&gt;domain&lt;/strong&gt; &amp;mdash; your address, registered in your name in a registrar account you can log into. And the &lt;strong&gt;hosting account&lt;/strong&gt; &amp;mdash; the server where the files live, under your billing and control. If all three are yours, you can change hosts, switch developers, or redesign at will. If even one is locked to someone else's platform, you're renting, no matter what the invoice calls it.&lt;/p&gt;&lt;h2&gt;Renting vs owning: the difference that costs thousands&lt;/h2&gt;
&lt;p&gt;Builders like Wix and Squarespace keep your site inside their walls by design. You pay monthly, and you cannot export the real, working code to run anywhere else &amp;mdash; when the payments stop, the site goes dark. A custom website is the inverse: you receive the complete codebase, host it wherever you choose, and pay no platform fee ever. Across a few years that's the difference between thousands of dollars in recurring rent and a one-time asset you control &amp;mdash; plus the peace of mind that no vendor can switch off your business.&lt;/p&gt;&lt;h2&gt;Warning signs you don't own your site&lt;/h2&gt;
&lt;p&gt;Treat any of these as a red flag: you can't download your full source code; the domain is registered under an agency or developer rather than your business; you're locked into a proprietary builder with no real export; your site would go offline if you cancelled a monthly subscription; or you need someone's permission to make a change. I've onboarded clients who hit several of these at once &amp;mdash; and the rescue is always harder than getting it right from the start would have been.&lt;/p&gt;&lt;h2&gt;How custom code guarantees ownership&lt;/h2&gt;
&lt;p&gt;A custom build hands you the entire codebase on delivery. The domain is registered in your name, the site is deployed to hosting you control, and there's no proprietary layer to trap you. You can edit it, scale it, hand it to another developer, or migrate it to any host on earth &amp;mdash; and because it's standard code, any competent developer can pick it up. That portability &lt;em&gt;is&lt;/em&gt; ownership. It's included in every flat-fee project I deliver, in writing, not as an upsell.&lt;/p&gt;&lt;h2&gt;How to check what you own right now&lt;/h2&gt;
&lt;p&gt;You can audit your own situation in ten minutes. Log into your domain registrar &amp;mdash; is the registrant your business name, with you as admin contact? Ask your provider for a full export of your site's source code and see whether you actually receive runnable files. Check whether your site survives a hypothetical cancellation of every monthly fee. If any answer is uncomfortable, you've found a dependency worth fixing before it becomes an emergency.&lt;/p&gt;&lt;h2&gt;Questions to ask before you sign&lt;/h2&gt;
&lt;p&gt;Before hiring anyone, get written answers to four questions: &lt;em&gt;Do I own the code and hosting after delivery? Is the domain registered in my name? Are there any monthly platform fees? Can I move the site to another host or developer later?&lt;/em&gt; A trustworthy developer answers all four in your favour and documents it in the contract. (My &lt;a href=&quot;/blog/how-to-hire-a-website-developer&quot;&gt;hiring guide&lt;/a&gt; covers the full list of terms that protect you.)&lt;/p&gt;&lt;h2&gt;Sources &amp;amp; further reading&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;&lt;a href=&quot;https://www.icann.org/resources/pages/name-holder-2013-05-03-en&quot; target=&quot;_blank&quot; rel=&quot;noopener nofollow&quot;&gt;ICANN &amp;mdash; Registrant (domain owner) rights and responsibilities&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href=&quot;/blog/how-to-hire-a-website-developer&quot;&gt;BuiltToWinWeb &amp;mdash; How to hire a developer (contract terms)&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;Ownership terms described here reflect my own current BuiltToWinWeb delivery standard as of June 2026.&lt;/p&gt;
&lt;h2&gt;Related services&lt;/h2&gt;
&lt;div class=&quot;post-related&quot;&gt;
        &lt;a href=&quot;/services/custom-PHP-website&quot;&gt;
        &lt;div class=&quot;t&quot;&gt;Own your website outright&lt;/div&gt;
        &lt;div class=&quot;d&quot;&gt;Flat-fee custom builds with 100% code ownership and no platform lock-in.&lt;/div&gt;
    &lt;/a&gt;
        &lt;a href=&quot;/website-hosting-and-domain/&quot;&gt;
        &lt;div class=&quot;t&quot;&gt;Hosting &amp;amp; domain setup&lt;/div&gt;
        &lt;div class=&quot;d&quot;&gt;Keep your domain and hosting registered in your own name.&lt;/div&gt;
    &lt;/a&gt;
        &lt;a href=&quot;/blog/how-to-hire-a-website-developer&quot;&gt;
        &lt;div class=&quot;t&quot;&gt;How to hire a developer&lt;/div&gt;
        &lt;div class=&quot;d&quot;&gt;The questions to ask before you sign any web project.&lt;/div&gt;
    &lt;/a&gt;
    &lt;/div&gt;

&lt;h2&gt;Frequently asked questions&lt;/h2&gt;
&lt;h3&gt;Do I own my website with a website builder?&lt;/h3&gt;
&lt;p&gt;Usually not. With builders like Wix or Squarespace, your site stays on their platform and cannot be exported as real, movable code. If you stop paying, the site typically goes offline. You are renting, not owning.&lt;/p&gt;
&lt;h3&gt;What do I need to fully own my website?&lt;/h3&gt;
&lt;p&gt;Three things in your control: the source code (as downloadable, runnable files), the domain registered in your business name, and the hosting account under your billing. With all three you can move hosts, switch developers, or redesign without anyone's permission.&lt;/p&gt;
&lt;h3&gt;Does a custom website mean I own the code?&lt;/h3&gt;
&lt;p&gt;Yes. With a custom flat-fee build you receive the complete codebase on delivery and own it outright forever, with no proprietary platform and no monthly lock-in fees.&lt;/p&gt;
&lt;h3&gt;How do I know if I really own my domain?&lt;/h3&gt;
&lt;p&gt;Log into your registrar and confirm the registrant and admin contact is your own name or business, not an agency or builder. If you cannot log in and transfer it yourself, you may not truly control it.&lt;/p&gt;
&lt;h3&gt;Can I move my website to another host later?&lt;/h3&gt;
&lt;p&gt;If you own the code and domain, yes &amp;mdash; you can move to any host at any time. If your site is locked to a proprietary builder, moving usually means rebuilding from scratch.&lt;/p&gt;
&lt;h3&gt;How can I check what I currently own?&lt;/h3&gt;
&lt;p&gt;Verify the registrant on your domain, request a full export of your source code and confirm you receive runnable files, and check whether your site would survive cancelling every monthly fee. Any uncomfortable answer is a dependency worth fixing.&lt;/p&gt;

&lt;div class=&quot;post-cta&quot;&gt;
    &lt;h2&gt;Own your website 100%&lt;/h2&gt;
    &lt;p&gt;Get a custom, flat-fee website you own outright &amp;mdash; code, domain, and hosting all in your control, with no monthly platform fees.&lt;/p&gt;
    &lt;a class=&quot;btn&quot; href=&quot;/free-quote/&quot;&gt;Get my free quote&lt;/a&gt;
&lt;/div&gt;
</description>
<category>Other</category>
<guid isPermaLink="true">https://coderlegion.com/21099/do-you-own-your-website-code-domain-ownership-explained</guid>
<pubDate>Sun, 28 Jun 2026 07:45:45 +0000</pubDate>
</item>
<item>
<title>How to Configure Nginx as an HTTPS Proxy Server?</title>
<link>https://coderlegion.com/18996/how-to-configure-nginx-as-an-https-proxy-server</link>
<description>
&lt;p&gt;Hello, I'm Ganesh. I'm building &lt;em&gt;git-lrc&lt;/em&gt;, an AI code reviewer that runs on every commit. It is free, unlimited, and source-available on Github. &lt;a href=&quot;https://github.com/HexmosTech/git-lrc&quot; rel=&quot;noopener noreferrer nofollow&quot;&gt;Star Us&lt;/a&gt; to help devs discover the project. Do give it a try and share your feedback for improving the product.&lt;/p&gt;

&lt;p&gt;In previous article we could able to setup basic nginx server and server simple html page. &lt;/p&gt;

&lt;p&gt;Now let's setup https for our nginx server.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Requirements&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;Before we start setting up https we should do the following:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Buy a domain name from any registrar.&lt;/li&gt;
&lt;li&gt;Set up dns records to point to our server ip.&lt;/li&gt;
&lt;li&gt;Setup Certificate for our domain name.&lt;/li&gt;
&lt;li&gt;Install nginx on our server.&lt;/li&gt;
&lt;li&gt;Set up nginx server to serve our website.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Buying Domain Name
&lt;/h2&gt;

&lt;p&gt;We can buy domain name from any registrar like Namecheap, GoDaddy, etc. &lt;/p&gt;

&lt;p&gt;It depends on which name it is and the charges will be around &lt;/p&gt;

&lt;h2&gt;
  
  
  Setting Up DNS Records
&lt;/h2&gt;

&lt;p&gt;Once buy setup the dns records to point to our server ip.&lt;/p&gt;

&lt;p&gt;Example:&lt;br&gt;
For your server the ip address is [IP_ADDRESS]. &lt;br&gt;
And your domain name is [EMAIL_ADDRESS]&lt;/p&gt;

&lt;p&gt;So, you need to set up a dns record to point to your server ip.&lt;/p&gt;
&lt;h2&gt;
  
  
  Setting up Certificate
&lt;/h2&gt;

&lt;p&gt;Now let's setup certificate for our domain name.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;example.com&lt;/code&gt; &lt;/p&gt;

&lt;p&gt;so, we setup&lt;br&gt;
&lt;/p&gt;

&lt;div class=&quot;highlight js-code-highlight&quot;&gt;
&lt;pre class=&quot;highlight shell&quot;&gt;&lt;code&gt;&lt;span class=&quot;nb&quot;&gt;sudo &lt;/span&gt;certbot &lt;span class=&quot;nt&quot;&gt;--nginx&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;-d&lt;/span&gt; &lt;span class=&quot;sb&quot;&gt;`&lt;/span&gt;example.com&lt;span class=&quot;sb&quot;&gt;`&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;--email&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;[&lt;/span&gt;EMAIL_ADDRESS] &lt;span class=&quot;nt&quot;&gt;--agree-tos&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;--no-eff-email&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Here is simple workflow on how certificate is fetched and how &lt;/p&gt;

&lt;p&gt;&lt;a rel=&quot;nofollow&quot; href=&quot;https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fftruvgc7r97ocn2ggu19.png&quot; class=&quot;article-body-image-wrapper&quot;&gt;&lt;img src=&quot;https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fftruvgc7r97ocn2ggu19.png&quot; alt=&quot;&quot;&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key generation&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;The Certbot generates a private key and a CSR (Certificate Signing Request) entirely on your machine. &lt;/p&gt;

&lt;p&gt;The private key is the core security guarantee.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;HTTP-01 Challenge&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;Let's Encrypt needs to verify you actually control &lt;code&gt;example.com&lt;/code&gt;. It sends Certbot a random token. &lt;/p&gt;

&lt;p&gt;Certbot places it at:&lt;br&gt;
&lt;/p&gt;

&lt;div class=&quot;highlight js-code-highlight&quot;&gt;
&lt;pre class=&quot;highlight plaintext&quot;&gt;&lt;code&gt;/var/www/html/.well-known/acme-challenge/&amp;lt;random-token&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Nginx (already running on port 80) serves this file publicly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Let's Encrypt fetches the token&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;LE makes a plain HTTP request to &lt;code&gt;&lt;a href=&quot;http://example.com/.well-known/acme-challenge/&quot; rel=&quot;nofollow&quot;&gt;http://example.com/.well-known/acme-challenge/&lt;/a&gt;&amp;lt;token&amp;gt;&lt;/code&gt;. &lt;/p&gt;

&lt;p&gt;If it gets the right response back, it's satisfied that you own the domain. &lt;/p&gt;

&lt;p&gt;This is why DNS must be pointing to your server before you run Certbot &amp;mdash; if the domain pointed elsewhere, LE would fetch the token from the wrong machine and the challenge would fail.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Certificate issued &amp;amp; saved&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;LE signs and returns your certificate. &lt;/p&gt;

&lt;p&gt;Certbot saves four files to &lt;code&gt;/etc/letsencrypt/live/example.com/&lt;/code&gt;:&lt;/p&gt;

&lt;div class=&quot;table-wrapper-paragraph&quot;&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;File&lt;/th&gt;
&lt;th&gt;What it is&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;fullchain.pem&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Your cert + intermediate CA chain (this is what Nginx uses)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;privkey.pem&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Your private key (Nginx uses this too)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;cert.pem&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Just your cert alone&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;chain.pem&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Just the CA chain alone&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Nginx config is rewritten&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;Certbot patches your &lt;code&gt;server&lt;/code&gt; block to add the &lt;code&gt;listen 443 ssl&lt;/code&gt; lines and the cert paths, and adds a new &lt;code&gt;server { listen 80; }&lt;/code&gt; block that redirects all HTTP traffic to HTTPS. &lt;/p&gt;

&lt;p&gt;Then it reloads Nginx for you.&lt;/p&gt;

&lt;h2&gt;
  
  
  Setting up with nginx
&lt;/h2&gt;

&lt;p&gt;Assuming your application running in local host 8090. and you are setting up https for your domain name example.com.&lt;br&gt;
&lt;/p&gt;

&lt;div class=&quot;highlight js-code-highlight&quot;&gt;
&lt;pre class=&quot;highlight conf&quot;&gt;&lt;code&gt;&lt;span class=&quot;n&quot;&gt;server&lt;/span&gt; {
    &lt;span class=&quot;n&quot;&gt;listen&lt;/span&gt; &lt;span class=&quot;m&quot;&gt;443&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;ssl&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;http2&lt;/span&gt;;
    &lt;span class=&quot;n&quot;&gt;server_name&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;example&lt;/span&gt;.&lt;span class=&quot;n&quot;&gt;com&lt;/span&gt;;

    &lt;span class=&quot;n&quot;&gt;ssl_certificate&lt;/span&gt;     /&lt;span class=&quot;n&quot;&gt;etc&lt;/span&gt;/&lt;span class=&quot;n&quot;&gt;letsencrypt&lt;/span&gt;/&lt;span class=&quot;n&quot;&gt;live&lt;/span&gt;/&lt;span class=&quot;n&quot;&gt;example&lt;/span&gt;.&lt;span class=&quot;n&quot;&gt;com&lt;/span&gt;/&lt;span class=&quot;n&quot;&gt;fullchain&lt;/span&gt;.&lt;span class=&quot;n&quot;&gt;pem&lt;/span&gt;;
    &lt;span class=&quot;n&quot;&gt;ssl_certificate_key&lt;/span&gt; /&lt;span class=&quot;n&quot;&gt;etc&lt;/span&gt;/&lt;span class=&quot;n&quot;&gt;letsencrypt&lt;/span&gt;/&lt;span class=&quot;n&quot;&gt;live&lt;/span&gt;/&lt;span class=&quot;n&quot;&gt;example&lt;/span&gt;.&lt;span class=&quot;n&quot;&gt;com&lt;/span&gt;/&lt;span class=&quot;n&quot;&gt;privkey&lt;/span&gt;.&lt;span class=&quot;n&quot;&gt;pem&lt;/span&gt;;

    &lt;span class=&quot;c&quot;&gt;# All requests &amp;mdash; public, no auth
&lt;/span&gt;    &lt;span class=&quot;n&quot;&gt;location&lt;/span&gt; / {
        &lt;span class=&quot;n&quot;&gt;proxy_pass&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;http&lt;/span&gt;://&lt;span class=&quot;n&quot;&gt;localhost&lt;/span&gt;:&lt;span class=&quot;m&quot;&gt;8090&lt;/span&gt;;
        &lt;span class=&quot;n&quot;&gt;proxy_set_header&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;Host&lt;/span&gt; $&lt;span class=&quot;n&quot;&gt;host&lt;/span&gt;;
        &lt;span class=&quot;n&quot;&gt;proxy_set_header&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;X&lt;/span&gt;-&lt;span class=&quot;n&quot;&gt;Real&lt;/span&gt;-&lt;span class=&quot;n&quot;&gt;IP&lt;/span&gt; $&lt;span class=&quot;n&quot;&gt;remote_addr&lt;/span&gt;;
        &lt;span class=&quot;n&quot;&gt;proxy_set_header&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;X&lt;/span&gt;-&lt;span class=&quot;n&quot;&gt;Forwarded&lt;/span&gt;-&lt;span class=&quot;n&quot;&gt;For&lt;/span&gt; $&lt;span class=&quot;n&quot;&gt;proxy_add_x_forwarded_for&lt;/span&gt;;
        &lt;span class=&quot;n&quot;&gt;proxy_set_header&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;X&lt;/span&gt;-&lt;span class=&quot;n&quot;&gt;Forwarded&lt;/span&gt;-&lt;span class=&quot;n&quot;&gt;Proto&lt;/span&gt; &lt;span class=&quot;n&quot;&gt;https&lt;/span&gt;;
    }
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Add to symlink to sites enabled&lt;br&gt;
&lt;/p&gt;

&lt;div class=&quot;highlight js-code-highlight&quot;&gt;
&lt;pre class=&quot;highlight shell&quot;&gt;&lt;code&gt;&lt;span class=&quot;nb&quot;&gt;sudo ln&lt;/span&gt; &lt;span class=&quot;nt&quot;&gt;-s&lt;/span&gt; /etc/nginx/sites-available/example.com /etc/nginx/sites-enabled/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Restarting nginx&lt;br&gt;
&lt;/p&gt;

&lt;div class=&quot;highlight js-code-highlight&quot;&gt;
&lt;pre class=&quot;highlight shell&quot;&gt;&lt;code&gt;&lt;span class=&quot;nb&quot;&gt;sudo &lt;/span&gt;nginx &lt;span class=&quot;nt&quot;&gt;-t&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class=&quot;nb&quot;&gt;sudo &lt;/span&gt;systemctl reload nginx
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;We could get https for our domain name example.com.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/HexmosTech/git-lrc&quot; rel=&quot;noopener noreferrer nofollow&quot;&gt;&lt;img src=&quot;https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fabn6nl3iehrohehnxgje.png&quot; alt=&quot;git-lrc&quot;&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Any feedback or contributors are welcome! It&amp;rsquo;s online, source-available, and ready for anyone to use. &lt;br&gt;
&amp;#11088; Star it on GitHub: &lt;a href=&quot;https://github.com/HexmosTech/git-lrc&quot; rel=&quot;noopener noreferrer nofollow&quot;&gt;https://github.com/HexmosTech/git-lrc&lt;/a&gt;&lt;/p&gt;


</description>
<category>Other</category>
<guid isPermaLink="true">https://coderlegion.com/18996/how-to-configure-nginx-as-an-https-proxy-server</guid>
<pubDate>Tue, 02 Jun 2026 16:03:57 +0000</pubDate>
</item>
<item>
<title>Domain Age Checker</title>
<link>https://coderlegion.com/16896/domain-age-checker</link>
<description>&lt;p&gt;A simple free tool to check any website’s &lt;a rel=&quot;nofollow&quot; href=&quot;https://beingoptimist.in/tools/hosting-tools/domain-age-checker/&quot;&gt;domain age&lt;/a&gt;, creation date, expiration date, registrar details, and WHOIS information instantly. Useful for SEO audits, domain research, backlink analysis, and website trust verification.&lt;/p&gt;
</description>
<category>Launches</category>
<guid isPermaLink="true">https://coderlegion.com/16896/domain-age-checker</guid>
<pubDate>Wed, 06 May 2026 20:21:48 +0000</pubDate>
</item>
<item>
<title>Instant CNAME Lookup Tool – Check DNS Al</title>
<link>https://coderlegion.com/12799/instant-cname-lookup-tool-check-dns-al</link>
<description>&lt;p&gt;Use this free &lt;a rel=&quot;nofollow&quot; href=&quot;https://beingoptimist.in/tools/dns-tools/cname-lookup-tool/&quot;&gt;CNAME Lookup Tool&lt;/a&gt; to quickly find the canonical name (CNAME) records for any domain or subdomain. It helps you verify DNS aliases, troubleshoot configuration issues, and ensure your domains are pointing to the correct targets without using complex command-line tools.&lt;/p&gt;
</description>
<category>Launches</category>
<guid isPermaLink="true">https://coderlegion.com/12799/instant-cname-lookup-tool-check-dns-al</guid>
<pubDate>Wed, 11 Mar 2026 21:25:19 +0000</pubDate>
</item>
<item>
<title>DNS Lookup &amp; Records Viewer</title>
<link>https://coderlegion.com/12124/dns-lookup-records-viewer</link>
<description>&lt;p&gt;This &lt;a rel=&quot;nofollow&quot; href=&quot;https://beingoptimist.in/tools/dns-tools/dns-lookup-tool/&quot;&gt;DNS Lookup Tool&lt;/a&gt; instantly pulls every public DNS record for your domain into a single, easy‑to‑scan table—A, AAAA, NS, MX, TXT and more, complete with TTL values. Just enter a domain, click “Run DNS Lookup,” and see exactly how your DNS is configured so you can debug email issues, verify CDN or nameserver changes, and confirm that everything is resolving correctly worldwide.&lt;/p&gt;
</description>
<category>Launches</category>
<guid isPermaLink="true">https://coderlegion.com/12124/dns-lookup-records-viewer</guid>
<pubDate>Tue, 24 Feb 2026 08:28:11 +0000</pubDate>
</item>
<item>
<title>DNS LookUp Tool</title>
<link>https://coderlegion.com/11884/dns-lookup-tool</link>
<description>&lt;p&gt;&lt;a rel=&quot;nofollow&quot; href=&quot;https://beingoptimist.in/tools/dns-tools/dns-lookup-tool/&quot;&gt;DNS Lookup Tool&lt;/a&gt; lets you instantly query A, AAAA, MX, TXT, CNAME, NS, and other DNS records for any domain, helping you verify configuration, troubleshoot issues, and understand how your domain is mapped on the internet.&lt;/p&gt;
</description>
<category>Launches</category>
<guid isPermaLink="true">https://coderlegion.com/11884/dns-lookup-tool</guid>
<pubDate>Wed, 18 Feb 2026 14:46:50 +0000</pubDate>
</item>
<item>
<title>Global DNS Propagation Checker</title>
<link>https://coderlegion.com/11751/global-dns-propagation-checker</link>
<description>&lt;p&gt;&lt;a rel=&quot;nofollow&quot; href=&quot;https://beingoptimist.in/tools/dns-tools/dns-propagation-checker/&quot;&gt;DNS Propagation Checker&lt;/a&gt; lets you instantly see how your domain’s DNS records resolve from multiple global locations, so you can verify updates, spot issues, and confirm your site is live everywhere.&lt;/p&gt;
</description>
<category>Launches</category>
<guid isPermaLink="true">https://coderlegion.com/11751/global-dns-propagation-checker</guid>
<pubDate>Mon, 16 Feb 2026 09:05:31 +0000</pubDate>
</item>
</channel>
</rss>