Analysis report on domain: www424.sakura.ne.jp favicon

www424.sakura.ne.jp has no website

Generated on
22 Jul 2021 10:39
Duration of the analysis
85.9s
Share

Score 79%
B
DNS
B
DOMAIN
A
MAIL
B
WEB
B

Resume

Same MX are returned

Server 133.167.21.1 returns different MX records from 61.211.236.1:
www424.sakura.ne.jp

BIND version is hidden

Dns version is visible for ns1.dns.ne.jp with IP 61.211.236.1 : 9.11.22.

Dns version is visible for ns2.dns.ne.jp with IP 133.167.21.1 : NSD 4.1.23.

MX servers accept abuse@ address

www424.sakura.ne.jp [59.106.13.54] does not accept email to abuse@sakura.ne.jp.

MX servers accept postmaster@ address

www424.sakura.ne.jp [59.106.13.54] does not accept email to postmaster@sakura.ne.jp.

SMTP server type is hidden

www424.sakura.ne.jp with IP [59.106.13.54] displays the type of SMTP, sendmail founded

220 www424.sakura.ne.jp ESMTP Sendmail 8.15.2/8.15.2; Thu, 22 Jul 2021 19:40:22 +0900 (JST)

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 sakura.ne.jp

www424.sakura.ne.jp was detected as host

Host informations

Ips
 
Cname
-

Query informations

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

Response

Query informations

Server
a.dns.jp
[ 203.119.1.1 ]
Duration
1282 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
b.dns.jp
[ 202.12.30.131 ]
Duration
246 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
c.dns.jp
[ 156.154.100.5 ]
Duration
4 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
d.dns.jp
[ 210.138.175.244 ]
Duration
81 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
e.dns.jp
[ 192.50.43.53 ]
Duration
5010 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
f.dns.jp
[ 150.100.6.8 ]
Duration
242 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
g.dns.jp
[ 203.119.40.1 ]
Duration
265 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
h.dns.jp
[ 161.232.72.25 ]
Duration
14 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Query informations

Server
ns2.dns.ne.jp
[ 133.167.21.1 ]
Duration
267 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Name servers

Mx Servers

Name
www424.sakura.ne.jp
IPs
Priority
10
TTL
3600 (1 hour)

A and AAAA fields

IPv4
59.106.13.54
TTL
3600 (1 hour )
IPv6
2001:e42:101:3:59:106:13:54
TTL
3600 (1 hour )

SOA

From
ns2.dns.ne.jp
Master server
dns.sakura.ad.jp
TTL
3600 (1 hour)
Contact
goN3@sakura.ad.jp
Serial
2021071600
Refresh
3600 (1 hour)
Retry
600 (10 minutes)
Expire
3600000 (1 month)
Minimum
3600 (1 hour)
Your domain is not protected by DNSSEC DNSSEC Definition

Same MX are returned

Server 133.167.21.1 returns different MX records from 61.211.236.1:
www424.sakura.ne.jp

It is extremely important that each DNS return the same MX records in order to avoid contacting an SMTP server that no longer exists.

0.281s

BIND version is hidden

Dns version is visible for ns1.dns.ne.jp with IP 61.211.236.1 : 9.11.22.

Dns version is visible for ns2.dns.ne.jp with IP 133.167.21.1 : NSD 4.1.23.

The Bind version should not be visible otherwise it will be possible to search for potential security vulnerabilities of the version.

0.284s

Domain have at least 2 DNS servers

Passed

In order for the availability rate of DNS servers to be at its highest, it is vital and recommended by the RFC to have at least 2 servers.

RFC

0.000s

All Dns servers are responding

Passed

Every DNS servers should be accessible and accept public query.

0.006s

All servers return success

Passed

It's important that all servers returned a "success" code.

0.002s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.002s

DNS servers IP are differents

Passed

IPs for DNS servers must be different in order to have high availability.

0.000s

DNS servers IP are in different class C

Passed

The class C of each IP must be different so that the servers are not found on the same bay and therefore there is a risk of unavailability.

RFC

0.000s

SOA are synchronized

Passed

The SOA answered by the DNS servers must be identical for each servers. The most important information is the master server and the contact email address.

0.000s

SOA email is valid

Passed

An email address must respect some conditions to be valid, accordding to the RFC 5322.

RFC

0.000s

SOA refresh is valid

Passed

The refresh value be must between 1200 and 43200.

RFC

0.000s

SOA retry, refresh and expire values are correct

Passed

The Retry, Refresh and Expire values musth follow this path : retry < refresh < expire.

RFC

0.000s

DNS servers are not open relay

Passed

DNS resolvers that allow queries from all IP addresses and are exposed to the Internet can be attacked and used to conduct Denial of Service (DoS) attacks on behalf of the hacker.

0.284s

Transfer zone is disable

Passed

An attacker can use a zone transfer that contains a malicious code or an inappropriate format that crashes a DNS server vulnerable to this type of attack, which results in a DoS that destabilizes the DNS services. It is possible to test it manually with this commands: #host -T axfr or #dig axfr.

documentation

0.912s

Recursive query is disable

Passed

Having a dns server that allow recursive queries is a security risk, DDOS attack can be performed.

RFC documentation documentation

0.280s

DNS servers IP are not private

Passed

It is strictly forbidden to have private IP in DNS

documentation

0.000s

DNS servers are synchronized

Skipped

The synchronization of the DNS servers must be perfect in order to avoid any dns resolution error. The servers must therefore give the same answer when asked "what are the DNS servers for the domain?".

0.000s

Domain

Whois

Registrar
-
Owner
-
Created at
21 Jul 2017
Changed at
31 Jul 2020
Expires at
unknown

