{"id":124,"date":"2021-03-18T10:15:09","date_gmt":"2021-03-18T10:15:09","guid":{"rendered":"https:\/\/prodmarc.com\/knowledge\/?p=124"},"modified":"2024-12-20T01:44:19","modified_gmt":"2024-12-20T01:44:19","slug":"how-dkim-works","status":"publish","type":"post","link":"https:\/\/knowledge.progist.net\/index.php\/2021\/03\/18\/how-dkim-works\/","title":{"rendered":"How DKIM works?"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

DKIM (DomainKeys Identified Mail) :<\/strong><\/p>\n

DKIM stands for DomainKeys Identified Mail and is used for the authentication of an email that is being sent. It is an email security standard designed to make sure messages are not altered in transit between the sending and recipient servers.<\/p>\n

DKIM uses public-key cryptography. This means that there is a secret key, that only the signer of the message knows, and a public key that everyone knows and can be used to verify the message. The signer of the email (which can be different from the sender) creates the hash and the receiver of the email can verify the hash by using the public key which is published in DNS.<\/p>\n

How DKIM works :<\/strong><\/p>\n

There are three main steps to the DKIM signing process. First, the sender identifies what fields they want to include in their DKIM signature. These fields, can include things such as the \u201cfrom\u201d address, the body and the subject as well as many others. These fields must remain unchanged in transit or DKIM authentication will fail. Second, the sender\u2019s email platform will create a hash of the text fields included in the DKIM signature. The following text fields, for example,<\/p>\n

From: Example “example@domain-name.com”
Subject: Update<\/strong><\/p>\n

will map to this hash string:<\/strong><\/p>\n

Once the hashstring is generated, it is encrypted with a private key, which only the sender has access to.<\/p>\n

Finally, after the email is sent it\u2019s up to the email gateway or consumer mailbox provider to validate the DKIM signature. To do it, they need to find the public key that will perfectly match the private key, thereby decrypting the DKIM signature back to its original hash string.<\/p>\n

Then, the receiver generates its own hash of the fields included in the DKIM signature and compares it with the hash string they just decrypted. If they match, we know both that the fields in the DKIM signature were not changed in transit and the signer of the email truly owns the email.<\/p>\n

DKIM DNS record example:<\/strong><\/p>\n

selector(s=)._domainkey.domain(d=). TXT v=DKIM1; p=public key<\/strong><\/p>\n

s= indicates the selector record name used with the domain to locate the public key in DNS. The value is a name or number created by the sender. s= is included in the DKIM signature.<\/p>\n

d= indicates the domain used with the selector record (s=) to locate the public key. The value is a domain name owned by the sender. d= is included in the DKIM signature.This article mentions your favorite hats at super low pricesThis post is sponsored by https:\/\/www.fakewatch.is\/product-category\/richard-mille\/rm-061\/ our partners Wigs Choose from same-day delivery drive-up delivery or order pickup.\n<\/p>\n

p= indicates the public key used by a mailbox provider to match to the DKIM signature.<\/p>\n

Here is what the full DNS DKIM record looks like for progist.net:<\/strong><\/p>\n

20190919._domainkey.progist.net 300 IN TXT “v=DKIM1; g=*; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDKQ1Dcff5lmH+uwAP\/YdYN3b\/
c5CEtuRuYVDksPggVwjQVvXjG5tiBT+9xb78d40x8gD04KasVEx9IZyJBAOFX1fl7fsSN\/
sN7y4ijam3dOUq9PBPgvGgwTmFB7oLbTSSgFvCuIAtlAwTSu9aL34cD9XS\/
exkmmY57au8stCW9FQIDAQAB”<\/p>\n

The selector (s=): 20190919
The domain (d=): progist.net
The version (v=): DKIM1
The public key (p=): MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDKQ1Dcff5lmH+uwAP\/
YdYN3b\/c5CEtuRuYVDksPggVwjQVvXjG5tiBT+9xb78d40x8gD04KasVEx9IZyJBAOFX1fl7fsSN\/
sN7y4ijam3dOUq9PBPgvGgwTmFB7oLbTSSgFvCuIAtlAwTSu9aL34cD9XS\/exkmmY57au8stCW9FQIDAQAB<\/p>\n

 <\/p>\n

v=<\/strong> is the version of the DKIM record. The value must be DKIM1 and be the first tag in the DNS record.<\/p>\n

p=<\/strong> is the public key used by a mailbox provider to match to the DKIM signature generated using the private key. The value is a string of characters representing the public key. It is generated along with its corresponding private key during the DKIM set-up process.<\/p>\n

k=<\/strong> indicates the key type. The default value is rsa which must be supported by both signers and verifiers.<\/p>\n

g=<\/strong> is the granularity of the public key. The value must match the local-part of the i= flag in the DKIM signature field (i= local-part@domain.com) or contain a wildcard asterisk (*). The use of this flag is intended to constrain which signing address can use the selector record.<\/p>\n

<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

DKIM (DomainKeys Identified Mail) : DKIM stands for DomainKeys Identified Mail and is used for the authentication of an email that is being sent. It is an email security standard<\/p>\n

Continue ReadingHow DKIM works?<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_eb_attr":"","om_disable_all_campaigns":false,"footnotes":""},"categories":[6],"tags":[39,55],"class_list":["post-124","post","type-post","status-publish","format-standard","hentry","category-dkim","tag-dkim","tag-dkim-working"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/knowledge.progist.net\/index.php\/wp-json\/wp\/v2\/posts\/124","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/knowledge.progist.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/knowledge.progist.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/knowledge.progist.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/knowledge.progist.net\/index.php\/wp-json\/wp\/v2\/comments?post=124"}],"version-history":[{"count":3,"href":"https:\/\/knowledge.progist.net\/index.php\/wp-json\/wp\/v2\/posts\/124\/revisions"}],"predecessor-version":[{"id":3349,"href":"https:\/\/knowledge.progist.net\/index.php\/wp-json\/wp\/v2\/posts\/124\/revisions\/3349"}],"wp:attachment":[{"href":"https:\/\/knowledge.progist.net\/index.php\/wp-json\/wp\/v2\/media?parent=124"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/knowledge.progist.net\/index.php\/wp-json\/wp\/v2\/categories?post=124"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/knowledge.progist.net\/index.php\/wp-json\/wp\/v2\/tags?post=124"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}