Analysis report on IP address: 3.222.239.129

3.222.239.129 has no website

Generated on
14 Oct 2021 00:13
Duration of the analysis
46.2s
Share

Score 85%
B
DNS
-
IP
A
MAIL
-
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 239.222.3.in-addr.arpa

3.222.239.129 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
c.root-servers.net
[ 192.33.4.12 ]
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
151 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
5011 ms
Type
timeout
Headers
RCODE : - AA : - TC : -

Server timeout

Query informations

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

Response

Query informations

Server
e.in-addr-servers.arpa
[ 203.119.86.101 ]
Duration
258 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
arin.authdns.ripe.net
[ 193.0.9.10 ]
Duration
32 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
ns1-16-us-east-1.ec2-rdns.amazonaws.com
[ 205.251.197.174 ]
Duration
43 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns2-16-us-east-1.ec2-rdns.amazonaws.com
[ 205.251.199.162 ]
Duration
10 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns3-16-us-east-1.ec2-rdns.amazonaws.com
[ 205.251.193.162 ]
Duration
9 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns4-16-us-east-1.ec2-rdns.amazonaws.com
[ 205.251.194.123 ]
Duration
22 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns1-24-us-east-1.ec2-rdns.amazonaws.com
[ 205.251.197.231 ]
Duration
13 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns2-24-us-east-1.ec2-rdns.amazonaws.com
[ 205.251.198.46 ]
Duration
2 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns3-24-us-east-1.ec2-rdns.amazonaws.com
[ 205.251.192.197 ]
Duration
2 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns4-24-us-east-1.ec2-rdns.amazonaws.com
[ 205.251.195.169 ]
Duration
12 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

Ip

Informations

Ip
3.222.239.129
Type
ipv4
Reverse
ec2-3-222-239-129.compute-1.amazonaws.com
ARPA
129.239.222.3.in-addr.arpa
Class C
3.222.239.0/24
ASN
14618 AMAZON-AES
Organisation
 
Maintainer
 

Reputation

Blacklists
Ip
Whois server
whois.arin.net
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.
#


Amazon Technologies Inc. AT-88-Z (NET-3-128-0-0-1) 3.128.0.0 - 3.255.255.255
Amazon Data Services NoVa AMAZON-IAD (NET-3-208-0-0-1) 3.208.0.0 - 3.223.255.255



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

Mail

There is no mail server. Please test ec2-3-222-239-129.compute-1.amazonaws.com.

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://3.222.239.129/
Https
Title
404 Not Found
Description
Unknown
First paragraph
Unknown
Url
http://3.222.239.129/
Title
404 Not Found
Description
Unknown
Response time
0.19 second
Server
Unknown
Powered by
Unknown
Encoding
Unknown
HSTS

Headers

  • Connection: Close
  • Content-Length: 146
  • Content-Type: text/html
  • Date: Thu, 14 Oct 2021 00:13:51 GMT
Url
https://3.222.239.129/
Title
404 Not Found
Description
Unknown
Response time
0.345 second
Server
Unknown
Powered by
Unknown
Encoding
Unknown
HSTS

Headers

  • Connection: Close
  • Content-Length: 146
  • Content-Type: text/html
  • Date: Thu, 14 Oct 2021 00:13:51 GMT

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