DomainKeys Identified Mail

DomainKeys Identified Mail (DKIM) is an email authentication method designed to detect forged sender addresses in email (email spoofing), a technique often used in phishing and email spam.

DKIM allows the receiver to check that an email that claimed to have come from a specific domain was indeed authorized by the owner of that domain. ^[1] It achieves this by affixing a digital signature, linked to a domain name, to each outgoing email message. The recipient system can verify this by looking up the sender's public key published in the DNS. A valid signature also guarantees that some parts of the email (possibly including attachments) have not been modified since the signature was affixed. ^[2] Usually, DKIM signatures are not visible to end-users, and are affixed or verified by the infrastructure rather than the message's authors and recipients.

DKIM is an Internet Standard. ^[3] It is defined in RFC 6376, dated September 2011, with updates in RFC 8301 and RFC 8463.

Overview

The need for email validated identification arises because forged addresses and content are otherwise easily created—and widely used in spam, phishing and other email-based fraud. ^[4] For example, a fraudster may send a message claiming to be from [e-mail], with the goal of convincing the recipient to accept and to read the email—and it is difficult for recipients to establish whether to trust this message. System administrators also have to deal with complaints about malicious email that appears to have originated from their systems, but did not. ^[5]

DKIM provides the ability to sign a message, and allows the signer (author organization) to communicate which email it considers legitimate. It does not directly prevent or disclose abusive behavior.

DKIM also provides a process for verifying a signed message. Verifying modules typically act on behalf of the receiver organization, possibly at each hop.

All of this is independent of Simple Mail Transfer Protocol (SMTP) routing aspects, in that it operates on the RFC 5322 message—the transported mail's header and body—not the SMTP "envelope" defined in RFC 5321. Hence, DKIM signatures survive basic relaying across multiple message transfer agents.

Technical details

Signing

The signing organization can be a direct handler of the message, such as the author, mail submission agent, site, or further intermediary along the transit path, or an indirect handler such as an independent service that is providing assistance to a direct handler.

Signing modules insert one or more DKIM-Signature: header fields, possibly on behalf of the author organization or the originating service provider. The specification allows signers to choose which header fields they sign, but the From: field must always be signed. ^{[6] [7]} The resulting header field consists of a list of tag=value parts as in the example below:

DKIM-Signature:v=1;a=rsa-sha256;d=example.net;s=brisbane; c=relaxed/simple;q=dns/txt;i=[e-mail]; t=1117574938;x=1118006938;l=200; h=from:to:subject:date:keywords:keywords; z=From:[e-mail]|To:[e-mail]| Subject:demo=20run|Date:July=205,=202005=203:44:08=20PM=20-0700; bh=MTIzNDU2Nzg5MDEyMzQ1Njc4OTAxMjM0NTY3ODkwMTI=; b=dzdVyOfAKCdLXdJOc9G2q8LoXSlEniSbav+yuU4zGeeruD00lszZ VoG4ZHRNiYzR 

where the tags used are:

• v (required), version
• a (required), signing algorithm
• d (required), Signing Domain Identifier (SDID)
• s (required), selector
• c (optional), canonicalization algorithm(s) for header and body
• q (optional), default query method
• i (optional), Agent or User Identifier (AUID)
• t (recommended), signature timestamp
• x (recommended), expire time
• l (optional), body length
• h (required), header fields - list of those that have been signed
• z (optional), header fields - copy of selected header fields and values
• bh (required), body hash
• b (required), signature of headers and body

The most relevant ones are b for the actual digital signature of the contents (headers and body) of the mail message, bh for the body hash (optionally limited to the first l octets of the body), d for the signing domain, and s for the selector.

An Agent or User Identifier (AUID) can optionally be included. The format is an email address with an optional local-part. The domain must be equal to, or a subdomain of, the signing domain. The semantics of the AUID are intentionally left undefined, and may be used by the signing domain to establish a more fine-grained sphere of responsibility.

Both header and body contribute to the signature. First, the message body is hashed, always from the beginning, possibly truncated to a given length l (which may be zero). Second, selected header fields are hashed, in the order given by h. Repeated field names are matched from the bottom of the header upward, which is the order in which Received: fields are inserted in the header. A non-existing field matches the empty string, so that adding a field with that name will break the signature. The DKIM-Signature: field of the signature being created, with bh equal to the computed body hash and b equal to the empty string, is implicitly added to the second hash, albeit its name must not appear in h — if it does, it refers to another, preexisting signature. For both hashes, text is canonicalized according to the relevant c algorithms. The result, after encryption with the signer's private key and encoding using Base64, is b.