Reputation

Google Safe Browsing
Web of trust
Blacklists
Virus Total
Domain
Whois server
whois.jprs.jp
Created at
21 Jul 2017
Changed at
31 Jul 2020
Expires at
unknown
Name servers

Google Safe Browsing

Status

Web of Trust

Status

Blacklists

RFC Ignorant
Rbl Jp
RblDns
Sorbs
Spam Eating Monkey
SpamHaus
SuRbl
Support Intelligence
Swinog
UriBl

Virus Total

VirusTotal is analysing. Please wait

DNS servers are same in dns tree and whois

Passed

The dns servers given in the domain whois must be the same as those returned by a dns resolution request.

0.000s

Domain is not blacklisted

Passed

A domain must not be blacklisted or it will be penalized for referencing and deliverability of emails.

0.000s

Domain is not listed in Google Safe Browsing

Passed

Google safe browsing categorizes a domain as bad if something suspicious is detected.

0.000s

Domain is not listed in VirusTotal

Passed

Virus Total analyze your domain or IP address with 66 antivirus.

0.000s

Domain have good reputation on Web of Trust

Passed

Web Of Trust rates thousands of websites and find threats if they exist.

0.000s

Mail

Mail servers

Name
www424.sakura.ne.jp
IP
59.106.13.54
Banner
220 www424.sakura.ne.jp ESMTP Sendmail 8.15.2/8.15.2; Thu, 22 Jul 2021 19:40:22 +0900 (JST)
Name
www424.sakura.ne.jp
IP
59.106.13.54
Banner
220 www424.sakura.ne.jp ESMTP Sendmail 8.15.2/8.15.2; Thu, 22 Jul 2021 19:40:22 +0900 (JST)
Starttls
yes
Dane
no
Mail size
200 MB
Expn
no
Vrfy
no

Smtp simulation

Connection to www424.sakura.ne.jp ...
220 www424.sakura.ne.jp ESMTP Sendmail 8.15.2/8.15.2; Thu, 22 Jul 2021 19:40:22 +0900 (JST)
HELO domain.com
250 www424.sakura.ne.jp Hello ns.tools [195.154.82.101], pleased to meet you
EHLO domain.com
250-www424.sakura.ne.jp Hello ns.tools [195.154.82.101], pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE 209715200
250-DSN
250-ETRN
250-AUTH CRAM-MD5 DIGEST-MD5 LOGIN PLAIN
250-STARTTLS
250-DELIVERBY
250 HELP
QUIT
221 2.0.0 www424.sakura.ne.jp closing connection

Autodiscover not configured

MX servers accept abuse@ address

www424.sakura.ne.jp [59.106.13.54] does not accept email to abuse@sakura.ne.jp.

According to the RFC 2142, SMTP server should accept abuse@yourDomain as a recipient.

RFC

2.162s

MX servers accept postmaster@ address

www424.sakura.ne.jp [59.106.13.54] does not accept email to postmaster@sakura.ne.jp.

According to the RFC 5321, SMTP server should accept postmaster@yourDomain as a recipient.

RFC

1.879s

SMTP server type is hidden

www424.sakura.ne.jp with IP [59.106.13.54] displays the type of SMTP, sendmail founded

220 www424.sakura.ne.jp ESMTP Sendmail 8.15.2/8.15.2; Thu, 22 Jul 2021 19:40:22 +0900 (JST)

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

Passed

Smtp servers that are listed in DNS area must be accessible, otherwise, there is a risk that emails may be lost

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

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

Web

Website

Url
https://www424.sakura.ne.jp/
Https
Title
さくらのレンタルサーバ
Description
Unknown
First paragraph
このサーバは、さくらのレンタルサーバで提供されています。 さくらのレンタルサーバ はじめてでもビジネスでも使える共有レンタルサーバサービス 2週間無料お試し付きで選べる全5プラン! レンタルサーバなら「さくらのレンタルサーバ」! 月額換算でわずか131円、缶ジュース1本分のお値段で使える格安プランから、ビジネスにも使える多機能&大容量プランまで、 用途と予算に合わせてプランを選べます。 さらにマルチドメイン対応でメールアドレスも無制限。無料ウイルススキャンや無料電話サポートもあるので安心して ご利用いただける共用レンタルサーバサービスです。 (C)Copyright 1996-2021 SAKURA Internet Inc.
Url
http://www424.sakura.ne.jp/
Title
さくらのレンタルサーバ
Description
Unknown
Response time
0.737 second
Server
nginx
Powered by
Unknown
Encoding
Unknown
HSTS

Headers

  • Connection: close
  • Content-Type: text/html
  • Date: Thu, 22 Jul 2021 10:40:24 GMT
  • Server: nginx
  • Transfer-Encoding: chunked
Url
https://www424.sakura.ne.jp/
Title
さくらのレンタルサーバ
Description
Unknown
Response time
1.214 seconds
Server
nginx
Powered by
Unknown
Encoding
Unknown
HSTS

Headers

  • Connection: close
  • Content-Type: text/html
  • Date: Thu, 22 Jul 2021 10:40:25 GMT
  • Server: nginx
  • Transfer-Encoding: chunked

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

Domain have "A" field

Passed

The domain must have an A field in order for the website to be accessible.

0.000s

Domain have "AAAA" field

Passed

It is highly recommended to have an IPv6 for the website.

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

Host "www" have "A" field

Skipped

WWW host is not required for a website, but it's better to have one.

0.000s

Host "www" have "AAAA" field

Skipped

If you configure a WWW host for your website, it is recommended to have an IPv6.

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