SPF is configured for domain
The Domain does not have SPF.
To avoid identity theft, it is strongly recommended to configure SPF.
SPF definition 0.000s
DMARC is configured for domain
The Domain does not have DMARC.
To avoid identity theft, it is strongly recommended to configure DMARC.
DMARC definition 0.000s
DKIM is configured for domain
We do not detect any DKIM record for this domain.
It is strongly recommended to configure DKIM. Note: You could use a service like Mailout to fix this problem. Click on below link to know more
mailout DKIM definition 0.000s
When a sending server makes a connection to the recipient server, the recipient server notes the sending IP address and performs a reverse lookup, called a PTR lookup, named after the type of DNS record used. If the result of the reverse lookup matches the result of a forward DNS Lookup, then it's much more likely that the message is legitimate. If the IP address doesn't match, it's much more likely that the sending address was spoofed and therefore much more likely that it's unwanted and could be considered spam.
documentation 0.000s
MX must be a domain, not an IP.
RFC 0.000s
According to the RFC 1034 and 2181 CNAME records should not be used with NS and MX
RFC RFC 2.314s
The IP of the SMTP servers must be different if it is no longer reachable.
0.000s
MX servers are accessibles
Smtp servers that are listed in DNS area must be accessible, otherwise, there is a risk that emails may be lost
0.000s
According to the RFC 2181, smtp server should accept HELO command
RFC 0.000s
According to the RFC 2181, smtp server should accept EHLO command
RFC 0.000s
STARTTLS command is accepted
STARTTLS turns an unencrypted connection into a secure connection. Note: You can use a service like altospam to solve this problem. Click on the link below to learn more
0.000s
EXPN command is now considered to be a security risk, spammers being able to harvest valid e-mail addresses via each mailing list.
0.000s
As the EXPN command, VRFY is used by spammers to verify an address.
0.000s
MX servers are not open relay
If a server is open relay, there is a risk that spammers use your server to send illegitimate mail.
0.000s
MX servers accept abuse@ address
According to the RFC 2142, SMTP server should accept abuse@yourDomain as a recipient.
RFC 0.000s
MX servers accept postmaster@ address
According to the RFC 5321, SMTP server should accept postmaster@yourDomain as a recipient.
RFC 0.000s
Banner return 2xx or 4xx code
The banner must return (2xx) a valid (4xx) or temporary code.
0.000s
Banner return server name
Banner must contain the name of the server
0.000s
SMTP server type is hidden
There is a risk to display the type and the version of the server, because people can find a breach for a specific version and use it
0.000s
Domain should have at least 2 SMTP servers according to the RFC. Note: You can use a service like altospam to solve this problem. Click on the link below to learn more
0.000s
MX IPs are in different class C
The class C of every IPs should be differents
0.000s
SPF record is no longer used, SPF must be into TXT record because many servers do not support SPF record. If SPF record exist, it should be the same as TXT
RFC 0.000s
Domain have only 1 SPF record
To avoid issue with SPF, it is strongly recommended to configure only one.
0.000s
According to the RFC, the SPF version must be specified.
RFC 0.000s
SPF version at first position
SPF has to start with version's tag.
RFC 0.000s
According to the RFC, the mecanism "all" must be specified in the SPF record, except if there is a Redirect tag.
RFC 0.000s
SPF "all" at last position
The mecanism "All" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.
RFC 0.000s
IPv4 & IPv6 syntaxes are corrects in SPF
IPs must be valid, otherwise the SPF will be useless.
RFC 0.000s
PTR has become obselete in SPF, should not be found in it.
RFC 0.000s
SPF "Redirect" at last position
The mecanism "Redirect" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.
RFC 0.000s
SPF records of type TXT & SPF are the same
SPF record has become obselete, if it is configured then it must be the same as the one present in the TXT record
0.000s
PTR must be just before All statement
The mecanism "PTR" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.
0.000s
Domain have only 1 DMARC record
To avoid issue with DMARC, it is strongly recommended to configure only one.
0.000s
According to the RFC 7489 section 6.3, the DMARC version is required.
RFC 0.000s
DMARC version at first position
According to the RFC 7489 section 6.3, the DMARC version must be the first tag in the list.
RFC 0.000s
According to the RFC 7489 section 6.3, the procedure is required.
RFC 0.000s
According to the RFC 7489 section 6.3, the procedure value must be none, quarantine or reject.
RFC 0.000s
DMARC "sp" field is valid
According to the RFC 7489 section 6.3, the subdomain procedure value must be none, quarantine or reject.
RFC 0.000s
DMARC "pct" field is valid
According to the RFC 7489 section 6.3, the percentage's value must be between 0 and 100.
RFC 0.000s
DMARC "adkim" field is valid
According to the RFC 7489 section 6.3, the adkim tag value must be the letter R or S.
RFC 0.000s
DMARC "aspf" field is valid
According to the RFC 7489 section 6.3, the aspf tag value must be the letter R or S.
RFC 0.000s
DMARC "rf" field is valid
According to the RFC 7489 section 6.3, the RF tag's value must be afrf or iodef.
RFC 0.000s
DMARC "ri" field is valid
According to the RFC 7489 section 6.3, the RI tag's value must be an integer.
RFC 0.000s
DMARC "ruf" field is valid
According to the RFC 7489 section 6.3, the RUF tag's value must be a valid email.
RFC 0.000s
DMARC "rua" field is valid
According to the RFC 7489 section 6.3, the RUA tag's value must be a valid email.
RFC 0.000s
According to the RFC 6376 section 3.6.1, the DKIM version is required.
RFC 0.000s
DKIM Service Type is valid
This Tag is optionnal but when use, it must be equal to "*" or "email".
RFC 0.000s
DKIM Testing flag is valid
This Tag is optionnal but when use, it must be equal to "s", "y" or "y:s".
RFC 0.000s
According to the RFC 6376 section 3.6.1, the public key is required and must be valid.
RFC 0.000s
DKIM public key is secure
The size of the public key must be bigger than 1024 bits.
0.000s