In addition to the list of header fields listed in h, a list of header fields (including both field name and value) present at the time of signing may be provided in z. This list need not match the list of headers in h.

Algorithms, fields, and body length are meant to be chosen so as to assure unambiguous message identification while still allowing signatures to survive the unavoidable changes which are going to occur in transit. No end-to-end data integrity is implied. ^[2]

Verification

A receiving SMTP server wanting to verify uses the domain name and the selector to perform a DNS lookup. ^[8] For example, given the example signature above: the d tag gives the author domain to be verified against, example.net ; the s tag the selector, brisbane. The string _domainkey is a fixed part of the specification. This gives the TXT resource record to be looked up as:

brisbane._domainkey.example.net

Note that the selector and the domain name can be UTF-8 in internationalized email. ^[9] In that case the label must be encoded according to IDNA before lookup. The data returned from the query of this record is also a list of tag-value pairs. It includes the domain's public key, along with other key usage tokens and flags (e.g. from a command line: nslookup -q=TXT brisbane._domainkey.example.net) as in this example:

"k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDDmzRmJRQxLEuyYiyMg4suA2Sy MwR5MGHpP9diNT1hRiwUd/mZp1ro7kIDTKS8ttkI6z6eTRW9e9dDOxzSxNuXmume60Cjbu08gOyhPG3 GfWdg7QkdN6kR4V75MFlw624VY35DaXBvnlTJTgRg/EW72O1DiYVThkyCgpSYS8nmEQIDAQAB" 

The available tags are: ^[3]

• v (recommended), version (default DKIM1, must be the first tag if present)
• h (optional), acceptable hash algorithms (default all)
• k (optional), key type (default rsa)
• n (optional), human-readable administrator notes
• p (required), public key data (base64 encoded, or empty if the public key has been revoked)
• s (optional), service type (default *, else email)
• t (optional), toggle flags (colon-separated list, default none, may include y for testing DKIM without rejecting failed signature verifications, and/or s which is recommended for subdomain strictness as explained in the RFC)

A CNAME record can also be used to point at a different TXT record, for example when one organization sends email on behalf of another.

The receiver can use the public key (value of the p tag) to then validate the signature on the hash value in the header field, and check it against the hash value for the mail message (headers and body) that was received. If the two values match, this cryptographically proves that the mail was signed by the indicated domain and has not been tampered with in transit.

Signature verification failure does not force rejection of the message. Instead, the precise reasons why the authenticity of the message could not be proven should be made available to downstream and upstream processes. Methods for doing so may include sending back an FBL message, or adding an Authentication-Results: header field to the message as described in RFC 7001.

Patent

DomainKeys was covered by U.S. patent 6,986,049 , now expired. Yahoo! licensed its patent claims under a dual license scheme: the DomainKeys Patent License Agreement v1.2, ^[10] or GNU General Public License v2.0 (and no other version). ^{[11] [12]}

Relationship to SPF and DMARC

In essence, both DKIM and SPF provide different measures of email authenticity. DMARC provides the ability for an organisation to publish a policy that specifies which mechanism (DKIM, SPF, or both) is employed when sending email from that domain; how to check the From: field presented to end users; how the receiver should deal with failures—and a reporting mechanism for actions performed under those policies. ^[13]

Advantages

The primary advantage of this system for e-mail recipients is in allowing the signing domain to reliably identify a stream of legitimate email, thereby allowing domain-based blacklists and whitelists to be more effective. ^[14] This is also likely to make certain kinds of phishing attacks easier to detect.

There are some incentives for mail senders to sign outgoing e-mail:

• It allows a great reduction in abuse desk work for DKIM-enabled domains if e-mail receivers use the DKIM system to identify forged e-mail messages claiming to be from that domain.
• The domain owner can then focus its abuse team energies on its own users who actually are making inappropriate use of that domain.

Use with spam filtering

