SPF and DMARC records for 0jylaegwalss9m6ilvq.tk

SPF for 0jylaegwalss9m6ilvq.tk

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

0jylaegwalss9m6ilvq.tk 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 0jylaegwalss9m6ilvq.tk.

Why it matters

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

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