{"id":5017,"date":"2021-09-20T13:23:52","date_gmt":"2021-09-20T17:23:52","guid":{"rendered":"https:\/\/www.exchangedefender.com\/blog\/?p=5017"},"modified":"2021-09-20T13:41:00","modified_gmt":"2021-09-20T17:41:00","slug":"exchangedefender-security-compliance","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2021\/09\/exchangedefender-security-compliance\/","title":{"rendered":"ExchangeDefender Security Compliance"},"content":{"rendered":"\n
<\/div>\n\n\n\n
\"\"<\/figure><\/div>\n\n\n\n

ExchangeDefender is helping our clients and partners comply with email validation & authorization requirements. DMARC (SPF + DKIM) help prevent unauthorized hijacking\/spoofing of your domain name and are used by email services to separate legitimate email from SPAM.<\/p>\n\n\n\n

<\/div>\n\n\n\n

We’ll offer assistance for SPF + DKIM<\/h3>\n\n\n\n

In order to assure reliable email delivery, ExchangeDefender is offering assistance with SPF + DKIM rollout from September 20th through October 20th.<\/strong> All domains must be brought to compliance by October 30th, 2021 in order to continue relaying mail through ExchangeDefender. We’ll even do it for you, for free. <\/p>\n\n\n\n

For more information on our new email security standards, please see our DMARC webinar<\/a>, and read our DMARC guide<\/a>.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Every domain that uses ExchangeDefender to send or receive email is required to update their SPF and DKIM records. Failure to comply <\/em>will result in having your email bounced.<\/p><\/blockquote>\n\n\n\n

<\/div>\n\n\n\n

How to get started:<\/h3>\n\n\n\n

Step 1: Contact your DNS Administrator<\/h4>\n\n\n\n

You will need to contact your DNS administrator or DNS hosting provider to create the following DNS records:<\/p>\n\n\n\n

<\/div>\n\n\n
\n

SPF Record
DNS Record Type: TXT
DNS Record Value: \u201cv=spf1 include:proxy.exchangedefender.com -all\u201dDKIM Record
DNS Record Type: TXT
DNS Record Hostname: default._domainkey
DNS Record Value: “v=DKIM1; k=rsa; s=email;  p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwkMvl3dS3g9XbhxtD16tSx\/l+s0cxVv73\/NCHywH2HFED61k+orBj4QY96FJcUD7MOwmwjC7Igtz5P9fVOLFoMr+d8g8c5J5OIA8Xj2ap4jsEnSF3rRrCNJDxojPvtGA1+ENwGpheHtniZG\/fgVguDL+M1zXNRsYTybzKwU49tmP4RyIFIC8NEV7jqrGSVWpQSXc12JlvmLQX1J5tdnWvTR7\/NGOzyth0rYP1STKj1hHU9ZVN+x8VFiumlPdpDQBMn5Bzu\/Cs6pzrSHJqGBcVer4mccpnCOX9bG3sR7wU6nDIv3rvwIlfBymylcZruJvjsXZAZaameUBpgGgmibpkwIDAQAB”<\/p>\n<\/blockquote>\n\n\n

<\/div>\n\n\n\n

Step 2: Validate your DNS records<\/h4>\n\n\n\n

After the DNS records are published please validate them using public tools like MX Toolbox (https:\/\/mxtoolbox.com\/SuperTool.aspx<\/a>) or DMARC Analyzer (https:\/\/www.dmarcanalyzer.com\/dkim\/dkim-checker\/<\/a>). Until your DNS records validate, you are not in compliance and will have issues with email delivery.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Step 3: Turn on DKIM signing <\/h4>\n\n\n\n

After your DNS records have been published and validated, you will need to turn on DKIM signing. Go to https:\/\/admin.exchangedefender.com<\/a>, login as Domain Administrator and go to Mail Flow -> DKIM Signature<\/strong>.

Finally, click on Accounts and confirm<\/strong> that all your email addresses are listed and associated with appropriate users.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\n\n\n\n
<\/div>\n\n\n\n

We’d love to help, if you’d like us to take care of this for you free of charge please fill out this form:
https:\/\/www.exchangedefender.com\/security-lockdown<\/a><\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":50,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[33,4],"tags":[],"class_list":["post-5017","post","type-post","status-publish","format-standard","hentry","category-compliance","category-exchangedefender"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5017","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/50"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=5017"}],"version-history":[{"count":27,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5017\/revisions"}],"predecessor-version":[{"id":5049,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5017\/revisions\/5049"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=5017"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=5017"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=5017"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}