Server 208.80.124.4 returns different MX records from 208.94.148.4: alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com
BIND version is hidden
Dns version is visible for ns10.dnsmadeeasy.com with IP 208.94.148.4 : 9.11.22.
SPF is configured for domain
The Domain does not have SPF.
DMARC is configured for domain
The Domain does not have DMARC.
Domain have "AAAA" field
Host has no "AAAA" (IPv6) field.
Cookies are secure
The HttpOnly flag was not found.
X-XSS-Protection header is present
The X-XSS-Protection header was not found.
Content Type Options header is present
The X-Content-Type-Options header was not found.
Banner return server name
aspmx.l.google.com with IP [64.233.184.27] does not contain the name of the server.
mx.google.com ESMTP r1si27806937wrv.217 - gsmtp
alt1.aspmx.l.google.com with IP [142.250.147.27] does not contain the name of the server.
mx.google.com ESMTP j14si20575830edw.465 - gsmtp
aspmx3.googlemail.com with IP [209.85.233.26] does not contain the name of the server.
mx.google.com ESMTP u11si25241125ljg.269 - gsmtp
aspmx2.googlemail.com with IP [142.250.147.26] does not contain the name of the server.
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
Same MX are returned
Server 208.80.124.4 returns different MX records from 208.94.148.4: alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com
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.033s
BIND version is hidden
Dns version is visible for ns10.dnsmadeeasy.com with IP 208.94.148.4 : 9.11.22.
The Bind version should not be visible otherwise it will be possible to search for potential security vulnerabilities of the version.
0.029s
Domain have at least 2 DNS servers
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.
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
SOA email is valid
Passed
An email address must respect some conditions to be valid, accordding to the RFC 5322.
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.030s
Transfer zone is disable
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.
Smtp servers that are listed in DNS area must be accessible, otherwise, there is a risk that emails may be lost
0.000s
MX IPs have reverse
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.
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 refused
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
VRFY command is refused
Passed
As the EXPN command, VRFY is used by spammers to verify an address.
0.000s
MX servers are not open relay
Passed
If a server is open relay, there is a risk that spammers use your server to send illegitimate mail.
0.740s
MX servers accept abuse@ address
Passed
According to the RFC 2142, SMTP server should accept abuse@yourDomain as a recipient.
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 differents
Passed
The IP of the SMTP servers must be different if it is no longer reachable.
0.000s
MX IPs are in different class C
Passed
The class C of every IPs should be differents
0.000s
SPF record is TXT type
Skipped
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
Copyright 2021 All rights reserved. Toronto Real Estate Board (TREB) assumes no responsibility for the accuracy of any information shown. The information provided herein must only be used by consumers that have a bona fide interest in the purchase, sale or lease of real estate and may not be used for any commercial purpose or any other purpose. Real Estate Webdesign by AgentLocator.
It is highly recommended to have an IPv6 for the website.
0.000s
Cookies are secure
The HttpOnly flag was not found.
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)
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.
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.
If you configure a WWW host for your website, it is recommended to have an IPv6.
0.000s
Content Security Policy header is present
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).
The domain must have an A field in order for the website to be accessible.
0.000s
Host "www" have "A" field
Passed
WWW host is not required for a website, but it's better to have one.
0.000s
HTTP port (80) is open
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
HTTPS port (443) is open
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
Web server version is hidden
Passed
To avoid giving details to malicious people, the version of the server should not be visible.
0.000s
Web application technology is hidden
Passed
To avoid giving details to malicious people, the technology that supports the application should not be visible.
