Analysis report on IP address: 81.7.7.41

81.7.7.41 has no website

Generated on
22 Jul 2021 06:40
Duration of the analysis
29.1s
Share

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

Resume

VRFY command is refused

mx0.jmt.gr [81.7.7.41] authorizes VRFY command.

Banner return server name

mx0.jmt.gr with IP [81.7.7.41] does not contain the name of the server.

ready

DNS

Dns servers for 7.7.81.in-addr.arpa

81.7.7.41 was detected as ipv4

Query informations

Server
a.root-servers.net
[ 198.41.0.4 ]
Duration
31 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
a.in-addr-servers.arpa
[ 199.180.182.53 ]
Duration
142 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
176 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

Server
e.in-addr-servers.arpa
[ 203.119.86.101 ]
Duration
259 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
ns3.afrinic.net
[ 204.61.216.100 ]
Duration
131 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
156 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
k1.kundencontroller.de
[ 85.31.185.124 ]
Duration
28 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns1.kundencontroller.de
[ 85.31.185.126 ]
Duration
35 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns2.kundencontroller.de
[ 85.31.184.6 ]
Duration
30 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns3.kundencontroller.de
[ 85.31.184.7 ]
Duration
28 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

Ip

Informations

Ip
81.7.7.41
Type
ipv4
Reverse
mx0.jmt.gr
ARPA
41.7.7.81.in-addr.arpa
Class C
81.7.7.0/24
ASN
35366 ISPpro Internet KG
Organisation
HMIP1-RIPE
Maintainer
ISPPRO-NOC-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 '81.7.7.0 - 81.7.7.255'

% Abuse contact for '81.7.7.0 - 81.7.7.255' is O3V2iYd5 [at] isppro.de'

inetnum:        81.7.7.0 - 81.7.7.255
netname:        EUSERV-SRV-NET16
descr:          EUserv Internet
descr:          Customer Network #16
descr:          Dedicated Rootserver Network
descr:          http://www.euserv.de
descr:          Rootserver, Webspace, Domains,
descr:          Gameserver, Housing, Streaming
country:        DE
admin-c:        HMIP1-RIPE
tech-c:         HMIP1-RIPE
status:         ASSIGNED PA
mnt-by:         ISPPRO-NOC-MNT
created:        2010-07-05T10:01:50Z
last-modified:  2010-07-05T10:01:50Z
source:         RIPE

% Information related to '81.7.0.0/19AS35366'

route:          81.7.0.0/19
origin:         AS35366
mnt-by:         ISPPRO-NOC-MNT
created:        2019-05-06T20:33:54Z
last-modified:  2019-05-06T20:33:54Z
source:         RIPE

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


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

Mail

Mail servers

Name
mx0.jmt.gr
IP
81.7.7.41
Banner
220 ESMTP ready
Name
mx0.jmt.gr
IP
81.7.7.41
Banner
220 ESMTP ready
Starttls
yes
Dane
yes
Mail size
97.66 MB
Expn
no
Vrfy
yes

Smtp simulation

Connection to mx0.jmt.gr ...
220 ESMTP ready
HELO domain.com
250 mx0.jmt.gr
EHLO domain.com
250-mx0.jmt.gr
250-PIPELINING
250-SIZE 102400000
250-VRFY
250-ETRN
250-STARTTLS
250-AUTH PLAIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
QUIT
221 2.0.0 Bye
Autodiscover analysis not possible on an IP

VRFY command is refused

mx0.jmt.gr [81.7.7.41] authorizes VRFY command.

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

0.000s

Banner return server name

mx0.jmt.gr with IP [81.7.7.41] does not contain the name of the server.

ready

Banner must contain the name of the server

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

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.

0.250s

Banner return 2xx or 4xx code

Passed

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

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

There is no web server. Please test mx0.jmt.gr.

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