SPF and DMARC records for agoodmail.com

SPF for agoodmail.com

agoodmail.com publishes no SPF record. Receiving servers cannot tell which servers are allowed to send as agoodmail.com, 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 agoodmail.com

agoodmail.com 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 agoodmail.com.

Why it matters

SPF says which servers may send as agoodmail.com; 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 agoodmail.com is trusted, and whether someone else can pretend to be agoodmail.com. 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 agoodmail.com

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