SPF (Sender Policy Framework) is a TXT record that lists which servers are authorized to send mail for a domain. Receiving mail systems check the SPF record during delivery and may reject or quarantine mail from unlisted senders.

SPF Record Check for semicvetic.com

SPF record has problems

Raw record

v=spf1 include:_spf.inboxer.pro include:amazonses.com include:_spf.sent2mail.com include:spf.retailcrm.pro include:_spf.timeweb.ru a mx ~all

DNS lookups: 13 of 10

Warnings~all (soft fail) marks unauthorized mail as suspicious but does not reject it outright. Learn more →

SPF requires more than 10 DNS lookups — receivers will return PermError.
Remove unused include: chains or flatten them into ip4:/ip6: ranges; RFC 7208 §4.6.4 caps total DNS-resolving mechanisms at 10.
Learn how to fix this →

The record above is parsed for the policy mechanism (~all soft-fail vs -all hard-fail vs ?all neutral) and the list of allowed senders. SPF has a 10-DNS-lookup hard limit per RFC 7208 — the count above shows where this domain stands.

A missing or syntactically invalid record means receivers fall back to local heuristics — often unfavorable. Hard-fail (-all) gives the strongest guarantee but breaks legitimate forwarding; soft-fail (~all) is the common production compromise. If lookups approach the 10 limit, consolidate include: chains.

Raw record

Warnings?~all (soft fail) marks unauthorized mail as suspicious but does not reject it outright. Learn more →

SPF requires more than 10 DNS lookups — receivers will return PermError.

Warnings~all (soft fail) marks unauthorized mail as suspicious but does not reject it outright. Learn more →