Analysis report on IP address: 200.128.56.117

200.128.56.117 has no website

Generated on
15 Jul 2021 08:59
Duration of the analysis
66.8s
Share

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

Congratulation

Your domain is really well configured

DNS

Dns servers for 56.128.200.in-addr.arpa

200.128.56.117 was detected as ipv4

There is no Dns server for this domain

Possible problem in Dns Tree

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

  • Not synchronised
  • Unknown error
  • Refuse to respond or is in timeout state.

Query informations

Server
e.root-servers.net
[ 192.203.230.10 ]
Duration
9 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

All the step don't return the same response.

Response

Query informations

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

All the step don't return the same response.

Response

Query informations

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

All the step don't return the same response.

Response

Query informations

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

.

Server refused to answer when edns query is performed.

Query informations

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

Response

Name
a.arpa.dns.br
IPs
  • No IP
Name
a.lactld.org
IPs
  • No IP
Name
lacnic.authdns.ripe.net
IPs
  • No IP
Name
ns-lacnic.nic.mx
IPs
  • No IP
Name
ns.lacnic.net
IPs
  • No IP
Name
ns2.lacnic.net
IPs
  • No IP
Name
ns3.afrinic.net
IPs
  • No IP
Name
ns4.apnic.net
IPs
  • No IP
Name
rirns.arin.net
IPs
  • No IP

Query informations

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

Response

Name
a.arpa.dns.br
IPs
  • No IP
Name
a.lactld.org
IPs
  • No IP
Name
lacnic.authdns.ripe.net
IPs
  • No IP
Name
ns-lacnic.nic.mx
IPs
  • No IP
Name
ns.lacnic.net
IPs
  • No IP
Name
ns2.lacnic.net
IPs
  • No IP
Name
ns3.afrinic.net
IPs
  • No IP
Name
ns4.apnic.net
IPs
  • No IP
Name
rirns.arin.net
IPs
  • No IP

Query informations

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

Response

Name
dns.ufba.br
IPs
  • No IP
Name
ns1.pop-ba.rnp.br
IPs
  • No IP
Name
ns2.pop-ba.rnp.br
IPs
  • No IP

Query informations

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

Response

Name
dns.ufba.br
IPs
  • No IP
Name
ns1.pop-ba.rnp.br
IPs
  • No IP
Name
ns2.pop-ba.rnp.br
IPs
  • No IP

Query informations

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

Response

Name
dns.ufba.br
IPs
  • No IP
Name
ns1.pop-ba.rnp.br
IPs
  • No IP
Name
ns2.pop-ba.rnp.br
IPs
  • No IP

Query informations

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

Response

Name
dns.ufba.br
IPs
  • No IP
Name
ns1.pop-ba.rnp.br
IPs
  • No IP
Name
ns2.pop-ba.rnp.br
IPs
  • No IP

Query informations

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

Response

Name
dns.ufba.br
IPs
  • No IP
Name
ns1.pop-ba.rnp.br
IPs
  • No IP
Name
ns2.pop-ba.rnp.br
IPs
  • No IP

Query informations

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

Response

Name
dns.ufba.br
IPs
  • No IP
Name
ns1.pop-ba.rnp.br
IPs
  • No IP
Name
ns2.pop-ba.rnp.br
IPs
  • No IP

Query informations

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

Response

Name
dns.ufba.br
IPs
  • No IP
Name
ns1.pop-ba.rnp.br
IPs
  • No IP
Name
ns2.pop-ba.rnp.br
IPs
  • No IP

Query informations

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

Response

Name
dns.ufba.br
IPs
  • No IP
Name
ns1.pop-ba.rnp.br
IPs
  • No IP
Name
ns2.pop-ba.rnp.br
IPs
  • No IP

Query informations

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

Response

Name
dns.ufba.br
IPs
  • No IP
Name
ns1.pop-ba.rnp.br
IPs
  • No IP
Name
ns2.pop-ba.rnp.br
IPs
  • No IP
DNSSEC analysis not possible on an IP

Ip

Informations

Ip
200.128.56.117
Type
ipv4
Reverse
smtp3.ufba.br
ARPA
117.56.128.200.in-addr.arpa
Class C
200.128.56.0/24
ASN
53164 UNIVERSIDADE FEDERAL DA BAHIA
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-07-15T06:00:52-03:00 - IP: 195.154.82.101

inetnum:     200.128.0.0/17
aut-num:     AS53164
abuse-c:     ABPOP
owner:       UNIVERSIDADE FEDERAL DA BAHIA
ownerid:     15.180.714/0001-04
responsible: Joao Carlos Salles Pires da Silva
owner-c:     LCM12
tech-c:      REPOP5
inetrev:     200.128.56.0/21
nserver:     dns.ufba.br
nsstat:      20210713 AA
nslastaa:    20210713
nserver:     ns1.pop-ba.rnp.br
nsstat:      20210713 AA
nslastaa:    20210713
nserver:     ns2.pop-ba.rnp.br
nsstat:      20210713 AA
nslastaa:    20210713
created:     20000215
changed:     20200218

nic-hdl-br:  LCM12
person:      Luiz Claudio de Araujo Mendonca
created:     19980304
changed:     20180418

nic-hdl-br:  ABPOP
person:      Abuse PoPBA
created:     20200218
changed:     20200218

nic-hdl-br:  REPOP5
person:      Registro PoPBA
created:     20200218
changed:     20200218

% 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

Passed

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 smtp3.ufba.br.

Name
smtp3.ufba.br
IP
200.128.56.117
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 smtp3.ufba.br.

Url
http://200.128.56.117/
Timeout
Yes
Url
https://200.128.56.117/
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