intended to support additional cross-checking at the client end of TLS connections to attempt to prevent certificates issued by CAs other than the specified CAs from being used to spoof |
('''CAA''') |
||
| Line 1: | Line 1: | ||
'''DNS Certification Authority Authorization''' uses the [[Internet]]'s [[Domain Name System]] to specify which [[Certificate Authority|Certificate Authorities]] may be regarded as authoritative for a domain. This is intended to support additional cross-checking at the client end of [[TLS]] connections to attempt to prevent certificates issued by CAs other than the specified CAs from being used to spoof the identity of websites or perform [[man-in-the-middle attack]]s on them. |
'''DNS Certification Authority Authorization''' ('''CAA''') uses the [[Internet]]'s [[Domain Name System]] to specify which [[Certificate Authority|Certificate Authorities]] may be regarded as authoritative for a domain. This is intended to support additional cross-checking at the client end of [[TLS]] connections to attempt to prevent certificates issued by CAs other than the specified CAs from being used to spoof the identity of websites or perform [[man-in-the-middle attack]]s on them. |
||
DNS Certification Authority Authorization is specified by RFC 6844, which designated a new "CAA" DNS RR type to carry name-value pairs that can carry a wide range of information to be used as part of the CA authorization process. Use of CAA, where available, to validate certificates is recommended, but not mandatory.<ref>{{cite web|url=https://tools.ietf.org/html/rfc6844|title=RFC 6844: DNS Certification Authority Authorization (CAA) Resource Record|publisher=Internet Engineering Task Force|author=P. Hallam-Baker and R. Stradling|date=January 2013}}</ref> |
DNS Certification Authority Authorization is specified by RFC 6844, which designated a new "CAA" DNS RR type to carry name-value pairs that can carry a wide range of information to be used as part of the CA authorization process. Use of CAA, where available, to validate certificates is recommended, but not mandatory.<ref>{{cite web|url=https://tools.ietf.org/html/rfc6844|title=RFC 6844: DNS Certification Authority Authorization (CAA) Resource Record|publisher=Internet Engineering Task Force|author=P. Hallam-Baker and R. Stradling|date=January 2013}}</ref> |
||
Revision as of 09:21, 7 May 2015
DNS Certification Authority Authorization (CAA) uses the Internet's Domain Name System to specify which Certificate Authorities may be regarded as authoritative for a domain. This is intended to support additional cross-checking at the client end of TLS connections to attempt to prevent certificates issued by CAs other than the specified CAs from being used to spoof the identity of websites or perform man-in-the-middle attacks on them.
DNS Certification Authority Authorization is specified by RFC 6844, which designated a new "CAA" DNS RR type to carry name-value pairs that can carry a wide range of information to be used as part of the CA authorization process. Use of CAA, where available, to validate certificates is recommended, but not mandatory.[1]
As of 2015[update], CAA records are supported in the BIND DNS server.[2]
References
- ^ P. Hallam-Baker and R. Stradling (January 2013). "RFC 6844: DNS Certification Authority Authorization (CAA) Resource Record". Internet Engineering Task Force.
- ^ Vicky Risk (August 29, 2014). "Certificate Authority Authorization Records". Internet Systems Consortium.