SPF and DMARC records for aetheron.cfd

SPF for aetheron.cfd

aetheron.cfd publishes no SPF record. Receiving servers cannot tell which servers are allowed to send as aetheron.cfd, so mail from the domain is easier to spoof and more likely to land in spam. A basic record (v=spf1 include:… -all) fixes that, and Spaw's risk score adds a small weight to addresses at domains without one.

DMARC for aetheron.cfd

aetheron.cfd publishes no DMARC record. Receivers have no policy to apply when SPF or DKIM fails, and the domain owner receives no aggregate reports about who is sending as aetheron.cfd.

Why it matters

SPF says which servers may send as aetheron.cfd; DKIM signs the messages; DMARC tells receivers what to do when neither checks out and reports back to the owner. Together they decide whether mail from aetheron.cfd is trusted, and whether someone else can pretend to be aetheron.cfd. For verification they are a domain-quality signal: Spaw folds a missing SPF record into the risk score and reports has_spf and dmarc_policy on every email and domain lookup.

More checks for aetheron.cfd

• MX records for aetheron.cfd
• Disposable domain check for aetheron.cfd
• The same answer over the API: GET /api/v1/email/domain/aetheron.cfd