Analysis report on IP address: 217.12.208.118

217.12.208.118 has no website

Generated on
15 Sep 2021 05:29
Duration of the analysis
10.9s
Share

Score 83%
C
DNS
-
IP
A
MAIL
A
WEB
C

Resume

Web application technology is hidden

Server is powered by: Express

Cookies are secure

The HttpOnly flag was not found.

The Secure flag was not found.

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.

HTTPS port (443) is open

The https port is close while there is a website.

Content Security Policy header is present

The Content-Security-Policy header was not found.

DNS

Dns servers for 208.12.217.in-addr.arpa

217.12.208.118 was detected as ipv4

Query informations

Server
j.root-servers.net
[ 192.58.128.30 ]
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
141 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
ns3.lacnic.net
[ 200.3.13.14 ]
Duration
197 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

Server
pri.authdns.ripe.net
[ 193.0.9.5 ]
Duration
18 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

Server
ns3.layer6.net
[ 195.123.245.45 ]
Duration
24 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns3.layer6.net
[ 195.123.243.46 ]
Duration
146 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns4.layer6.net
[ 195.123.233.95 ]
Duration
76 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
rdns-kha1.layer6.net
[ 217.12.200.136 ]
Duration
14 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

Ip

Informations

Ip
217.12.208.118
Type
ipv4
Reverse
protoserver.site
ARPA
118.208.12.217.in-addr.arpa
Class C
217.12.208.0/24
ASN
21100 ITL LLC
Organisation
ORG-GFL1-RIPE
Maintainer
GRFL-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 '217.12.208.0 - 217.12.209.255'

% Abuse contact for '217.12.208.0 - 217.12.209.255' is O3V2iYd5 [at] greenfloid.com'

inetnum:        217.12.208.0 - 217.12.209.255
netname:        GF-AMS-NET
remarks:        Geofeed https://itldc.com/ipgeo.csv
descr:          ***********************************************************
descr:          * As ISP we provide hosting, virtual and dedicated servers.
descr:          *
descr:          * Those services are self managed by our customers
descr:          * therefore, we are not using this IP space ourselves
descr:          * and it could be assigned to various end customers.
descr:          *
descr:          * In case of issues related with SPAM, Fraud, Phishing
descr:          * DDoS, port scans or others, feel free to contact us
descr:          * with relevant info. Abuse email: dXaJh3k= [at] greenfloid.com
descr:          ***********************************************************
country:        NL
geoloc:         52.7179748 6.1999859
org:            ORG-GFL1-RIPE
admin-c:        GFES1-RIPE
tech-c:         GFES1-RIPE
status:         ASSIGNED PA
mnt-by:         GRFL-MNT
created:        2007-03-03T09:41:09Z
last-modified:  2021-03-20T19:06:51Z
source:         RIPE

% Information related to '217.12.208.0/23AS21100'

route:          217.12.208.0/23
descr:          GREENFLOID-NL
origin:         AS21100
mnt-by:         ITL-MNT
created:        2017-05-15T09:00:21Z
last-modified:  2017-05-15T09:00:21Z
source:         RIPE

% This query was served by the RIPE Database Query Service version 1.101 (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.002s

Mail

There is no mail server. Please test protoserver.site.

Name
protoserver.site
IP
217.12.208.118
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
http://217.12.208.118/login
Https
Title
Grabber - Grabber
Description
The most beautiful application
First paragraph
Unknown
Url
http://217.12.208.118/
Redirect to
http://217.12.208.118/login
Redirect code
302 - found

Headers

  • Access-Control-Allow-Credentials: true
  • Access-Control-Allow-Headers: X-Requested-With, X-HTTP-Method-Override, Content-Type, Accept, Authorization
  • Access-Control-Allow-Methods: GET, POST, DELETE
  • Access-Control-Allow-Origin: undefined
  • Connection: close
  • Date: Wed, 15 Sep 2021 05:29:57 GMT
  • Location: /login
  • Server: nginx
  • Set-Cookie: auth.strategy=local; Path=/, auth.redirect=%2F; Path=/
  • Transfer-Encoding: chunked
  • X-Powered-By: Express
Url
http://217.12.208.118/login
Title
Grabber - Grabber
Description
The most beautiful application
Response time
0.145 second
Server
nginx
Powered by
express
Encoding
utf-8
HSTS

Headers

  • Accept-Ranges: none
  • Access-Control-Allow-Credentials: true
  • Access-Control-Allow-Headers: X-Requested-With, X-HTTP-Method-Override, Content-Type, Accept, Authorization
  • Access-Control-Allow-Methods: GET, POST, DELETE
  • Access-Control-Allow-Origin: undefined
  • Connection: close
  • Content-Length: 349696
  • Content-Type: text/html; charset=utf-8
  • Date: Wed, 15 Sep 2021 05:29:57 GMT
  • ETag: "55600-rtP8BRXVOvr2TE1xfbIpMf8h5Mo"
  • Server: nginx
  • Set-Cookie: auth.strategy=local; Path=/
  • Vary: Accept-Encoding
  • X-Powered-By: Express
Url
https://217.12.208.118/
Reachable
No

Web application technology is hidden

Server is powered by: Express

To avoid giving details to malicious people, the technology that supports the application should not be visible.

0.000s

Cookies are secure

The HttpOnly flag was not found.

The Secure flag was not found.

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

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

HTTPS port (443) is open

The https port is close while there is a website.

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

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

Web server version is hidden

Passed

To avoid giving details to malicious people, the version of the server should not be visible.

0.000s