DKIM is a method of labeling a message, and it does not itself filter or identify spam. However, widespread use of DKIM can prevent spammers from forging the source address of their messages, a technique they commonly employ today. If spammers are forced to show a correct source domain, other filtering techniques can work more effectively. In particular, the source domain can feed into a reputation system to better identify spam. Conversely, DKIM can make it easier to identify mail that is known not to be spam and need not be filtered. If a receiving system has a whitelist of known good sending domains, either locally maintained or from third party certifiers, it can skip the filtering on signed mail from those domains, and perhaps filter the remaining mail more aggressively. ^[14]

Anti-phishing

DKIM can be useful as an anti-phishing technology. Mailers in heavily phished domains can sign their mail to show that it is genuine. Recipients can take the absence of a valid signature on mail from those domains to be an indication that the mail is probably forged. The best way to determine the set of domains that merit this degree of scrutiny remains an open question. DKIM used to have an optional feature called ADSP that lets authors that sign all their mail self-identify, but it was demoted to historic status in November 2013. ^[15] Instead, DMARC can be used for the same purpose ^[16] and allows domains to self-publish which techniques (including SPF and DKIM) they employ, which makes it easier for the receiver to make an informed decision whether a certain mail is spam or not. ^[17] For example, using DMARC, eBay and PayPal both publish policies that all of their mail is authenticated, and requesting that any receiving system, such as Gmail, should reject any that is not. ^[18]

Compatibility

Because it is implemented using DNS records and an added RFC 5322 header field, DKIM is compatible with the existing e-mail infrastructure. In particular, it is transparent to existing e-mail systems that lack DKIM support. ^[19]

This design approach also is compatible with other, related services, such as the S/MIME and OpenPGP content-protection standards. DKIM is compatible with the DNSSEC standard and with SPF.

Computation overhead

DKIM requires cryptographic checksums to be generated for each message sent through a mail server, which results in computational overhead not otherwise required for e-mail delivery. This additional computational overhead is a hallmark of digital postmarks, making sending bulk spam more (computationally) expensive. ^[20] This facet of DKIM may look similar to hashcash, except that the receiver side verification is a negligible amount of work, while a typical hashcash algorithm would require far more work.^{[ citation needed ]}

Non-repudiability

DKIM's non-repudiation feature prevents senders (such as spammers) from credibly denying having sent an email. It has proven useful to news media sources such as WikiLeaks, which has been able to leverage DKIM body signatures to prove that leaked emails were genuine and not tampered with. ^[21]

Many consider non-repudiation a non-wanted feature of DKIM, forced by behaviors such as those just described. Indeed, DKIM protocol provides for expiration. There is an optional x tag on each signature, which establishes a formal expiration time; however, verifiers can ignore it. In addition, domain owners can revoke a public key by removing its cryptographic data from the record, thereby preventing signature verification unless someone saved the public key data beforehand. DKIM key rotation is often recommended just to minimize the impact of compromised keys. However, in order to definitely disable non-repudiation, expired secret keys can be published, thereby allowing everyone to produce fake signatures, thus voiding the significance of original ones. ^{[22] [23] [24]}

Weaknesses

The RFC itself identifies a number of potential attack vectors. ^[25]

DKIM signatures do not encompass the message envelope, which holds the return-path and message recipients. Since DKIM does not attempt to protect against mis-addressing, this does not affect its utility.

A number of concerns were raised and refuted in 2013 at the time of the standardization. ^[26]

A concern for any cryptographic solution would be message replay abuse, which bypasses techniques that currently limit the level of abuse from larger domains.^{[ clarification needed ]} Replay can be inferred by using per-message public keys, tracking the DNS queries for those keys and filtering out the high number of queries due to e-mail being sent to large mailing lists or malicious queries by bad actors.

For a comparison of different methods also addressing this problem see e-mail authentication.

Arbitrary forwarding

As mentioned above, authentication is not the same as abuse prevention. A malicious email user of a reputable domain can compose a bad message and have it DKIM-signed and sent from that domain to any mailbox from where they can retrieve it as a file, so as to obtain a signed copy of the message. Use of the l tag in signatures makes doctoring such messages even easier. The signed copy can then be forwarded to a million recipients, for example through a botnet, without control. The email provider who signed the message can block the offending user, but cannot stop the diffusion of already-signed messages. The validity of signatures in such messages can be limited by always including an expiration time tag in signatures, or by revoking a public key periodically or upon a notification of an incident. Effectiveness of the scenario can hardly be limited by filtering outgoing mail, as that implies the ability to detect if a message might potentially be useful to spammers. ^[27]

