SPF and DMARC records for 10963rip1.mimimail.me
Live SPF and DMARC lookup for 10963rip1.mimimail.me: the raw TXT records and the policy they enforce.
try:
- mail hosts
- mx.mimimail.me
- provider
- other
- spf record
- no
- dmarc policy
- none published
- disposable domain
- yes
- free consumer provider
- no
SPF for 10963rip1.mimimail.me
10963rip1.mimimail.me publishes no SPF record. Receiving servers cannot tell which servers are allowed to send as 10963rip1.mimimail.me, 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 10963rip1.mimimail.me
10963rip1.mimimail.me 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 10963rip1.mimimail.me.
Why it matters
SPF says which servers may send as 10963rip1.mimimail.me; 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 10963rip1.mimimail.me is trusted, and whether someone else can pretend to be 10963rip1.mimimail.me. 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 10963rip1.mimimail.me
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.