<story><title>Giving every IPv6 address a name</title><url>https://has-a.name</url></story><parent_chain><item><author>robbya</author><text>This is cool, but keep in mind that the operator can also get SSL certs for your site (they just point the domain somewhere else and use Lets Encrypt or similar to get a certificate). So from a security perspective, you are putting a ton of trust if you use this for anything real.</text></item></parent_chain><comment><author>gregmac</author><text>Also don&amp;#x27;t use for anything real, because you should not be teaching users that &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;1234-5678-9adc-def0-1234-5678-9abc-def0.has-a.name&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;1234-5678-9adc-def0-1234-5678-9abc-def0.has-a.name&lt;/a&gt; is the proper, trusted domain for your service. Because it was supposed to be &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;1234-5678-9abc-def0-1234-5678-9abc-def0.has-a.name&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;1234-5678-9abc-def0-1234-5678-9abc-def0.has-a.name&lt;/a&gt; and I just tricked &lt;i&gt;you&lt;/i&gt;.</text></comment>
<story><title>Giving every IPv6 address a name</title><url>https://has-a.name</url></story><parent_chain><item><author>robbya</author><text>This is cool, but keep in mind that the operator can also get SSL certs for your site (they just point the domain somewhere else and use Lets Encrypt or similar to get a certificate). So from a security perspective, you are putting a ton of trust if you use this for anything real.</text></item></parent_chain><comment><author>anaphor</author><text>I don&amp;#x27;t think they even need to point the A record somewhere else. They can just create a TXT record and some CAs will allow you to validate it that way, if I&amp;#x27;m not mistaken.</text></comment>