DKIM Signature of your Message:

{$ DKIMValue $}

Your DKIM Selector:

{$ DKIMSelector $}

DKIM, which stands for DomainKeys Identified Mail, is an email authentication method designed to detect email spoofing and ensure the integrity of email messages. It allows the sender to digitally sign their email messages, providing a way for the recipient to verify that the message was indeed sent by the claimed sender and that it hasn't been altered during transit.

Here's a brief overview of how DKIM works:

1. Digital Signature: The sender generates a digital signature for each outgoing email using a private key. This signature is added to the email's headers.
2. Public Key in DNS: The sender publishes the corresponding public key in the DNS (Domain Name System) records for the sending domain. This allows anyone receiving an email from that domain to retrieve the public key.
3. Verification: When the recipient's email server receives the email, it uses the sender's public key to verify the digital signature. If the verification is successful, it means that the email is from the claimed sender and hasn't been tampered with during transmission.

DKIM helps prevent email spoofing, phishing, and tampering. It's one component of a broader set of email authentication mechanisms that also includes SPF (Sender Policy Framework) and DMARC (Domain-based Message Authentication, Reporting, and Conformance).

In the context of the email headers you provided earlier, the DKIM-Signature field contains information about the DKIM signature applied to the email. It includes details such as the signing algorithm (`a`), the selector (`s`) indicating which public key to use, and the signature itself (`b`). The verification process involves using the public key to check the signature's validity.

• Your rDNS/PTR Record: {$ RDNSValue $}
• Your server IP: {$ MailServerIP $}
• Your HELO Domain: {$ HELO $}

Reverse DNS (rDNS) or Pointer (PTR) records are essentially the opposite of forward DNS records. While forward DNS maps domain names to IP addresses, reverse DNS does the reverse: it maps IP addresses to domain names. A PTR record is a type of DNS record that resolves an IP address to a domain or hostname. It is commonly used for various purposes, including:

• Email authentication: Many email servers use reverse DNS to verify that the domain name associated with an email sender's IP address matches the domain name declared in the sender's email headers. This helps in detecting and preventing email spoofing.
• Troubleshooting network issues: Network administrators often use reverse DNS to troubleshoot issues related to IP addresses. By looking up the PTR record for an IP address, they can identify the corresponding domain name and gather information about the owner of that IP address.
• Security: Reverse DNS can also be used as part of security measures to identify potentially malicious activity. For example, it can be used to check if an IP address associated with a network request resolves to a known domain name or if it is associated with suspicious or blacklisted domains.

In summary, rDNS or PTR records play a crucial role in internet infrastructure, email authentication, network troubleshooting, and security measures. They provide a way to map IP addresses to domain names, enabling various systems and services to verify and identify connections and communication sources.

Your MX Records are:

{$ MailServer $}

MX (Mail Exchange) records are DNS (Domain Name System) records that specify the mail servers responsible for receiving email on behalf of a domain. These records are used to route email messages to the correct mail servers based on the recipient's email address domain.

Each MX record contains two main components:

• Priority: This indicates the order in which mail servers should be contacted. Lower values indicate higher priority. If multiple MX records exist for a domain, the sending mail server will attempt to deliver the email to the mail server with the lowest priority first.
• Mail Server Domain Name: This specifies the domain name of the mail server responsible for receiving email for the domain. It is typically an A or AAAA record that resolves to an IP address.

Here's an example of an MX record:

example.com. IN MX 10 mail.example.com.

In this example:

• Domain Name: example.com.
• Class: IN (Internet).
• Record Type: MX (Mail Exchange).
• Priority: 10
• Mail Server Domain Name: mail.example.com.

When an email is sent to an address at `example.com`, the sending mail server will query the DNS for the MX records of `example.com`. It will then attempt to deliver the email to the mail server(s) listed in the MX records, starting with the one with the lowest priority. If the delivery fails for any reason, the sending server may attempt delivery to the next mail server listed in the MX records.

Matches your server IP address {$ MailServerIP $} against most popular IPv4 blocklists.

Blacklist	Status	Action
Spamhaus SBL Advisory	{$ sblText $}	Learn More NO ACTION NEEDED
Spamhaus XBL Advisory	{$ xblText $}	Learn More NO ACTION NEEDED
Spamhaus PBL Advisory	{$ pblText $}	Learn More NO ACTION NEEDED