SPF and DMARC records for objectmail.com
Live SPF and DMARC lookup for objectmail.com: the raw TXT records and the policy they enforce.
try:
- mail hosts
- smtp.trashmail.com
- provider
- other
- spf record
- v=spf1 mx a a:a.mxout.trashmail.com a:b.mxout.trashmail.com -all
- dmarc policy
- none
- dmarc record
- v=DMARC1; p=none; rua=mailto:[email protected]; pct=100; adkim=r; aspf=r
- disposable domain
- yes
- free consumer provider
- yes
SPF for objectmail.com
objectmail.com publishes an SPF record; it names its senders directly rather than through include mechanisms, and the record ends in -all (hard fail): mail from a server that is not listed should be rejected.
DMARC for objectmail.com
The DMARC policy for objectmail.com is p=none: the domain collects authentication reports but asks receivers not to act on failures. Spoofed mail is still delivered; the owner just gets told about it.
Why it matters
SPF says which servers may send as objectmail.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 objectmail.com is trusted, and whether someone else can pretend to be objectmail.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 objectmail.com
checked 2026-09-03 · sources: live-dns 2026-09-03 · disposable-domains 2026-09-02 · free-provider-domains 2026-09-02 · mx-provider-patterns 2026-09-03
Need this at scale?
The Spaw API runs the same checks plus mailbox-level SMTP verification, batch and bulk endpoints, and list monitoring — 10 free lookups a month, no card required.