Analysis report on IP address: 193.0.9.6

193.0.9.6
Generated on
17 Apr 2021 17:57
Duration of the analysis
50.3s
Share

Score 93%
A
DNS
A
IP
A
MAIL
-
WEB
A

Resume

BIND version is hidden

Dns version is visible for ns3.lacnic.net with IP 200.3.13.14 : 9.16.15.

DNS

Dns servers for 193.in-addr.arpa

193.0.9.6 was detected as ipv4

Query informations

Server
k.root-servers.net
[ 193.0.14.129 ]
Duration
12 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
ns3.afrinic.net
[ 204.61.216.100 ]
Duration
2 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns3.lacnic.net
[ 200.3.13.14 ]
Duration
195 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

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

Query informations

Server
pri.authdns.ripe.net
[ 193.0.9.5 ]
Duration
11 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
rirns.arin.net
[ 199.253.249.53 ]
Duration
138 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

BIND version is hidden

Dns version is visible for ns3.lacnic.net with IP 200.3.13.14 : 9.16.15.

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

0.499s

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

All servers return success

Passed

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

0.003s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.003s

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

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

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

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
193.0.9.6
Type
ipv4
Reverse
ns.ripe.net
ARPA
6.9.0.193.in-addr.arpa
Class C
193.0.9.0/24
ASN
197000 Reseaux IP Europeens Network Coordination Centre (RIPE NCC)
Organisation
GII-RIPE
Maintainer
RIPE-GII-MNT

Reputation

Blacklists
Ip
Whois server
whois.ripe.net
Raw data
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '193.0.9.0 - 193.0.9.255'

% Abuse contact for '193.0.9.0 - 193.0.9.255' is O3V2iYd5 [at] ripe.net'

inetnum:        193.0.9.0 - 193.0.9.255
netname:        RIPE-NCC-AUTHDNS
descr:          RIPE NCC DNS anycast system
country:        NL
admin-c:        GII-RIPE
tech-c:         GII-RIPE
status:         ASSIGNED PA
mnt-by:         RIPE-GII-MNT
created:        2010-03-10T13:17:48Z
last-modified:  2016-09-12T11:39:00Z
source:         RIPE

% Information related to '193.0.9.0/24AS197000'

route:          193.0.9.0/24
descr:          Auth DNS Service Network
origin:         AS197000
mnt-by:         RIPE-GII-MNT
created:        2010-03-10T13:17:48Z
last-modified:  2012-04-25T12:02:20Z
source:         RIPE

% This query was served by the RIPE Database Query Service version 1.99 (WAGYU)


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

Mail

There is no mail server. Please test ns.ripe.net.

Name
ns.ripe.net
IP
193.0.9.6
Accessible
Autodiscover analysis not possible on an IP

Web

There is no web server. Please test ns.ripe.net.

Url
http://193.0.9.6/
Timeout
Yes
Url
https://193.0.9.6/
Timeout
Yes

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