Analysis report on IP address: 49.212.36.229

49.212.36.229 has no website

Generated on
15 Sep 2021 08:22
Duration of the analysis
18.4s
Share

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

Resume

SMTP server type is hidden

maxiumdomain.com with IP [49.212.36.229] displays the type of SMTP, exim founded

220 ip124.ultra-server.jp ESMTP Exim 4.92.3 Wed, 15 Sep 2021 17:22:23 +0900

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.

Banner return server name

maxiumdomain.com with IP [49.212.36.229] does not contain the name of the server.

ip124.ultra-server.jp ESMTP Exim 4.92.3 Wed, 15 Sep 2021 17:22:23 +0900

Content Security Policy header is present

The Content-Security-Policy header was not found.

DNS

Dns servers for 36.212.49.in-addr.arpa

49.212.36.229 was detected as ipv4

Query informations

Server
a.root-servers.net
[ 198.41.0.4 ]
Duration
25 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
41 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
e.in-addr-servers.arpa
[ 203.119.86.101 ]
Duration
260 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
apnic.authdns.ripe.net
[ 193.0.9.9 ]
Duration
510 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
apnic1.dnsnode.net
[ 194.146.106.106 ]
Duration
18 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns2.apnic.net
[ 203.119.95.53 ]
Duration
13 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
rirns.arin.net
[ 199.253.249.53 ]
Duration
140 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns1.dns.ne.jp
[ 61.211.236.1 ]
Duration
248 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns2.dns.ne.jp
[ 133.167.21.1 ]
Duration
255 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

Ip

Informations

Ip
49.212.36.229
Type
ipv4
Reverse
maxiumdomain.com
ARPA
229.36.212.49.in-addr.arpa
Class C
49.212.36.0/24
ASN
9371 SAKURA Internet Inc.
Organisation
JNIC1-AP
Maintainer
MAINT-JPNIC

Reputation

Blacklists
Ip
Whois server
whois.apnic.net
Raw data
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '49.212.0.0 - 49.212.255.255'

% Abuse contact for '49.212.0.0 - 49.212.255.255' is O3yDh4iBdYeIeYY= [at] nic.ad.jp'

inetnum:        49.212.0.0 - 49.212.255.255
netname:        SAKURA-OSAKA
descr:          SAKURA Internet Inc.
descr:          Grandfront Osaka Bldg. Tower-A 35F, 4-20, Ofukacho, Kita-ku, Osaka 530-0011 Japan
admin-c:        JNIC1-AP
tech-c:         JNIC1-AP
remarks:        Email address for spam or abuse complaints : dXaJh3k= [at] sakura.ad.jp
country:        JP
mnt-by:         MAINT-JPNIC
mnt-lower:      MAINT-JPNIC
mnt-irt:        IRT-JPNIC-JP
status:         ALLOCATED PORTABLE
last-modified:  2017-11-08T09:05:53Z
source:         APNIC

% Information related to '49.212.36.0 - 49.212.36.255'

inetnum:        49.212.36.0 - 49.212.36.255
netname:        SAKURA-NET
descr:          SAKURA Internet Inc.
country:        JP
admin-c:        KT749JP
tech-c:         KW419JP
remarks:        This information has been partially mirrored by APNIC from
remarks:        JPNIC. To obtain more specific information, please use the
remarks:        JPNIC WHOIS Gateway at
remarks:        http://www.nic.ad.jp/en/db/whois/en-gateway.html or
remarks:        whois.nic.ad.jp for WHOIS client. (The WHOIS client
remarks:        defaults to Japanese output, use the /e switch for English
remarks:        output)
last-modified:  2011-03-07T22:47:04Z
source:         JPNIC

% This query was served by the APNIC Whois Service version 1.88.15-SNAPSHOT (WHOIS-UK4)


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
maxiumdomain.com
IP
49.212.36.229
Banner
220 ip124.ultra-server.jp ESMTP Exim 4.92.3 Wed, 15 Sep 2021 17:22:23 +0900
Name
maxiumdomain.com
IP
49.212.36.229
Banner
220 ip124.ultra-server.jp ESMTP Exim 4.92.3 Wed, 15 Sep 2021 17:22:23 +0900
Starttls
yes
Dane
no
Mail size
50 MB
Expn
no
Vrfy
no

Smtp simulation

Connection to maxiumdomain.com ...
220 ip124.ultra-server.jp ESMTP Exim 4.92.3 Wed, 15 Sep 2021 17:22:23 +0900
HELO domain.com
250 ip124.ultra-server.jp Hello ns.tools [195.154.82.101]
EHLO domain.com
250-ip124.ultra-server.jp Hello ns.tools [195.154.82.101]
250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-CHUNKING
250-STARTTLS
250-PRDR
250 HELP
QUIT
221 ip124.ultra-server.jp closing connection
Autodiscover analysis not possible on an IP

SMTP server type is hidden

maxiumdomain.com with IP [49.212.36.229] displays the type of SMTP, exim founded

220 ip124.ultra-server.jp ESMTP Exim 4.92.3 Wed, 15 Sep 2021 17:22:23 +0900

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

Banner return server name

maxiumdomain.com with IP [49.212.36.229] does not contain the name of the server.

ip124.ultra-server.jp ESMTP Exim 4.92.3 Wed, 15 Sep 2021 17:22:23 +0900

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

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.

2.724s

Banner return 2xx or 4xx code

Passed

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

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://49.212.36.229/
Https
Title
Apache HTTP Server Test Page powered by CentOS
Description
Unknown
First paragraph
This page is used to test the proper operation of the Apache HTTP server after it has been installed. If you can read this page it means that the Apache HTTP server installed at this site is working properly. The fact that you are seeing this page indicates that the website you just visited is either experiencing problems or is undergoing routine maintenance. If you would like to let the administrators of this website know that you've seen this page instead of the page you expected, you should send them e-mail. In general, mail sent to the name "webmaster" and directed to the website's domain should reach the appropriate person. For example, if you experienced problems while visiting www....
Url
http://49.212.36.229/
Title
Apache HTTP Server Test Page powered by CentOS
Description
Unknown
Response time
0.515 second
Server
apache
Powered by
Unknown
Encoding
Unknown
HSTS

Headers

  • Accept-Ranges: bytes
  • Connection: close
  • Content-Length: 4961
  • Content-Type: text/html
  • Date: Wed, 15 Sep 2021 08:22:25 GMT
  • Server: Apache
Url
https://49.212.36.229/
Title
Apache HTTP Server Test Page powered by CentOS
Description
Unknown
Response time
1.101 seconds
Server
apache
Powered by
Unknown
Encoding
Unknown
HSTS

Headers

  • Accept-Ranges: bytes
  • Connection: close
  • Content-Length: 4961
  • Content-Type: text/html
  • Date: Wed, 15 Sep 2021 08:22:26 GMT
  • 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