<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>email-security on Raúl Pastor</title><link>https://pixelotes.com/tags/email-security/</link><description>Recent content in email-security on Raúl Pastor</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 29 Oct 2026 20:05:00 +0100</lastBuildDate><atom:link href="https://pixelotes.com/tags/email-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Hardening a personal domain in an afternoon, for free</title><link>https://pixelotes.com/blog/hardening-a-personal-domain/</link><pubDate>Thu, 29 Oct 2026 20:05:00 +0100</pubDate><guid>https://pixelotes.com/blog/hardening-a-personal-domain/</guid><description>&lt;p&gt;Your personal domain is part of your professional identity. If someone can send mail as you, get a certificate for it or take over a forgotten subdomain, that&amp;rsquo;s your name on it. I recently cleaned up mine with a free Cloudflare plan and a free mail plan. Here is what each piece does and how to check it. The examples use &lt;code&gt;example.com&lt;/code&gt;.&lt;/p&gt;&#10;&lt;h2 id="1-remove-what-you-dont-use"&gt;1. Remove what you don&amp;rsquo;t use&lt;/h2&gt;&#10;&lt;p&gt;Old subdomains pointing at services you have deleted are the easiest way in. If &lt;code&gt;blog.example.com&lt;/code&gt; still has a CNAME to a hosting platform where you closed the account, someone else can claim it and serve content on your domain. This is called &lt;strong&gt;subdomain takeover&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>