RFC 7873: Domain Name System (DNS) Cookies
In plain English — editorial summary, not part of the RFC
DNS Cookies are a lightweight DNS transaction security mechanism that provides limited protection to DNS servers and clients against a variety of increasingly common denial-of-service and amplification/ forgery or cache poisoning attacks by off-path attackers. DNS Cookies are tolerant of NAT, NAT-PT (Network Address Translation - Protocol Translation), and anycast and can be incrementally deployed. (Since DNS Cookies are only returned to the IP address from which they were originally received, they cannot be used to generally track Internet users.)
Document record
- Document ID
- RFC7873
- Published
- May 2016
- Authors
- D. Eastlake 3rd; M. Andrews
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 25
- Also known as
- —
- Updated by:
- RFC 9018
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9288Recommendations on the Filtering of IPv6 Packets Containing IPv6 Extension Headers at Transit RoutersCurrent
August 2022
- RFC 6274Security Assessment of the Internet Protocol Version 4Current
July 2011
- RFC 5358Preventing Use of Recursive Nameservers in Reflector AttacksCurrent
October 2008
- RFC 7837IPv6 Destination Option for Congestion Exposure (ConEx)Current
May 2016
- RFC 7739Security Implications of Predictable Fragment Identification ValuesCurrent
February 2016
- RFC 7141Byte and Packet Congestion NotificationCurrent
February 2014
- RFC 5575Dissemination of Flow Specification RulesObsoleted
August 2009
- RFC 4832Security Threats to Network-Based Localized Mobility Management (NETLMM)Current
April 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?