Analysis report on IP address: 191.6.210.94

191.6.210.94 has no website

Generated on
13 Oct 2021 23:20
Duration of the analysis
58.0s
Share

Score 90%
B
DNS
-
IP
A
MAIL
A
WEB
B

Resume

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.

Content Security Policy header is present

The Content-Security-Policy header was not found.

DNS

Dns servers for 210.6.191.in-addr.arpa

191.6.210.94 was detected as ipv4

Possible problem in Dns Tree

We have detected the following error on one or more server(s).
Consult Tree for more details.

  • Refuse to respond or is in timeout state.

Query informations

Server
b.root-servers.net
[ 199.9.14.201 ]
Duration
241 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
c.in-addr-servers.arpa
[ 196.216.169.10 ]
Duration
5008 ms
Type
timeout
Headers
RCODE : - AA : - TC : -

Server timeout

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
262 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

Server
a.arpa.dns.br
[ 200.160.11.50 ]
Duration
602 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
12 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
ns2.lacnic.net
[ 200.3.13.11 ]
Duration
196 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

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
185 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

Server
dnsr1.hospedagem.net
[ 189.38.85.4 ]
Duration
208 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
dnsr2.hospedagem.net
[ 189.38.95.4 ]
Duration
199 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

Ip

Informations

Ip
191.6.210.94
Type
ipv4
Reverse
web260.uni5.net
ARPA
94.210.6.191.in-addr.arpa
Class C
191.6.210.0/24
ASN
28299 IPV6 Internet Ltda
Organisation
 
Maintainer
 

Reputation

Blacklists
Ip
Whois server
whois.lacnic.net
Raw data
% Copyright (c) Nic.br
%  The use of the data below is only permitted as described in
%  full by the terms of use at https://registro.br/termo/en.html ,
%  being prohibited its distribution, commercialization or
%  reproduction, in particular, to use it for advertising or
%  any similar purpose.
%  2021-10-13T20:21:23-03:00 - IP: 195.154.82.101

inetnum:     191.6.192.0/19
aut-num:     AS28299
abuse-c:     COABU
owner:       IPV6 Internet Ltda
ownerid:     13.793.593/0001-32
responsible: Administrador de Contratos
owner-c:     COABU
tech-c:      NOKIN4
inetrev:     191.6.210.0/24
nserver:     dnsr1.hospedagem.net
nsstat:      20211012 AA
nslastaa:    20211012
nserver:     dnsr2.hospedagem.net
nsstat:      20211012 AA
nslastaa:    20211012
created:     20140207
changed:     20190206

nic-hdl-br:  COABU
person:      Contato de Abuse
created:     20080919
changed:     20180417

nic-hdl-br:  NOKIN4
person:      NOC Kinghost
created:     20180814
changed:     20190606

% Security and mail abuse issues should also be addressed to
% cert.br, http://www.cert.br/ , respectivelly to d3mGiA== [at] cert.br
% and gXV9gEF1domHeQ== [at] cert.br
%
% whois.registro.br accepts only direct match queries. Types
% of queries are: domain (.br), registrant (tax ID), ticket,
% provider, CIDR block, IP and ASN.

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

Mail

There is no mail server. Please test web260.uni5.net.

Name
web260.uni5.net
IP
191.6.210.94
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

Website

Url
https://191.6.210.94/
Https
Title
Web260
Description
Unknown
First paragraph
Unknown
Url
http://191.6.210.94/
Title
Web260
Description
Unknown
Response time
0.399 second
Server
apache
Powered by
Unknown
Encoding
utf-8
HSTS

Headers

  • Connection: close
  • Content-Type: text/html; charset=UTF-8
  • Date: Wed, 13 Oct 2021 23:21:20 GMT
  • Layer1: Cache
  • Server: Apache
  • Transfer-Encoding: chunked
Url
https://191.6.210.94/
Title
Web260
Description
Unknown
Response time
0.806 second
Server
apache
Powered by
Unknown
Encoding
utf-8
HSTS

Headers

  • Connection: close
  • Content-Type: text/html; charset=UTF-8
  • Date: Wed, 13 Oct 2021 23:21:21 GMT
  • Layer1: Cache
  • Server: Apache
  • Transfer-Encoding: chunked

X-XSS-Protection header is present

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.

documentation

0.000s

Content Type Options header is present

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.

RFC

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

documentation

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.

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