Analysis report on domain: ns3.lacnic.net favicon

ns3.lacnic.net has no website

Generated on
22 Sep 2021 15:15
Duration of the analysis
86.4s
Share

Score 91%
B
DNS
B
DOMAIN
A
MAIL
A
WEB
A

Resume

SOA are synchronized

SOA of servers from SList aren't the same.

BIND version is hidden

Dns version is visible for a.lactld.org with IP 200.0.68.10 : NSD 4.3.2.

Dns version is visible for ns.lacnic.net with IP 200.3.13.10 : 9.11.31.

Dns version is visible for ns2.dns.br with IP 200.192.232.53 : 9.16.15.

Dns version is visible for ns2.lacnic.net with IP 200.3.13.11 : 9.11.31.

DNS

Dns servers for lacnic.net

ns3.lacnic.net was detected as host

Host informations

Ips
 
Cname
-

Query informations

Server
m.root-servers.net
[ 202.12.27.33 ]
Duration
10 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
a.gtld-servers.net
[ 192.5.6.30 ]
Duration
1133 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
b.gtld-servers.net
[ 192.33.14.30 ]
Duration
9 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
c.gtld-servers.net
[ 192.26.92.30 ]
Duration
10 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
d.gtld-servers.net
[ 192.31.80.30 ]
Duration
10 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
e.gtld-servers.net
[ 192.12.94.30 ]
Duration
10 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
f.gtld-servers.net
[ 192.35.51.30 ]
Duration
34 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
g.gtld-servers.net
[ 192.42.93.30 ]
Duration
32 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
h.gtld-servers.net
[ 192.54.112.30 ]
Duration
32 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
i.gtld-servers.net
[ 192.43.172.30 ]
Duration
33 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
j.gtld-servers.net
[ 192.48.79.30 ]
Duration
32 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
k.gtld-servers.net
[ 192.52.178.30 ]
Duration
31 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
l.gtld-servers.net
[ 192.41.162.30 ]
Duration
32 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
m.gtld-servers.net
[ 192.55.83.30 ]
Duration
32 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
a.lactld.org
[ 200.0.68.10 ]
Duration
17 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
lacnic.authdns.ripe.net
[ 193.0.9.11 ]
Duration
15 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns.lacnic.net
[ 200.3.13.10 ]
Duration
196 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns2.dns.br
[ 200.192.232.53 ]
Duration
202 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns2.lacnic.net
[ 200.3.13.11 ]
Duration
198 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns4.apnic.net
[ 202.12.31.53 ]
Duration
147 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
rirns.arin.net
[ 199.253.249.53 ]
Duration
144 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Name servers

A and AAAA fields

IPv4
200.3.13.14
TTL
7200 (2 hours )
IPv6
2001:13c7:7002:3000:0:0:0:14
TTL
7200 (2 hours )

SOA

From
lacnic.authdns.ripe.net
Master server
ns.lacnic.net
TTL
600 (10 minutes)
Contact
fIOHiIF1h4h5hg==@lacnic.net
Serial
2021081951
Refresh
7200 (2 hours)
Retry
3600 (1 hour)
Expire
648736 (1 week)
Minimum
600 (10 minutes)
From
rirns.arin.net
Master server
NS.LACNIC.NET
TTL
600 (10 minutes)
Contact
fIOHiIF1h4h5hg==@lacnic.net
Serial
2021081951
Refresh
7200 (2 hours)
Retry
3600 (1 hour)
Expire
648736 (1 week)
Minimum
600 (10 minutes)

RRSIG

Numbers of Labels
2
Created
23 Sep 2021 11:10
Expire
23 Oct 2021 12:10
Algorithme
8 (RSA/SHA-256)
Orig TTL
7200 (2 hours)
TTL
600 (10 minutes)
signature Name
lacnic.net
signature
JZGeWxg4A7i2jR3kRLF5OF1/uXzvi5jOMXWZrdr+oKz+2UNYJq3Jau8jPiV6gF4+TEoIetzwlVC5uugQ1HMyWnHbip9sFVD919fGLCshaK3SlNu+Uj90ZLRS7vh9tlaDWsk163Xm7WTUkUCLHRO5b5uFFTrkQVWsFAd8tydy3P4QyHUwonETDhIaZ+AjNNyHruzkVOLmDTqTC8zSpteWExkNU0MTXmM7u681I509RBVBKf/P6XUO7htwK6Z9+GQu7KjswJD7Vs2mXbbqGdn6+X6tGky2gtO1KFAk7F96s8Y5pjNg5kdg48s5mTzfCnCh5bTKeH5aO0B9bwG6VjPM4Q==

SOA are synchronized

SOA of servers from SList aren't the same.

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

BIND version is hidden

Dns version is visible for a.lactld.org with IP 200.0.68.10 : NSD 4.3.2.

Dns version is visible for ns.lacnic.net with IP 200.3.13.10 : 9.11.31.

Dns version is visible for ns2.dns.br with IP 200.192.232.53 : 9.16.15.

Dns version is visible for ns2.lacnic.net with IP 200.3.13.11 : 9.11.31.

The Bind version should not be visible otherwise it will be possible to search for potential security vulnerabilities of the version.

0.913s

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.

RFC

0.000s

All Dns servers are responding

Passed