Content modification

DKIM currently features two canonicalization algorithms, simple and relaxed, neither of which is MIME-aware. ^[28] Mail servers can legitimately convert to a different character set, and often document this with X-MIME-Autoconverted: header fields. In addition, servers in certain circumstances have to rewrite the MIME structure, thereby altering the preamble, the epilogue, and entity boundaries, any of which breaks DKIM signatures. Only plain text messages written in us-ascii, provided that MIME header fields are not signed, ^[29] enjoy the robustness that end-to-end integrity requires.

The OpenDKIM Project organized a data collection involving 21 mail servers and millions of messages. 92.3% of observed signatures were successfully verified, a success rate that drops slightly (90.5%) when only mailing list traffic is considered. ^[30]

Annotations by mailing lists

The problems might be exacerbated when filtering or relaying software makes changes to a message. Without specific precaution implemented by the sender, the footer addition operated by most mailing lists and many central antivirus solutions will break the DKIM signature. A possible mitigation is to sign only designated number of bytes of the message body. It is indicated by l tag in DKIM-Signature header. Anything added beyond the specified length of the message body is not taken into account while calculating DKIM signature. This won't work for MIME messages. ^[31]

Another workaround is to whitelist known forwarders; e.g., by SPF. For yet another workaround, it was proposed that forwarders verify the signature, modify the email, and then re-sign the message with a Sender: header. ^[32] However, this solution has its risk with forwarded third party signed messages received at SMTP receivers supporting the RFC 5617 ADSP protocol. Thus, in practice, the receiving server still has to whitelist known message streams.

The Authenticated Received Chain (ARC) is an email authentication system designed to allow an intermediate mail server like a mailing list or forwarding service to sign an email's original authentication results. This allows a receiving service to validate an email when the email's SPF and DKIM records are rendered invalid by an intermediate server's processing. ^[33] ARC is defined in RFC 8617, published in July 2019, as "Experimental". ^[34]

Short key vulnerability

In October 2012, Wired reported that mathematician Zach Harris detected and demonstrated an email source spoofing vulnerability with short DKIM keys for the google.com corporate domain, as well as several other high-profile domains. He stated that authentication with 384-bit keys can be factored in as little as 24 hours "on my laptop," and 512-bit keys, in about 72 hours with cloud computing resources. Harris found that many organizations sign email with such short keys; he factored them all and notified the organizations of the vulnerability. He states that 768-bit keys could be factored with access to very large amounts of computing power, so he suggests that DKIM signing should use key lengths greater than 1,024.

Wired stated that Harris reported, and Google confirmed, that they began using new longer keys soon after his disclosure. According to RFC 6376 the receiving party must be able to validate signatures with keys ranging from 512 bits to 2048 bits, thus usage of keys shorter than 512 bits might be incompatible and shall be avoided. RFC 6376 also states that signers must use keys of at least 1024 bits for long-lived keys, though long-livingness is not specified there. ^[35]

History

DKIM resulted in 2004 from merging two similar efforts, "enhanced DomainKeys" from Yahoo and "Identified Internet Mail" from Cisco. ^{[36] [37]} This merged specification has been the basis for a series of IETF standards-track specifications and support documents which eventually resulted in STD 76, currently RFC 6376. ^[38] "Identified Internet Mail" was proposed by Cisco as a signature-based mail authentication standard, ^{[39] [40]} while DomainKeys was designed by Yahoo ^{[41] [42]} to verify the DNS domain of an e-mail sender and the message integrity.

Aspects of DomainKeys, along with parts of Identified Internet Mail, were combined to create DomainKeys Identified Mail (DKIM). ^{[41] [43] [44]} Trendsetting providers implementing DKIM include Yahoo, Gmail, AOL and FastMail. Any mail from these organizations should carry a DKIM signature. ^{[41] [45] [46] [47]}

Discussions about DKIM signatures passing through indirect mail flows, formally in the DMARC working group, took place right after the first adoptions of the new protocol wreaked havoc on regular mailing list use. However, none of the proposed DKIM changes passed. Instead, mailing list software was changed. ^{[48] [ irrelevant citation ]}

