Analysis report on IP address: 200.3.13.14

200.3.13.14 has no website

Generated on
19 Sep 2021 07:47
Duration of the analysis
68.8s
Share

Score 86%
C
DNS
C
IP
A
MAIL
A
WEB
A

Resume

DNS servers IP are in different class C

IPs have the same C class.

BIND version is hidden

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

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

DNS servers IP are differents

Ip for hosts ns.lacnic.net and dns.anycast.lacnic.net are same.

DNS

Dns servers for 13.3.200.in-addr.arpa

200.3.13.14 was detected as ipv4

Query informations

Server
l.root-servers.net
[ 199.7.83.42 ]
Duration
50 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
a.in-addr-servers.arpa
[ 199.180.182.53 ]
Duration
259 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
b.in-addr-servers.arpa
[ 199.253.183.183 ]
Duration
37 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
c.in-addr-servers.arpa
[ 196.216.169.10 ]
Duration
182 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
d.in-addr-servers.arpa
[ 200.10.60.53 ]
Duration
108 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
e.in-addr-servers.arpa
[ 203.119.86.101 ]
Duration
657 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
f.in-addr-servers.arpa
[ 193.0.9.1 ]
Duration
18 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
a.arpa.dns.br
[ 200.160.11.50 ]
Duration
2605 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
a.lactld.org
[ 200.0.68.10 ]
Duration
18 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
lacnic.authdns.ripe.net
[ 193.0.9.11 ]
Duration
13 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns-lacnic.nic.mx
[ 200.33.111.2 ]
Duration
139 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Query informations

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

Query informations

Server
ns3.afrinic.net
[ 204.61.216.100 ]
Duration
3 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns4.apnic.net
[ 202.12.31.53 ]
Duration
146 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
rirns.arin.net
[ 199.253.249.53 ]
Duration
141 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
dns.anycast.lacnic.net
[ 200.3.13.10 ]
Duration
194 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

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

Query informations

Server
ns2.lacnic.net
[ 200.3.13.11 ]
Duration
186 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

DNS servers IP are in different class C

IPs have the same C class.

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

BIND version is hidden

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

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

DNS servers IP are differents

Ip for hosts ns.lacnic.net and dns.anycast.lacnic.net are same.

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

0.000s

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

All servers return success

Passed

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

0.005s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.006s

SOA are synchronized

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

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

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

1.383s

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

DNS servers IP are not private

Passed

It is strictly forbidden to have private IP in DNS

documentation

0.000s

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

Ip

Informations

Ip
200.3.13.14
Type
ipv4
Reverse
ns3.lacnic.net
ARPA
14.13.3.200.in-addr.arpa
Class C
200.3.13.0/24
ASN
28001 Latin American and Caribbean IP address
Organisation
 
Maintainer
 

Reputation

Blacklists
Ip
Whois server
whois.lacnic.net
Raw data
% Joint Whois - whois.lacnic.net
%  This server accepts single ASN, IPv4 or IPv6 queries

% LACNIC resource: whois.lacnic.net


% Copyright LACNIC lacnic.net
%  The data below is provided for information purposes
%  and to assist persons in obtaining information about or
%  related to AS and IP numbers registrations
%  By submitting a whois query, you agree to use this data
%  only for lawful purposes.
%  2021-09-24 16:38:12 (-03 -03:00)

inetnum:     200.3.12.0/22
status:      assigned
aut-num:     N/A
owner:       LACNIC - Latin American and Caribbean IP address
ownerid:     UY-LACN-LACNIC
responsible: Ernesto Majó
address:     Rambla República de México, 6125, Esquina 6 de Abril
address:     11400 - Montevideo - 
country:     UY
phone:       +598  26042222 [0000]
owner-c:     AIL
tech-c:      AIL
abuse-c:     AIL
inetrev:     200.3.12.0/22
nserver:     NS.LACNIC.NET
nsstat:      20210924 AA
nslastaa:    20210924
nserver:     NS2.LACNIC.NET
nsstat:      20210924 AA
nslastaa:    20210924
nserver:     DNS.ANYCAST.LACNIC.NET
nsstat:      20210924 AA
nslastaa:    20210924
created:     20080902
changed:     20080902

nic-hdl:     AIL
person:      Carlos M Martínez
e-mail:      fYR1eIF9gg== [at] lacnic.net
address:     Rambla Rep. Mexico, 6125, Casa de Internet
address:     11400 - Montevideo - Montevideo
country:     UY
phone:       +598  26042222 [4401]
created:     20080125
changed:     20210901

% whois.lacnic.net accepts only direct match queries.
% Types of queries are: POCs, ownerid, CIDR blocks, IP
% and AS numbers.

Blacklists

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

Ip is not blacklisted

SpamHaus has blacklisted your domain/IP.

An ip must not be blacklisted or it will be penalized for referencing and deliverability of emails.

0.004s

Mail

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

Name
ns3.lacnic.net
IP
200.3.13.14
Accessible
Autodiscover analysis not possible on an IP

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 ns3.lacnic.net.

Url
http://200.3.13.14/
Timeout
Yes
Url
https://200.3.13.14/
Reachable
No

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