TTL | |
Address |
The SPF record is basically useful for confirming the server that the e-mail is coming from, determining that it is not fake, and also preventing harmful e-mails.
Although there is more than one method for this, you can use our SPF inquiry page offered to you by Atak Domain as the first method. As another method, when you type the CMD command after entering the run application in the start menu on your own computer's terminal screen, you can perform SPF querying through the houses that appear.
SPF records contain a version number for each record. This version number starts with the characters "v = spf1". Starting with this version, there are unlimited registrations from start to finish.
In fact, although these records are directives, these so-called directives are usually mechanisms that define the authority of the post, sometimes hitting a qualifying and clear IP address in the optional location, or sometimes no hits. Accordingly, the first mechanism that shows a hit clearly reveals the evaluation result of the desired SPF record.
The evaluation result in SPF records depends on certain rules. Within the framework of these rules;
• When the Q-Syntax position is (+), the “Pass” result code is obtained and the authorized sending server is defined and a positive result is obtained as standard.
• Although the result is "Fail" in the (-) position, the IP is not authorized and if there is an e-mail from the source, it is sent back incorrectly.
• In the case of (~) position, while the result code is evaluated as “SoftFail”, servers may be defined for unauthorized e-mail. But this error is handled deliberately.
• Finally, the “Neutral” result appears with the (?) Q-Syntax position. In this case, since the e-mail server that sent the e-mail clearly defines the legitimacy of the rules, this e-mail will be accepted.
There are common operating mechanisms that are clearly seen in SPF records. Among these mechanisms, depending on the state of the instruction;
• In the All mechanism, the instruction is always valid.
• In the query performed with the domain name in the MX mechanism, the MX record and the MX IP address are included.
• In the IPv4 mechanism, the sender's IP address or the specified IPv4 subnet contains the IPv4 address specified in the query.
• In the IPv6 mechanism, the IP address of the sending server or the specified IPv6 subnet is considered the IPv6 address specified in the query.
• The MX record of the domain name and the MX IP address is included in the content, together with the query made in the A mechanism.
• For the domain name specified in the Include mechanism, an additional separate SPF request is requested to include the sender's IP address.
• Another domain name's SPF record in the redirect mechanism also legitimizes the sender's IP address.
• In the Exists mechanism, the IP address of the sender is authorized in the context of a client connection or different criteria within the framework of RFC7208.
At Atak Domain, our technical personnel will assist you in creating, querying, and processing SPF records every day, thanks to uninterrupted expert support for you.
We are with you whenever you need it!