Analysis report on IP address: 188.40.0.146

188.40.0.146 has no website

Generated on
15 Sep 2021 04:38
Duration of the analysis
17.2s
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 0.40.188.in-addr.arpa

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
pri.authdns.ripe.net
[ 193.0.9.5 ]
Duration
24 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
ns.second-ns.com
[ 213.239.204.242 ]
Duration
16 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns1.your-server.de
[ 213.133.106.251 ]
Duration
13 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns3.second-ns.de
[ 193.47.99.4 ]
Duration
15 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

Ip

Informations

Ip
188.40.0.146
Type
ipv4
Reverse
www32.flk1.host-h.net
ARPA
146.0.40.188.in-addr.arpa
Class C
188.40.0.0/24
ASN
24940 Hetzner Online GmbH
Organisation
HOAC1-RIPE
Maintainer
HOS-GUN

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 '188.40.0.128 - 188.40.0.159'

% Abuse contact for '188.40.0.128 - 188.40.0.159' is O3V2iYd5 [at] hetzner.com'

inetnum:        188.40.0.128 - 188.40.0.159
netname:        HETZNER-fsn1-dc13
descr:          Hetzner Online GmbH
descr:          Datacenter fsn1-dc13
country:        DE
admin-c:        HOAC1-RIPE
tech-c:         HOAC1-RIPE
status:         ASSIGNED PA
remarks:        INFRA-AW
mnt-by:         HOS-GUN
mnt-lower:      HOS-GUN
mnt-routes:     HOS-GUN
created:        2010-08-13T14:40:10Z
last-modified:  2018-03-15T14:12:47Z
source:         RIPE

% Information related to '188.40.0.0/16AS24940'

route:          188.40.0.0/16
descr:          HETZNER-RZ-FKS-BLK1
origin:         AS24940
org:            ORG-HOA1-RIPE
mnt-by:         HOS-GUN
created:        2009-04-23T15:49:32Z
last-modified:  2009-04-23T15:49:32Z
source:         RIPE

% This query was served by the RIPE Database Query Service version 1.101 (HEREFORD)


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
www32.flk1.host-h.net
IP
188.40.0.146
Banner
220 www32.flk1.host-h.net ESMTP XNEELO_MTA 1.00 Wed, 15 Sep 2021 06:38:25 +0200
Name
www32.flk1.host-h.net
IP
188.40.0.146
Banner
220 www32.flk1.host-h.net ESMTP XNEELO_MTA 1.00 Wed, 15 Sep 2021 06:38:25 +0200
Starttls
yes
Dane
no
Mail size
30 MB
Expn
no
Vrfy
no

Smtp simulation

Connection to www32.flk1.host-h.net ...
220 www32.flk1.host-h.net ESMTP XNEELO_MTA 1.00 Wed, 15 Sep 2021 06:38:25 +0200
HELO nstools.fr
250 www32.flk1.host-h.net Hello ns.tools [195.154.82.101]
EHLO nstools.fr
250-www32.flk1.host-h.net Hello ns.tools [195.154.82.101]
250-SIZE 31457280
250-8BITMIME
250-ETRN
250-PIPELINING
250-AUTH LOGIN PLAIN
250-STARTTLS
250 HELP
QUIT
221 www32.flk1.host-h.net closing connection
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

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.

3.135s

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

SMTP server type is hidden

Passed

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 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://188.40.0.146/
Https
Title
Login
Description
First paragraph
Unknown
Url
http://188.40.0.146/
Redirect to
https://188.40.0.146/
Redirect code
302 - found

Headers

  • Connection: close
  • Content-Length: 276
  • Content-Type: text/html; charset=iso-8859-1
  • Date: Wed, 15 Sep 2021 04:38:25 GMT
  • Location: https://188.40.0.146/
  • Server: Apache
Url
https://188.40.0.146/
Title
Login
Description
Response time
0.097 second
Server
apache
Powered by
Unknown
Encoding
Unknown
HSTS

Headers

  • Accept-Ranges: bytes
  • Connection: Upgrade, close
  • Content-Length: 7860
  • Content-Type: text/html
  • Date: Wed, 15 Sep 2021 04:38:25 GMT
  • ETag: "1eb4-5957f89182740"
  • Last-Modified: Tue, 22 Oct 2019 13:11:17 GMT
  • Server: Apache
  • Upgrade: h2,h2c
  • Vary: Accept-Encoding

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