Domain authentication is the process that allows you to tell email service providers that Method is a trusted sender from your domains. Domain authentication is about security and deliverability, as it helps you protect your brand's reputation and ensures your emails successfully reach recipients’ inboxes.

Authenticating your domain involves publishing DNS records to establish your domain reputation.

The domain authentication section is on your Account Settings page, under Communications. To verify and authenticate a custom domain, follow these steps:

It's now time to log into your DNS provider.

Within Method, you can manually set up MX, SPF, DKIM, and DMARC records when adding a custom domain.

This is done by unchecking Use automatic security (recommended) when adding a domain.

It’s important to note that you will not be required to modify your current records. Instead, we are asking our customers to add new records to their DNS, which will allow Method to send emails on your behalf without affecting your current setup.

To do this we provide unique sub-domains for our email sending services, ensuring that there’s no interference with your main domain's email flow, or existing DNS settings.

Here’s how you can proceed with adding the 3 provided records:

Domain-based Message Authentication, Reporting, and Conformance (DMARC) comprises a set of policies determining actions when DKIM and SPF configurations are incorrect. It also links the sender's domain with the information in the From: header, providing enhanced reporting from mail recipients.

DMARC is a TXT record you need to add to your DNS records. Configuring your DMARC is required to send emails via Method from an authenticated domain. If you do not have a DMARC policy enabled, your emails may not be delivered to recipients' inboxes.

DMARC supports three main policy configurations:

Implementing a DMARC policy of "Quarantine" or "Reject" will require a proper DKIM record setup for your sending domain, or else your mail from Method will fail the DMARC test. Ensure you set up DKIM for all your sending domains before setting up a strict DMARC record.

The DMARC RUA tag allows you to receive DMARC Aggregate Reports at an email address or addresses. These reports can provide valuable insight into domain spoofing or phishing attacks impersonating your domain, which may impact your business and reputation.

Be advised when setting the email address to receive reports you will want to select one that will be solely dedicated to receiving these reports, as there can be hundreds to thousands per day depending on your mail volume. It is also recommended to use a DMARC report processing service so that you will be able to make sense/take action on these reports without being inundated.

DNS providers—also called “registrars,” “web hosting,” or “domain hosting” companies—are the entities that allow you to add DNS records.

Typically, your domain is hosted by the company that you bought the domain from. Popular domain vendors include GoDaddy, CloudFlare, and Siteground. If you’re not sure of your DNS provider, you can use this tool.

It’s important to note that you will not be required to modify your current MX, SPF, DKIM, or DMARC records. Instead, we are asking our customers to add new records to their DNS, which will allow us to send emails on your behalf without affecting your current setup.

To do this we provide unique sub-domains for our email sending services, ensuring that there’s no interference with your main domain's email flow, or existing DNS settings.

Here’s how you can proceed with adding the 3 provided records:

Once an administrator has authenticated a domain on an account, all users will be able to modify their notification address to send from that domain. Users will need to navigate to Profile - Email Settings, and select the checkbox “Send from authenticated domains.” The domain name will then populate and they can input their email prefix.

We’ve got your back. When on the Customize Tab, go to My Account, Default Email Preferences, and click on the hyperlink in the first paragraph to navigate to Method: New, where you can authenticate a domain. This won’t migrate you over to Method: New, it just allows you to make use of the new domain authentication functionality while continuing to use Classic. Win-win scenario!