SPF and DMARC records for 14p.in
Live SPF and DMARC lookup for 14p.in: the raw TXT records and the policy they enforce.
try:
- mail hosts
- eforward2.registrar-servers.com, eforward3.registrar-servers.com, eforward1.registrar-servers.com, eforward4.registrar-servers.com, eforward5.registrar-servers.com
- provider
- other
- spf record
- v=spf1 include:spf.efwd.registrar-servers.com ~all
- dmarc policy
- none published
- disposable domain
- yes
- free consumer provider
- no
SPF for 14p.in
14p.in 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 14p.in
There is no DMARC record for 14p.in, so failed SPF or DKIM checks lead nowhere: no quarantine, no rejection, and no reports back to the owner.
Why it matters
Receivers use SPF, DKIM, and DMARC together to decide whether a message really came from 14p.in. A domain with a strict SPF record and an enforcing DMARC policy is hard to spoof and easier to deliver for; one without either is neither. Spaw reports has_spf and dmarc_policy on every lookup and adds a small risk weight when SPF is missing.
More checks for 14p.in
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.