In 2017, another working group was launched, DKIM Crypto Update (dcrup), with the specific restriction to review signing techniques. ^[49] RFC 8301 was issued in January 2018. It bans SHA-1 and updates key sizes (from 512-2048 to 1024-4096). ^[50] RFC 8463 was issued in September 2018. It adds an elliptic curve algorithm to the existing RSA. The added key type, k=ed25519 is adequately strong while featuring short public keys, more easily publishable in DNS. ^[51]

Development

The original DomainKeys was designed by Mark Delany of Yahoo! and enhanced through comments from many others since 2004. It is specified in Historic RFC 4870, superseded by Standards Track RFC 4871, DomainKeys Identified Mail (DKIM) Signatures; both published in May 2007. A number of clarifications and conceptualizations were collected thereafter and specified in RFC 5672, August 2009, in the form of corrections to the existing specification. In September 2011, RFC 6376 merged and updated the latter two documents, while preserving the substance of the DKIM protocol. Public key compatibility with the earlier DomainKeys is also possible.

DKIM was initially produced by an informal industry consortium and was then submitted for enhancement and standardization by the IETF DKIM Working Group, chaired by Barry Leiba and Stephen Farrell, with Eric Allman of sendmail, Jon Callas of PGP Corporation, Mark Delany and Miles Libbey of Yahoo!, and Jim Fenton and Michael Thomas of Cisco Systems attributed as primary authors.

Source code development of one common library is led by The OpenDKIM Project, following the most recent protocol additions, and licensing under the New BSD License. ^[52]

Enforcement

Email providers are increasingly requiring senders to implement email authentication in order to successfully deliver mail to their users' mailboxes.

In February 2024, Google started requiring bulk senders to authenticate their emails with DKIM to successfully deliver emails to Google-hosted mailboxes. ^{[53] [54]}

Similarly in February 2024, Yahoo started requiring bulk senders to implement SPF and DKIM to successfully deliver emails to Yahoo users. ^[55]

See also

• Authenticated Received Chain (ARC)
• Author Domain Signing Practices
• Bounce message
• Context filtering
• DMARC (Domain-based Message Authentication, Reporting and Conformance)
• DomainKeys
• Email authentication
• OpenPGP
• S/MIME
• Sender Policy Framework (SPF)
• Vouch by Reference

References

