<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Audit on happyDomain&#39; latests news</title>
		<link>https://blog.happydomain.org/tags/audit/</link>
		<description>Recent content in Audit on happyDomain&#39; latests news</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
			<copyright>happyDomain</copyright>
		
		
			<lastBuildDate>Mon, 03 Aug 2026 09:00:00 +0200</lastBuildDate>
		
			<atom:link href="https://blog.happydomain.org/tags/audit/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>An independent security audit of happyDomain, funded by NLnet</title>
				<link>https://blog.happydomain.org/security-audit-2026/</link>
				<pubDate>Mon, 03 Aug 2026 09:00:00 +0200</pubDate>
				<guid>https://blog.happydomain.org/security-audit-2026/</guid>
				<description>&lt;p&gt;happyDomain holds something valuable: the API credentials that let you edit your&#xA;DNS zones at your registrar or DNS provider.&#xA;Were we really handling them correctly? Was there, somewhere, still a path&#xA;allowing someone to use another person&amp;rsquo;s keys?&#xA;We have been asking ourselves that for years, with the eyes of the people who&#xA;wrote the code.&lt;/p&gt;&#xA;&lt;p&gt;Thanks to our &lt;a href=&#34;https://nlnet.nl/core/&#34;&gt;NGI Zero Core&lt;/a&gt; grant from&#xA;&lt;a href=&#34;https://nlnet.nl/&#34;&gt;NLnet&lt;/a&gt;, &lt;a href=&#34;https://www.radicallyopensecurity.com/&#34;&gt;Radically Open&#xA;Security&lt;/a&gt; has audited&#xA;happyDomain during July 2026.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
