<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-dnsop-domain-verification-techniques" target="https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-domain-verification-techniques-10">
   <front>
      <title>Domain Control Validation using DNS</title>
      <author initials="S. K." surname="Sahib" fullname="Shivan Kaul Sahib">
         <organization>Brave Software</organization>
      </author>
      <author initials="S." surname="Huque" fullname="Shumon Huque">
         <organization>Salesforce</organization>
      </author>
      <author initials="P." surname="Wouters" fullname="Paul Wouters">
         <organization>Aiven</organization>
      </author>
      <author initials="E." surname="Nygren" fullname="Erik Nygren">
         <organization>Akamai Technologies</organization>
      </author>
      <author initials="T." surname="Wicinski" fullname="Tim Wicinski">
         <organization>Cox Communications</organization>
      </author>
      <date month="October" day="13" year="2025" />
      <abstract>
	 <t>   Many application services on the Internet need to verify ownership or
   control of a domain in the Domain Name System (DNS).  The general
   term for this process is &quot;Domain Control Validation&quot;, and can be done
   using a variety of methods such as email, HTTP/HTTPS, or the DNS
   itself.  This document focuses only on DNS-based methods, which
   typically involve the Application Service Provider requesting a DNS
   record with a specific format and content to be visible in the domain
   to be verified.  There is wide variation in the details of these
   methods today.  This document provides some best practices to avoid
   known problems.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-dnsop-domain-verification-techniques-10" />
   
</reference>
