<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloudflare on Mexicali IT</title><link>https://mxlit.com/technologies/cloudflare/</link><description>Recent content in Cloudflare on Mexicali IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 17 Mar 2026 19:00:00 -0700</lastBuildDate><atom:link href="https://mxlit.com/technologies/cloudflare/index.xml" rel="self" type="application/rss+xml"/><item><title>Umami: Solving Geolocation (City and Region) with Cloudflare Tunnels</title><link>https://mxlit.com/kb-00075/</link><pubDate>Tue, 17 Mar 2026 19:00:00 -0700</pubDate><guid>https://mxlit.com/kb-00075/</guid><description>&lt;p&gt;Umami is one of the best privacy-focused, self-hosted alternatives for web analytics. However, an extremely common issue when deploying it behind &lt;strong&gt;Cloudflare Tunnels&lt;/strong&gt; is that the dashboard identifies the visitor&amp;rsquo;s country, but the &lt;strong&gt;City&lt;/strong&gt; and &lt;strong&gt;Region&lt;/strong&gt; fields appear empty (&lt;code&gt;—&lt;/code&gt;).&lt;/p&gt;
&lt;p&gt;&lt;img src="https://mxlit.com/kb-00075/index-1.png" alt=""&gt;&lt;/p&gt;
&lt;p&gt;In this guide, we will look at how to fix this telemetry &amp;ldquo;short circuit&amp;rdquo; by correctly configuring HTTP headers so that Cloudflare provides Umami with all the geographic information it needs.&lt;/p&gt;</description></item><item><title>Cloudflare: Cryptographic Security for Your Domain with DNSSEC</title><link>https://mxlit.com/kb-00072/</link><pubDate>Sun, 15 Mar 2026 14:30:00 -0700</pubDate><guid>https://mxlit.com/kb-00072/</guid><description>&lt;p&gt;The Domain Name System (DNS) is the Internet&amp;rsquo;s address book, but by original design, it is not secure. When a user types a domain into their browser, the query travels in plain text and blindly trusts the response it receives. This is where &lt;strong&gt;DNSSEC (Domain Name System Security Extensions)&lt;/strong&gt; comes in.&lt;/p&gt;
&lt;p&gt;DNSSEC does not encrypt DNS queries, but rather &lt;strong&gt;digitally signs them&lt;/strong&gt;. It works through a public-key cryptography system that guarantees DNS resolvers (such as those from Google, Cloudflare, or your ISP) that the IP address they are being directed to is legitimate and has not been altered along the way.&lt;/p&gt;</description></item></channel></rss>