SPF and DMARC records for a-bc.net
Live SPF and DMARC lookup for a-bc.net: the raw TXT records and the policy they enforce.
try:
- mail hosts
- gourmet7.spamgourmet.com
- provider
- other
- spf record
- v=spf1 mx ip4:216.75.62.81 ip4:216.75.62.102 -all
- dmarc policy
- none published
- disposable domain
- yes
- free consumer provider
- yes
SPF for a-bc.net
a-bc.net 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 a-bc.net
a-bc.net 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 a-bc.net.
Why it matters
SPF says which servers may send as a-bc.net; 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 a-bc.net is trusted, and whether someone else can pretend to be a-bc.net. 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 a-bc.net
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.