 In this session, we're going to be discussing domain keys identified mail, also referred to as DKIM or DKIM. I'm probably going to end up swapping back and forth between either of those acronyms during this session, so why don't we get right into it. Domain keys identified mail, DKIM, is a method to prevent spoofing. We've got another very long explanation here, but ultimately it comes down to, just like SPF, DKIM is a way to prevent jerks from spoofing emails. You may ask why you need DKIM if you're using SPF. The simple answer is that it just provides an additional method of preventing messages from being spoofed. What it does is embed information into the header of the emails, which helps identify that the sender of that message is valid by embedding a key into that header, which can be compared against a private key that is just kind of stored on the server so that we can verify whether or not that email came from a source that should have been sending that email. SPF and DKIM are also used, they're both used by DMARC, which is another layer of security that we're going to be discussing later. But in order for things to pass DMARC, they have to pass SPF and or DKIM, so enabling DKIM allows us to provide that authentication scenario for DMARC to work properly.