1. Tony Hansen; Dave Crocker; Phillip Hallam-Baker (July 2009). DomainKeys Identified Mail (DKIM) Service Overview. IETF. doi: 10.17487/RFC5585 . RFC 5585 . Retrieved 6 January 2016. Receivers who successfully verify a signature can use information about the signer as part of a program to limit spam, spoofing, phishing, or other undesirable behaviors. DKIM does not, itself, prescribe any specific actions by the recipient; rather, it is an enabling technology for services that do.
2. Dave Crocker; Tony Hansen; Murray S. Kucherawy, eds. (September 2011). "Data Integrity". DomainKeys Identified Mail (DKIM) Signatures. IETF. sec. 1.5. doi: 10.17487/RFC6376 . RFC 6376 . Retrieved 6 January 2016. Verifying the signature asserts that the hashed content has not changed since it was signed and asserts nothing else about "protecting" the end-to-end integrity of the message.
3. Crocker, D.; Hansen, T.; Kucherawy, M. (September 2011). "DomainKeys Identified Mail (DKIM) Signatures". RFC Editor. ISSN   2070-1721 . Retrieved 30 March 2020.
4. "DKIM: What is it and why is it important?". postmarkapp.com. Retrieved 19 February 2022.
5. Jason P. Stadtlander (16 January 2015). "Email Spoofing: Explained (and How to Protect Yourself)". HuffPost . Retrieved 11 January 2016.
6. Dave Crocker; Tony Hansen; Murray S. Kucherawy, eds. (July 2009). "Determine the Header Fields to Sign". DomainKeys Identified Mail (DKIM) Signatures. IETF. sec. 5.4. doi: 10.17487/RFC6376 . RFC 6376 . Retrieved 6 January 2016. The From header field MUST be signed (that is, included in the "h=" tag of the resulting DKIM-Signature header field).
7. Signing modules use the private half of a key-pair to do the signing, and publish the public half in a DNS TXT record as outlined in the "Verification" section below.
8. Note that there are no CAs nor revocation lists involved in DKIM key management, and the selector is a straightforward method to allow signers to add and remove keys whenever they wish – long lasting signatures for archival purposes are outside DKIM's scope.
9. John Levine (June 2019). "DKIM and Internationalized Mail". Email Authentication for Internationalized Mail. IETF. sec. 5. doi: 10.17487/RFC8616 . RFC 8616.
10. "Yahoo! DomainKeys Patent License Agreement v1.1". SourceForge. 2006. Retrieved 30 May 2010. Yahoo! DomainKeys Patent License Agreement v1.2
11. Levine, John R. (25 January 2010). "IPR disclosures, was Collecting re-chartering questions". ietf-dkim mailing list. Mutual Internet Practices Association. Archived from the original on 14 September 2016. Retrieved 30 May 2010. The reference to the GPL looks to me like it only covers the old Sourceforge DK library, which I don't think anyone uses any more. The patent, which is what's important, is covered by a separate license that Yahoo wrote.
12. Chen, Andy (26 September 2011). "Yahoo! Inc.'s Statement about IPR related to RFC 6376". IPR disclosure. IETF . Retrieved 3 October 2011.
13. "History". dmarc.org.
14. Falk, J.D. (17 March 2009). "Searching for Truth in DKIM". CircleID.
15. Barry Leiba (25 November 2013). "Change the status of ADSP (RFC 5617) to Historic". IETF . Retrieved 13 March 2015.
16. "FAQ - DMARC Wiki". The DMARC standard states in Section 6.7, "Policy Enforcement Considerations," that if a DMARC policy is discovered the receiver must disregard policies advertised through other means such as SPF or ADSP.
17. "Add a DMARC record - Google Apps Administrator Help".
18. "About DMARC - Google Apps Administrator Help". Your policy can be strict or relaxed. For example, eBay and PayPal publish a policy requiring all of their mail to be authenticated in order to appear in someone's inbox. In accordance with their policy, Google rejects all messages from eBay or PayPal that aren't authenticated.
19. Tony Hansen; Dave Crocker; Phillip Hallam-Baker (July 2009). DomainKeys Identified Mail (DKIM) Service Overview. IETF. doi: 10.17487/RFC5585 . RFC 5585 . Retrieved 1 July 2013.
20. Roic, Alessio (5 July 2007). "Postmarking: helping the fight against spam" Archived 17 July 2011 at the Wayback Machine . Microsoft Office Outlook Blog.
21. "DKIM Verification". www.wikileaks.org. 4 November 2016. Retrieved 7 November 2016.
22. Matthew D. Green (16 November 2020). "Ok Google: please publish your DKIM secret keys". cryptographyengineering.com. Google.
23. Ian Jackson (2022). "dkim-rotate - Principles of Operation". manpages.ubuntu.com. Ubuntu.
24. "DKIM Signing Keys". iecc.com. 10 April 2023. Retrieved 27 April 2023.
25. D. Crocker; T. Hansen; M. Kucherawy. "Security considerations". DomainKeys Identified Mail (DKIM) Signatures. IETF. sec. 8. doi: 10.17487/RFC6376 . RFC 6376.
26. "IESG Report regarding "Appeal of decision to advance RFC6376"". IETF.org. IETF. Retrieved 26 December 2018.
27. Jim Fenton (September 2006). "Chosen Message Replay". Analysis of Threats Motivating DomainKeys Identified Mail (DKIM). IETF. sec. 4.1.4. doi: 10.17487/RFC4686 . RFC 4686 . Retrieved 10 January 2016.
28. Ned Freed (with agreement by John Klensin) (5 March 2010). "secdir review of draft-ietf-yam-rfc1652bis-03". YAM mailing list. IETF . Retrieved 30 May 2010. DKIM WG opted for canonical form simplicity over a canonical form that's robust in the face of encoding changes. It was their engineering choice to make and they made it.
29. RFC 2045 allows a parameter value to be either a token or a quoted-string, e.g. in {{{1}}} the quotes can be legally removed, which breaks DKIM signatures.
30. Kucherawy, Murray (28 March 2011). "RFC4871 Implementation Report". IETF . Retrieved 18 February 2012.
31. Murray S. Kucherawy (September 2011). DomainKeys Identified Mail (DKIM) and Mailing Lists. IETF. doi: 10.17487/RFC6377 . RFC 6377 . Retrieved 10 January 2016.
32. Eric Allman; Mark Delany; Jim Fenton (August 2006). "Mailing List Manager Actions". DKIM Sender Signing Practices. IETF. sec. 5.1. I-D draft-allman-dkim-ssp-02. Retrieved 10 January 2016.
33. "Authenticated Received Chain Overview" (PDF). Retrieved 15 June 2017.
34. K. Andersen; B. Long; S. Blank; M. Kucherawy. The Authenticated Received Chain (ARC) Protocol. IETF. doi: 10.17487/RFC8617/ . RFC 8617/.
35. Zetter, Kim (24 October 2012). "How a Google Headhunter’s E-Mail Unraveled a Massive Net Security Hole". Wired. Accessed 24 October 2012.
36. "DKIM Frequently Asked Questions". DKIM.org. 16 October 2007. Retrieved 4 January 2016. DKIM was produced by an industry consortium in 2004. It merged and enhanced DomainKeys, from Yahoo! and Identified Internet Mail, from Cisco.
37. Jim Fenton (15 June 2009). "DomainKeys Identified Mail (DKIM) Grows Significantly". Cisco. Archived from the original on 24 December 2014. Retrieved 28 October 2014.
38. "STD 76, RFC 6376 on DomainKeys Identified Mail (DKIM) Signatures". IETF. 11 July 2013. Retrieved 12 July 2013. RFC 6376 has been elevated to Internet Standard.
39. "Identified Internet Mail: A network based message signing approach to combat email fraud". 26 April 2006. Archived from the original on 27 April 2006. Retrieved 4 January 2016.
40. Jim Fenton; Michael Thomas (1 June 2004). Identified Internet Mail. IETF. I-D draft-fenton-identified-mail-00. Retrieved 6 January 2016.
41. Delany, Mark (22 May 2007). "One small step for email, one giant leap for Internet safety" Archived 14 March 2013 at the Wayback Machine . Yahoo! corporate blog. Delany is credited as Chief Architect, inventor of DomainKeys.
42. "Yahoo Releases Specs for DomainKeys". DMNews.com. 19 May 2004.
43. RFC 4870 ("Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys)"; obsoleted by RFC 4871).
44. RFC 6376 ("DomainKeys Identified Mail (DKIM) Signatures"; obsoletes RFC 4871 and RFC 5672).
45. Taylor, Brad (8 July 2008). "Fighting phishing with eBay and Paypal". Gmail Blog.
46. "I’m having trouble sending messages in Gmail". Gmail Help entry, mentioning DKIM support when sending.
47. Mueller, Rob (13 August 2009). "All outbound email now being DKIM signed" Archived 6 October 2011 at the Wayback Machine . Fastmail blog.
48. "DMARC Group History". IETF .
49. "DKIM Crypto Update (dcrup)". IETF .
50. Scott Kitterman (January 2018). Cryptographic Algorithm and Key Usage Update to DomainKeys Identified Mail (DKIM). IETF. doi: 10.17487/RFC8301 . RFC 8301.
51. John Levine (September 2018). A New Cryptographic Signature Method for DomainKeys Identified Mail (DKIM). IETF. doi: 10.17487/RFC8463 . RFC 8463.
52. "OpenDKIM".
53. "New Gmail protections for a safer, less spammy inbox". Google. 3 October 2023.
54. "The New Requirements for Email Delivery at Gmail - Valimail". www.valimail.com. 3 October 2023.
55. "Sender Best Practices". senders.yahooinc.com.

Further reading

• RFC  4686 Analysis of Threats Motivating DomainKeys Identified Mail (DKIM)
• RFC  4871 DomainKeys Identified Mail (DKIM) Signatures Proposed Standard
• RFC  5617 DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)
• RFC  5585 DomainKeys Identified Mail (DKIM) Service Overview
• RFC  5672 RFC 4871 DomainKeys Identified Mail (DKIM) Signatures—Update
• RFC  5863 DKIM Development, Deployment, and Operations
• RFC  6376 DomainKeys Identified Mail (DKIM) Signatures Draft Standard
• RFC  6377 DomainKeys Identified Mail (DKIM) and Mailing Lists
• RFC  8301 Cryptographic Algorithm and Key Usage Update to DomainKeys Identified Mail (DKIM)
• RFC  8463 A New Cryptographic Signature Method for DomainKeys Identified Mail (DKIM)

External links

• DomainKeys Identified Mail (DKIM)