Loading...

Knowledge Base

How Do I Edit DKIM Settings?

DomainKeys Identified Mail, also known as DKIM, is an email authentication system that adds a digital signature to the email header. It verifies that the email was sent from the real sender and has not been tampered with during transit. DKIM uses public-key cryptography to create a signature that can be verified on the recipient's email server. You can edit DKIM settings to ensure your email security is properly configured.

Important: This article applies to customers with Edge Desk, ProMail, and Webmail version 7.10.2 email platform. To determine your email platform, check How Do I Determine My Email Platform?

In this article, we will discuss:

How DKIM Protects Your Email

DKIM plays a crucial role in email security. It provides three key benefits:

  1. Prevents email spoofing – DKIM prevents email spoofing by verifying the genuineness or authenticity of the sender's email address.
  2. Protects email integrity – DKIM protects email integrity by making sure that the email has not been tampered with during transit.
  3. Improves email deliverability – Emails that fail DKIM verification are more likely to be marked as spam or rejected by the recipient's email server, thereby improving email deliverability and lowering the risk of being marked as spam.

 

How to Manage DKIM Settings

Follow the steps below to enable and adjust the DKIM Settings.

  1. Log in to your Account Manager via https://www.networksolutions.com/my-account/login.
     
  2. On the left side of the page, click Email.
    Edit DKIM
     
  3. On the Email page, select the mailbox for which you wish to adjust the DKIM settings for, then click Manage.
     
  4. Click DKIM Manager to launch the DKIM Control Panel.

    Edit DKIM
     
  5. You will then be taken to the DKIM Manager.
     
  6. To enable DKIM, make sure you select Configure with auto-generated keys.

    Edit DKIM
     
  7. Then, select the DMARC policy.

    Edit DKIM
    • The DMARC policy indicates to your receivers that your messages are DKIM-protected. It also tells them what to do if messages do not pass, are flagged as junk, or are rejected.
    • It is recommended that DMARC policies be introduced gradually. Begin with a setting of None, move to Quarantine, and finally to Reject. Monitor your DMARC reports at each stage to ensure messages are signed and not spoofed.
       
  8. Click DKIM Manager to launch the DKIM Control Panel.
Note: An email address is required to configure your DMARC policy. It will be used to receive reports on authenticated messages and flagged messages, including the reasons why. The email needs to be under the same domain as the DKIM domain. If not, you will need to publish a DNS report record to allow it to receive reports from a different domain.
  1. Please take note of the following DMARC options:
     
    • None - No action is needed, but it is useful for monitoring.
    • Quarantine - Message should be set aside.
    • Reject - Message should be rejected.
       
  2. Enter the preferred email address that will receive the DMARC reports in the Send Reports to field. The email address must be under the domain that you are managing.

    Edit DKIM
     
  3. You have enabled DKIM, and your DNS settings will be automatically updated as long as your domain name is on our nameservers.

    If your domain is not on our nameservers, click the link that says View DNS TXT Record Information after you have enabled DKIM and provide these records to your nameserver host.
    Edit DKIM

 

Review

Editing DKIM settings is an essential step in protecting your domain and improving email deliverability. By enabling DKIM, you ensure that each message carries a digital signature verifying it came from the real sender and was not altered in transit. This not only prevents email spoofing but also safeguards your brand reputation. Combined with proper DMARC policies, DKIM helps you maintain email integrity and reduce the risk of your messages being flagged as spam.

Did you find this article helpful?

 
* Your feedback is too short

Loading...