Dns version is visible for ns1.maxxsoft.nl with IP 89.207.128.251 : PowerDNS Authoritative Server 4.9.0 (built Mar 15 2024 09:19:57 by root@localhost).
Dns version is visible for ns2.maxxsoft.nl with IP 89.207.130.251 : PowerDNS Authoritative Server 4.9.0 (built Mar 15 2024 09:19:57 by root@localhost).
A PTR was found in SPF.
v=spf1 a mx ptr ip4:185.62.58.176 include:spf.protection.outlook.com include:_spf.smtprelay.snel.com include:_spf.exactonline.nl ~all
v=spf1 a mx ptr ip4:185.62.58.176 include:spf.protection.outlook.com include:_spf.smtprelay.snel.com include:_spf.exactonline.nl ~all
Version 2 has been found.
The X-XSS-Protection header was not found.
The X-Content-Type-Options header was not found.
sau-nl.mail.protection.outlook.com with IP [52.101.73.8] does not contain the name of the server.
1
sau-nl.mail.protection.outlook.com with IP [52.101.68.29] does not contain the name of the server.
1
sau-nl.mail.protection.outlook.com with IP [52.101.73.22] does not contain the name of the server.
1
sau-nl.mail.protection.outlook.com with IP [52.101.68.32] does not contain the name of the server.
1
sau-nl.mail.protection.outlook.com with IP [52.101.73.30] does not contain the name of the server.
1
sau-nl.mail.protection.outlook.com with IP [52.101.73.28] does not contain the name of the server.
1
sau-nl.mail.protection.outlook.com with IP [52.101.68.0] does not contain the name of the server.
1
The Content-Security-Policy header was not found.
sau-amsterdam.fr was detected as domain
-----BEGIN PUBLIC KEY----- MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCxZgyyUQZpWEZ8r3VaT+iXf9ob wfEga5MauXnd6U7FbvqOLSLZ8kEwkC/pZ19QX+3I32JAsabadNnzDs4ot23Z8uaH zpkUh41DNMJ3MXnQkNk5+YYKTPDzhjM69vnHyrjXx6LUp4PhmADRNPlFYfQbf9Z0 aIh2guO0ff0n0sI18wIDAQAB -----END PUBLIC KEY-----
Dns version is visible for ns1.maxxsoft.nl with IP 89.207.128.251 : PowerDNS Authoritative Server 4.9.0 (built Mar 15 2024 09:19:57 by root@localhost).
Dns version is visible for ns2.maxxsoft.nl with IP 89.207.130.251 : PowerDNS Authoritative Server 4.9.0 (built Mar 15 2024 09:19:57 by root@localhost).
The Bind version should not be visible otherwise it will be possible to search for potential security vulnerabilities of the version.
0.034s
Passed
In order for the availability rate of DNS servers to be at its highest, it is vital and recommended by the RFC to have at least 2 servers.
RFC0.000s
Passed
Every DNS servers should be accessible and accept public query.
0.003s
Passed
It's important that all servers returned a "success" code.
0.002s
Passed
Passed
IPs for DNS servers must be different in order to have high availability.
0.000s
Passed
The class C of each IP must be different so that the servers are not found on the same bay and therefore there is a risk of unavailability.
RFC0.000s
Passed
The synchronization of the DNS servers must be perfect in order to avoid any dns resolution error. The servers must therefore give the same answer when asked "what are the DNS servers for the domain?".
0.000s
Passed
The SOA answered by the DNS servers must be identical for each servers. The most important information is the master server and the contact email address.
0.000s
Passed
Passed
Passed
Passed
DNS resolvers that allow queries from all IP addresses and are exposed to the Internet can be attacked and used to conduct Denial of Service (DoS) attacks on behalf of the hacker.
0.035s
Passed
An attacker can use a zone transfer that contains a malicious code or an inappropriate format that crashes a DNS server vulnerable to this type of attack, which results in a DoS that destabilizes the DNS services. It is possible to test it manually with this commands: #host -T axfr or #dig axfr.
documentation0.102s
Passed
Having a dns server that allow recursive queries is a security risk, DDOS attack can be performed.
RFC documentation documentation0.034s
Passed
Passed
It is extremely important that each DNS return the same MX records in order to avoid contacting an SMTP server that no longer exists.
0.065s
Passed
A domain must not be blacklisted or it will be penalized for referencing and deliverability of emails.
0.000s
Passed
Google safe browsing categorizes a domain as bad if something suspicious is detected.
0.000s
Passed
Virus Total analyze your domain or IP address with 66 antivirus.
0.000s
Passed
Web Of Trust rates thousands of websites and find threats if they exist.
0.000s
Skipped
The dns servers given in the domain whois must be the same as those returned by a dns resolution request.
0.000s
Find more informations about this SPF entry into the DNS > Zone tab
Find more informations about DKIM entries into the DNS > Zone tab
Have you other DKIM selector to analyse ?
Find more informations about this DMARC entry into the DNS > Zone tab
Autodiscover not configured
A PTR was found in SPF.
v=spf1 a mx ptr ip4:185.62.58.176 include:spf.protection.outlook.com include:_spf.smtprelay.snel.com include:_spf.exactonline.nl ~all
v=spf1 a mx ptr ip4:185.62.58.176 include:spf.protection.outlook.com include:_spf.smtprelay.snel.com include:_spf.exactonline.nl ~all
The mecanism "PTR" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.
SPF definition0.000s
sau-nl.mail.protection.outlook.com with IP [52.101.73.8] does not contain the name of the server.
1
sau-nl.mail.protection.outlook.com with IP [52.101.68.29] does not contain the name of the server.
1
sau-nl.mail.protection.outlook.com with IP [52.101.73.22] does not contain the name of the server.
1
sau-nl.mail.protection.outlook.com with IP [52.101.68.32] does not contain the name of the server.
1
sau-nl.mail.protection.outlook.com with IP [52.101.73.30] does not contain the name of the server.
1
sau-nl.mail.protection.outlook.com with IP [52.101.73.28] does not contain the name of the server.
1
sau-nl.mail.protection.outlook.com with IP [52.101.68.0] does not contain the name of the server.
1
Banner must contain the name of the server
0.001s
Passed
Smtp servers that are listed in DNS area must be accessible, otherwise, there is a risk that emails may be lost
0.000s
Passed
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.
documentation0.000s
Passed
Passed
Passed
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
Passed
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
Passed
As the EXPN command, VRFY is used by spammers to verify an address.
0.000s
Passed
The banner must return (2xx) a valid (4xx) or temporary code.
0.000s
Passed
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
Passed
Passed
Passed
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
Passed
The IP of the SMTP servers must be different if it is no longer reachable.
0.000s
Passed
The class C of every IPs should be differents
0.000s
Passed
To avoid identity theft, it is strongly recommended to configure SPF.
0.000s
Passed
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
RFC0.000s
Passed
To avoid issue with SPF, it is strongly recommended to configure only one.
0.000s
Passed
Passed
Passed
According to the RFC, the mecanism "all" must be specified in the SPF record, except if there is a Redirect tag.
RFC0.000s
Passed
The mecanism "All" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.
RFC0.000s
Passed
Passed
The mecanism "Redirect" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.
RFC0.000s
Passed
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
Passed
To avoid identity theft, it is strongly recommended to configure DMARC.
0.000s
Passed
To avoid issue with DMARC, it is strongly recommended to configure only one.
0.000s
Passed
Passed
According to the RFC 7489 section 6.3, the DMARC version must be the first tag in the list.
RFC0.000s
Passed
Passed
According to the RFC 7489 section 6.3, the procedure value must be none, quarantine or reject.
RFC0.000s
Passed
According to the RFC 7489 section 6.3, the subdomain procedure value must be none, quarantine or reject.
RFC0.000s
Passed
Passed
Passed
Passed
Passed
Passed
Passed
Configured selector(s)
selector1
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
0.000s
Passed
Passed
Passed
Passed
Passed
The size of the public key must be bigger than 1024 bits.
0.000s
SAU (Strijbosch Acrylics Unlimited) SAU is a full service provider of various products and services tailored for the financial and investment business, corporate sector, promotional industry, and design environment.We invite you to request a fee quote for your project by clicking on the orange button located at the top. In case you need inspiration, we invite your to review some of our products here. SAU is a full service provider of various products and services tailored for the financial and investment business, corporate sector, promotional industry, and design environment.We invite you to request a fee quote for your project by clicking on the orange button located at the top. In case...
Version 2 has been found.
To avoid giving details to malicious people, the version of the server should not be visible.
0.000s
The X-XSS-Protection header was not found.
The HTTP X-XSS-Protection response header is a feature of Internet Explorer, Chrome and Safari that stops pages from loading when they detect reflected cross-site scripting (XSS) attacks.
documentation0.000s
The X-Content-Type-Options header was not found.
The only defined value, "nosniff", prevents Internet Explorer from MIME-sniffing a response away from the declared content-type. This also applies to Google Chrome, when downloading extensions.
RFC0.000s
The Content-Security-Policy header was not found.
The HTTP Content-Security-Policy response header allows web site administrators to control resources the user agent is allowed to load for a given page. With a few exceptions, policies mostly involve specifying server origins and script endpoints. This helps guard against cross-site scripting attacks (XSS).
documentation0.000s
Passed
The domain must have an A field in order for the website to be accessible.
0.000s
Passed
WWW host is not required for a website, but it's better to have one.
0.000s
Passed
It is highly recommended to have an IPv6 for the website.
0.000s
Passed
If you configure a WWW host for your website, it is recommended to have an IPv6.
0.000s
Passed
This test verifies the presence of a website for the given IP or domain. Then scans port 80.
If the domain or IP is pointing to a website then port 80 must be open so that it can be accessed from a browser.
Otherwise port 80 must be closed.
0.000s
Passed
This test verifies the presence of a website for the given IP or domain. Then scans port 443.
If the domain or IP is pointing to a website then port 443 must be open so that it can be accessed from a browser.
Otherwise port 443 must be closed.
0.000s
Passed
To avoid giving details to malicious people, the technology that supports the application should not be visible.
0.000s
Skipped
Using "HttpOnly" instruction prevents someone to access to cookies via Javascript. The secure flag will allow you to prevent a cookie from ever being communicated in simple HTTP. (RFC 6265 section 8.3)
RFC0.000s