SPF and DMARC records for goemailgo.com
Live SPF and DMARC lookup for goemailgo.com: the raw TXT records and the policy they enforce.
try:
- mail hosts
- mx1-hosting.jellyfish.systems, mx2-hosting.jellyfish.systems, mx3-hosting.jellyfish.systems
- provider
- other
- spf record
- v=spf1 +a +mx +ip4:162.213.251.35 include:spf.web-hosting.com ~all
- dmarc policy
- none
- dmarc record
- v=DMARC1; p=none;
- disposable domain
- yes
- free consumer provider
- yes
SPF for goemailgo.com
goemailgo.com publishes an SPF record; it authorises 1 included sender list, and the record ends in ~all (soft fail): mail from unlisted servers is marked suspicious but usually still delivered.
DMARC for goemailgo.com
The DMARC policy for goemailgo.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 goemailgo.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 goemailgo.com is trusted, and whether someone else can pretend to be goemailgo.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 goemailgo.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.