Every DNS servers should be accessible and accept public query.

0.029s

All servers return success

Passed

It's important that all servers returned a "success" code.

0.017s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.010s

DNS servers IP are differents

Passed

IPs for DNS servers must be different in order to have high availability.

0.000s

DNS servers IP are in different class C

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.

RFC

0.000s

SOA email is valid

Passed

An email address must respect some conditions to be valid, accordding to the RFC 5322.

RFC

0.000s

SOA refresh is valid

Passed

The refresh value be must between 1200 and 43200.

RFC

0.000s

SOA retry, refresh and expire values are correct

Passed

The Retry, Refresh and Expire values musth follow this path : retry < refresh < expire.

RFC

0.000s

DNS servers are not open relay

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.922s

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.

documentation

3.049s

Recursive query is disable

Passed

Having a dns server that allow recursive queries is a security risk, DDOS attack can be performed.

RFC documentation documentation

0.908s

DNS servers IP are not private

Passed

It is strictly forbidden to have private IP in DNS

documentation

0.000s

Same MX are returned

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.908s

DNS servers are synchronized

Skipped

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

Domain

Whois

Registrar
GoDaddy.com, LLC
Owner
-
Created at
02 Sep 1999
Changed at
26 Jan 2021
Expires at
02 Sep 2022

Reputation

Google Safe Browsing
Web of trust
Blacklists
Virus Total
Domain
Whois server
whois.godaddy.com
Created at
02 Sep 1999
Changed at
26 Jan 2021
Expires at
02 Sep 2022
Name servers
Registrar
Id
146
Name
GoDaddy.com, LLC
Phone
+1.4806242505
Email
dXaJh3k=@godaddy.com
Url
http://www.godaddy.com
Owner
Name
-
Organization
Registro Regional de Direccion IP Latinoamericano y Caribeno
Address
-
City
-
Zip code
-
Country
UY
Phone
-
Email

Google Safe Browsing

Status

Web of Trust

Status

Blacklists

RFC Ignorant
Rbl Jp
RblDns
Sorbs
Spam Eating Monkey
SpamHaus
SuRbl
Support Intelligence
Swinog
UriBl

Virus Total

Detection ratio
/

Scans

DNS servers are same in dns tree and whois

Passed

The dns servers given in the domain whois must be the same as those returned by a dns resolution request.

0.000s

Domain is not blacklisted

Passed

A domain must not be blacklisted or it will be penalized for referencing and deliverability of emails.

0.000s

Domain is not listed in Google Safe Browsing

Passed

Google safe browsing categorizes a domain as bad if something suspicious is detected.

0.000s

Domain is not listed in VirusTotal

Passed

Virus Total analyze your domain or IP address with 66 antivirus.

0.000s

Domain have good reputation on Web of Trust

Passed

Web Of Trust rates thousands of websites and find threats if they exist.

0.000s

Mail

There is no mail server. Please test lacnic.net.

Name
ns3.lacnic.net
IP
200.3.13.14
Accessible

Autodiscover not configured

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.

documentation

0.000s

MX servers are accessibles

Skipped

Smtp servers that are listed in DNS area must be accessible, otherwise, there is a risk that emails may be lost

0.000s

HELO command is accepted

Skipped

According to the RFC 2181, smtp server should accept HELO command

RFC

0.000s

EHLO command is accepted

Skipped

According to the RFC 2181, smtp server should accept EHLO command

RFC

0.000s

STARTTLS command is accepted

Skipped

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

Skipped

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

Skipped

As the EXPN command, VRFY is used by spammers to verify an address.

0.000s

MX servers are not open relay

Skipped

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

Skipped

According to the RFC 2142, SMTP server should accept abuse@yourDomain as a recipient.

RFC

0.000s

MX servers accept postmaster@ address

Skipped

According to the RFC 5321, SMTP server should accept postmaster@yourDomain as a recipient.

RFC

0.000s

Banner return 2xx or 4xx code

Skipped

The banner must return (2xx) a valid (4xx) or temporary code.

0.000s

Banner return server name

Skipped

Banner must contain the name of the server

0.000s

SMTP server type is hidden

Skipped

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

Web

There is no web server. Please test lacnic.net.

Url
http://ns3.lacnic.net/
Timeout
Yes
Url
https://ns3.lacnic.net/
Timeout
Yes

Domain have "A" field

Skipped

The domain must have an A field in order for the website to be accessible.

0.000s

Host "www" have "A" field

Skipped

WWW host is not required for a website, but it's better to have one.

0.000s

Domain have "AAAA" field

Skipped

It is highly recommended to have an IPv6 for the website.

0.000s

Host "www" have "AAAA" field

Skipped

If you configure a WWW host for your website, it is recommended to have an IPv6.

0.000s

HTTP port (80) is open

Skipped

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

Skipped

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

Skipped

To avoid giving details to malicious people, the version of the server should not be visible.

0.000s

Web application technology is hidden

Skipped

To avoid giving details to malicious people, the technology that supports the application should not be visible.

0.000s

Cookies are secure

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)

RFC

0.000s

X-XSS-Protection header is present

Skipped

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.

documentation

0.000s

Content Security Policy header is present

Skipped

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).

documentation

0.000s

Content Type Options header is present

Skipped

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.

0.000s