SPF and DMARC records for 171646.app

SPF for 171646.app

171646.app publishes no SPF record. Receiving servers cannot tell which servers are allowed to send as 171646.app, 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 171646.app

171646.app 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 171646.app.

Why it matters

SPF says which servers may send as 171646.app; 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 171646.app is trusted, and whether someone else can pretend to be 171646.app. 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 171646.app

• MX records for 171646.app
• Disposable domain check for 171646.app
• The same answer over the API: GET /api/v1/email/domain/171646.app