FAQ

No, you don't need to give us your DNS settings or any other access. With our EasySPF, we will provide you with a single include: mechanism that you will apply in your DNS, and every update/change in your SPF Record will be managed from your EasyDMARC account portal.

SPF specification has a limit on the number of DNS lookups (10) required to fully resolve an SPF record. This is a highly critical limitation to prevent Denial of Service (DoS) attacks. If you are using multiple Third-Party services for your various email strategies, it can be easy to exceed this limitation. Check our EasySPF solution on how to overcome this limitation.

For adding two SPF includes in your single SPF record, you need to include the two include: mechanisms next to each other for example: v=spf1 include:example.com include:example2.com ~all.

If your SPF record has more than 450 characters, this may lead to SPF record validation errors. To solve this issue, you need to adjust your SPF Record or check our EasySPF solution.

SPF checks against the Return-Path: or MailFrom: address domain for verification. If the address domain doesn't match with your From: domain, then SPF will fail due to misalignment. Check out Why is DMARC Failing article for more information.

DKIM selector is part of the DKIM record and it allows publishing multiple DKIM keys for a domain. Check our article for more information.

DKIM works with Private and Public keys. Private keys are stored in email servers, while Public keys are implemented in domain's DNS. There are multiple use-cases for DKIM implementation:

1. If you are using Third-Party ESPs (Google, Microsoft365, Mailchimp, etc.) DKIM Public keys are obtained from their portals. ESPs won't share their Private Keys for privacy and security concerns.
2. For dedicated servers, EasyDMARC's DKIM Generator tool can be used. You will securely store the Private key in your own server, while implementing the Public key in your DNS.

Senders should use 1024 to 4096-bit keys. Google and some other receivers consider keys smaller than 1024-bits insecure, and will not use them for authentication.

There can be multiple cases for this. Most common cases include:

1. Syntax issue with subdomain added in the "Host" or "Name" section. DMARC needs to be implemented on _dmarc.yourdomain.com subdomain. Make sure you got that right.

2. Some DNS Zones (e.g GoDaddy) will not inherit but overwrite the subdomain name once added in the "Host" section. (For e,g, when you input your whole subdomain "_dmarc.yourdomain.com", GoDaddy will read that as "_dmarc.yourdomain.com.yourdomain.com" which invalidates your DMARC Record. To fix this, simply remove your domain name and just keep "_dmarc".

3. You have multiple DMARC Records implemented in your DNS. Make sure you have only one DMARC TXT Record on per your root/subdomain level.

4. You are still with DMARC None policy (Monitoring mode) and you are getting an error indicating "DMARC record is valid, but you are not protected against email spoofing and phishing". This is a warning sign from our side that your DMARC Policy is not enforced, and your domain is still open to any spoofing attempts.

That is because your DMARC record policy is p=none; which is the monitoring phase to ensure all your email vendors pass the DMARC check, when you later enforce your DMARC record to higher levels then that alert will disappear. That means to change your policy from p=none; to p=quarantine; and later p=reject.

DMARC enforcement can be achieved after making sure that all your outgoing legitimate servers are properly authenticated . Contact our Support team to discuss further.

Major Providers like Google & Verizon Media have chosen to simplify the reporting by sending Daily reports only (every 24 hours), even if admins have a shorter "ri" period tag included in their DMARC Record. You can check our article for a detailed overview of DMARC Tags.

BIMI is a fairly new protocol and not many ISPs currently support it. Also, for BIMI to work, first you need to have an enforced DMARC Policy (Quarantine or Reject). We at EasyDMARC highly recommend our users to first start with their DMARC enforcement journey, and then proceed forward with BIMI.

EasyDMARC's BIMI Converter Tool can be used to convert BIMI SVG images and logos to BIMI-compatible SVG Tiny P/S format. You can also check our article on how to convert a PNG/JPEG to BIMI-Compatible SVG format.

Currently, VMCs are being issued by two BIMI-qualified Certification Authorities, DigiCert and Entrust Datacard. Contact them for more details.

If you've just added or updated your DMARC Record, it will take up to 72 hours (3 days) until the first DMARC reports are received. After that, reports are usually updated every 24-32 hours.

If you've just added or updated your DMARC Record, it will take up to 72 hours (3 days) until the first DMARC reports are received. After that, reports are usually updated every 24-32 hours.

There are 2 different types of DMARC reports: Aggregate report and Failure (formerly known as Forensic report). Check our article for more information.

EasyDMARC segments DMARC Reports into 4 tabs to make your DMARC enforcement journey easier and successful.

DMARC Compliant: Under this tab, our system discovers and shows you all the email sources that are sending DMARC Compliant emails on your domain behalf. These are your legitimate sources that are meeting compliance via SPF and/or DKIM authentication and alignment.

DMARC Non-Compliant: This tab identifies all your sending sources that are failing DMARC compliance checks. These sources are failing both SPF and DKIM authentication and alignment.

Threat/Unknown: This tab identifies all the spoofing or fraudulent attempts on your domain behalf that are being sent from Source IPs that are blacklisted in multiple RBLs (Blacklist checks) or a Source IP which doesn't resolve to a Reverse DNS (PTR). You may, at some point, discover your legitimate servers labeled under this tab, which indicates your server is either blacklisted in multiple lists or lacks Reverse DNS (PTR).

Forwarded: Forwarding happens when your receiver forwards your email to another recipient. This is usually caused by Auto-Forwarding or Routing rules that are applied in major Mailbox Providers.

With access to User Management (available in the Premium and Business packages), you can add additional users directly from the "User Access" tab available in your EasyDMARC portal.

Yes. If your monthly email volume doesn't exceed 10,000 mark, you can stay in our Free tier with limited features.

Yes, we at EasyDMARC are highly flexible and can adjust to your needs.

Yes, we do. It mainly depends on the subscription and the agreement plan.

EasyDMARC supports many of the most popular SAML 2.0 compliant Single Sign-On (SSO) providers, including Azure AD, Okta, OneLogin, Google SSO, etc. Contact our Support to get the applicable how-to-setup documentation.