Our SPF record checker will try to validate SPF macro’s you use.
If this fails, the default behaviour is to still allow this source. The record will first try to match the sending source to another mechanism. If you use the mechanism ‘all’ with a “+” qualifier this means you essentially allow anybody to send email on your behalf. We have detected content which is not in the SPF specification. The PTR mechanism is slow and not as reliable in comparison with other mechanisms in case of DNS errors therefore we strongly recommend to not use the PTR mechanism. The PTR mechanism validates if the DNS reverse-mapping for an exists and if it’s able to point to a domain name within a particular domain. Instead of resolving a domain name to an IP address, the PTR record resolves an IP address to a domain name. We recommend not to use PTR as this is a deprecated mechanism and several senders may (completely) ignore your SPF record if you use this.The function of a PTR record is the opposite of an A record. When using SPF, you can only perform 10 (nested) DNS lookups. Therefore, you should always update your SPF record rather than entering a new record beside the existing one. If you publish multiple SPF records (v=spf1), this will invalidate your SPF record.
You can only have 1 SPF record in DNS for each SPF version.
Logically we require a SPF record in your DNS so we can validate it. The SPF Record Checker Will Validate SPF Records On:
0 kommentar(er)
