Analysis report on IP address: 138.117.216.29

138.117.216.29
Generated on
08 Apr 2021 07:17
Duration of the analysis
85.1s
Share

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

Resume

SMTP server type is hidden

wh1.eivus.com with IP [138.117.216.29] displays the type of SMTP, exim founded

220-wh1.eivus.com ESMTP Exim 4.94 #2 Thu, 08 Apr 2021 04:18:01 -0300
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.

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 216.117.138.in-addr.arpa

138.117.216.29 was detected as ipv4

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
c.in-addr-servers.arpa
[ 196.216.169.10 ]
Duration
190 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
253 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

Server
arin.authdns.ripe.net
[ 193.0.9.10 ]
Duration
409 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
r.arin.net
[ 199.180.180.63 ]
Duration
144 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
u.arin.net
[ 204.61.216.50 ]
Duration
8 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
x.arin.net
[ 199.180.180.63 ]
Duration
145 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
y.arin.net
[ 192.82.134.30 ]
Duration
25 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
z.arin.net
[ 199.212.0.63 ]
Duration
86 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
a.dns.eivus.com
[ 138.117.216.18 ]
Duration
197 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
b.dns.eivus.com
[ 138.117.216.19 ]
Duration
198 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

Ip

Informations

Ip
138.117.216.29
Type
ipv4
Reverse
wh1.eivus.com
ARPA
29.216.117.138.in-addr.arpa
Class C
138.117.216.0/24
ASN
264254 EIVUS DATA CENTER E TELECOM
Organisation
 
Maintainer
 

Reputation

Blacklists
Ip
Whois server
Raw data
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2021, American Registry for Internet Numbers, Ltd.
#


NetRange:       138.117.0.0 - 138.117.255.255
CIDR:           138.117.0.0/16
NetName:        LACNIC-ERX-138-117-0-0
NetHandle:      NET-138-117-0-0-1
Parent:         NET138 (NET-138-0-0-0-0)
NetType:        Transferred to LACNIC
OriginAS:       
Organization:   Latin American and Caribbean IP address Regional Registry (LACNIC)
RegDate:        2010-11-19
Updated:        2010-11-19
Comment:        This IP address range is under LACNIC responsibility
Comment:        for further allocations to users in LACNIC region.
Comment:        Please see http://www.lacnic.net/ for further details,
Comment:        or check the WHOIS server located at http://whois.lacnic.net
Ref:            https://rdap.arin.net/registry/ip/138.117.0.0

ResourceLink:  http://lacnic.net/cgi-bin/lacnic/whois
ResourceLink:  whois.lacnic.net


OrgName:        Latin American and Caribbean IP address Regional Registry
OrgId:          LACNIC
Address:        Rambla Republica de Mexico 6125
City:           Montevideo
StateProv:      
PostalCode:     11400
Country:        UY
RegDate:        2002-07-27
Updated:        2018-03-15
Ref:            https://rdap.arin.net/registry/entity/LACNIC

ReferralServer:  whois://whois.lacnic.net
ResourceLink:  http://lacnic.net/cgi-bin/lacnic/whois

OrgTechHandle: LACNIC-ARIN
OrgTechName:   LACNIC Whois Info
OrgTechPhone:  +598-2604-2222 
OrgTechEmail:  i3yDfYdBd4OCiHV3iA== [at] lacnic.net
OrgTechRef:    https://rdap.arin.net/registry/entity/LACNIC-ARIN

OrgAbuseHandle: LWI100-ARIN
OrgAbuseName:   LACNIC Whois Info
OrgAbusePhone:  +598-2604-2222 
OrgAbuseEmail:  dXaJh3k= [at] lacnic.net
OrgAbuseRef:    https://rdap.arin.net/registry/entity/LWI100-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2021, American Registry for Internet Numbers, Ltd.
#

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

Mail

Mail servers

Name
wh1.eivus.com
IP
138.117.216.29
Banner
220-wh1.eivus.com ESMTP Exim 4.94 #2 Thu, 08 Apr 2021 04:18:01 -0300 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.
Name
wh1.eivus.com
IP
138.117.216.29
Banner
220-wh1.eivus.com ESMTP Exim 4.94 #2 Thu, 08 Apr 2021 04:18:01 -0300 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.
Starttls
yes
Dane
no
Mail size
50 MB
Expn
no
Vrfy
no

Smtp simulation

Connection to wh1.eivus.com ...
220-wh1.eivus.com ESMTP Exim 4.94 #2 Thu, 08 Apr 2021 04:18:01 -0300
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
HELO domain.com
250 wh1.eivus.com Hello ns.tools [195.154.82.101]
EHLO domain.com
250-wh1.eivus.com Hello ns.tools [195.154.82.101]
250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-X_PIPE_CONNECT
250-STARTTLS
250 HELP
QUIT
221 wh1.eivus.com closing connection
Autodiscover analysis not possible on an IP

SMTP server type is hidden

wh1.eivus.com with IP [138.117.216.29] displays the type of SMTP, exim founded

220-wh1.eivus.com ESMTP Exim 4.94 #2 Thu, 08 Apr 2021 04:18:01 -0300
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.

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

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

HELO command is accepted

Passed

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

RFC

0.000s

EHLO command is accepted

Passed

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

RFC

0.000s

STARTTLS command is accepted

Passed

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

Passed

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

Passed

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

0.000s

MX servers are not open relay

Passed

If a server is open relay, there is a risk that spammers use your server to send illegitimate mail.

42.420s

Banner return 2xx or 4xx code

Passed

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

0.000s

Banner return server name

Passed

Banner must contain the name of the server

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

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

Web

Website

Url
https://138.117.216.29/
Https
Title
Unknown
Description
Unknown
First paragraph
Unknown
Url
http://138.117.216.29/
Title
Unknown
Description
Unknown
Response time
0.393 second
Server
apache
Powered by
Unknown
Encoding
Unknown
HSTS

Headers

  • Accept-Ranges: bytes
  • Cache-Control: no-cache, no-store, must-revalidate
  • Connection: close
  • Content-Length: 163
  • Content-Type: text/html
  • Date: Thu, 08 Apr 2021 07:18:02 GMT
  • Expires: 0
  • Last-Modified: Sat, 06 Feb 2021 03:52:09 GMT
  • Pragma: no-cache
  • Server: Apache
Url
https://138.117.216.29/
Title
Unknown
Description
Unknown
Response time
0.6 second
Server
apache
Powered by
Unknown
Encoding
Unknown
HSTS

Headers

  • Accept-Ranges: bytes
  • Cache-Control: no-cache, no-store, must-revalidate
  • Connection: close
  • Content-Length: 163
  • Content-Type: text/html
  • Date: Thu, 08 Apr 2021 07:18:02 GMT
  • Expires: 0
  • Last-Modified: Sat, 06 Feb 2021 03:52:09 GMT
  • Pragma: no-cache
  • Server: Apache

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