SPF and DMARC records for 74.ru
Live SPF and DMARC lookup for 74.ru: the raw TXT records and the policy they enforce.
try:
- mail hosts
- 74.ru
- provider
- other
- spf record
- v=spf1 a:smtpout.sender.ngs.ru -all
- dmarc policy
- reject
- dmarc record
- v=DMARC1;p=reject;pct=100;rua=mailto:[email protected]
- disposable domain
- no
- free consumer provider
- yes
SPF for 74.ru
74.ru publishes an SPF record; it names its senders directly rather than through include mechanisms, and the record ends in -all (hard fail): mail from a server that is not listed should be rejected.
DMARC for 74.ru
74.ru enforces DMARC at p=reject, so messages that fail alignment are dropped by receivers rather than delivered or quarantined. That is the end state most domains work towards.
Why it matters
Receivers use SPF, DKIM, and DMARC together to decide whether a message really came from 74.ru. 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 74.ru
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.