Should I use hyphenated domains for email sending and how does it affect my DMARC policy?

Email marketer from Gmass responds saying that each distinct domain, including hyphenated ones, needs its own email authentication (SPF, DKIM, DMARC) setup to ensure deliverability and avoid being flagged as spam.

Email marketer from SendPulse notes that using similar-looking domains (like hyphenated versions) can be risky, as they can be easily spoofed by phishers, potentially damaging your brand reputation and deliverability.

Email marketer from StackExchange notes that its better to use a subdomain over a separate domain for email marketing, as authentication is made easier and you can protect your main domain reputation.

Email marketer from Email Geeks explains that related domains (cousin domains) are often seen as a sign of being a spammer trying to protect the primary domain.

Email marketer from Reddit explains to avoid hyphenated domains or 'cousin domains', as they can be mistaken for phishing attempts and may negatively affect deliverability, requiring separate and careful authentication.

Email marketer from EmailBlogger.com shares that sending email using a separate domain is a good idea to protect your primary domain reputation. However, each new domain requires its own unique setup of SPF, DKIM and DMARC to function properly.

Email marketer from Email Geeks says that if anti-spam/anti-abuse systems need to guess if a domain is related to a real domain, it's already a problem, advising against this practice.

Email marketer from Litmus suggests that using a separate domain offers a clear separation of email reputation, helping isolate deliverability issues, but that hyphenated domains require a full new setup of authentication and reputation building.

Email marketer from Mailjet shares that using separate domains (including hyphenated ones) can isolate reputation, but requires setting up authentication (SPF, DKIM, DMARC) independently for each, increasing complexity.

Email marketer from EmailonAcid.com responds suggesting that using different domains or subdomains for email sending can increase the complexity of your authentication and deliverability strategy. Consider this before making the change.

Email marketer from Email Marketing Forum shares that they had deliverability problems using a hyphenated domain because it was flagged as a potential phishing site. Recommends using a subdomain instead.

Expert from Email Geeks explains that a hyphenated domain is a different domain, not a subdomain, and is a completely different entity altogether.

Expert from Spam Resource responds saying that hyphenated domains are more likely to get filtered and have deliverability issues because they are often used in phishing and spam campaigns. Establishing a good reputation and authentication will be an uphill battle. Also, each domain needs its own DMARC policy.

Expert from Word to the Wise answers that while separating sending domains for transactional vs marketing mail is good, hyphenated domains are risky. They advise using subdomains instead to inherit authentication and avoid confusion.

Expert from Email Geeks notes that cousin domains/lookalike domains were more common in the past but are now considered a bad practice, despite some platforms still recommending them due to outdated guidance.

Expert from Email Geeks shares that cousin domains/lookalike domains are a bad idea because bad actors can register similar domains, potentially tricking recipients and leading to spoofing.

Documentation from Microsoft responds indicating that different domains each require their own SPF records; the same principle applies to DMARC, therefore hyphenated domains are considered separate and require individual DMARC setup.

Documentation from DMARC.org explains that each domain sending email on its behalf needs its own DMARC record. Domains with hyphens are distinct and require separate DMARC configuration.

Documentation from Google explains that DMARC policies apply to subdomains unless a specific subdomain policy is defined. Hyphenated domains, being distinct, do not inherit the DMARC policy. Each domain needs its own DMARC record.