Domain

IPs

97.74.101.42

Name

IPs

173.201.69.42

Host informations

Ips

153.126.165.85

Cname

Query informations

Server: d.root-servers.net
[ 199.7.91.13 ]
Duration: 28 ms
Type: authority
Headers: RCODE : 0 AA : 0 TC : 0

Response

Name

a0.info.afilias-nst.info

IPs

199.254.31.1

Name

a2.info.afilias-nst.info

IPs

199.249.113.1

Name

b0.info.afilias-nst.org

IPs

199.254.48.1

Name

b2.info.afilias-nst.org

IPs

199.249.121.1

Name

c0.info.afilias-nst.info

IPs

199.254.49.1

Name

d0.info.afilias-nst.org

IPs

199.254.50.1

Query informations

Server: a0.info.afilias-nst.info
[ 199.254.31.1 ]
Duration: 18 ms
Type: authority
Headers: RCODE : 0 AA : 0 TC : 0

Response

Name

IPs

97.74.101.42

Name

IPs

173.201.69.42

Query informations

Server: a2.info.afilias-nst.info
[ 199.249.113.1 ]
Duration: 13 ms
Type: authority
Headers: RCODE : 0 AA : 0 TC : 0

Response

Name

IPs

97.74.101.42

Name

IPs

173.201.69.42

Query informations

Server: b0.info.afilias-nst.org
[ 199.254.48.1 ]
Duration: 20 ms
Type: authority
Headers: RCODE : 0 AA : 0 TC : 0

Response

Name

IPs

97.74.101.42

Name

IPs

173.201.69.42

Query informations

Server: b2.info.afilias-nst.org
[ 199.249.121.1 ]
Duration: 13 ms
Type: authority
Headers: RCODE : 0 AA : 0 TC : 0

Response

Name

IPs

97.74.101.42

Name

IPs

173.201.69.42

Query informations

Server: c0.info.afilias-nst.info
[ 199.254.49.1 ]
Duration: 16 ms
Type: authority
Headers: RCODE : 0 AA : 0 TC : 0

Response

Name

IPs

97.74.101.42

Name

IPs

173.201.69.42

Query informations

Server: d0.info.afilias-nst.org
[ 199.254.50.1 ]
Duration: 15 ms
Type: authority
Headers: RCODE : 0 AA : 0 TC : 0

Response

Name

IPs

97.74.101.42

Name

IPs

173.201.69.42

Query informations

Server: ns63.domaincontrol.com
[ 97.74.101.42 ]
Duration: 12 ms
Type: unknown
Headers: RCODE : 0 AA : 1 TC : 0

Query informations

Server: ns64.domaincontrol.com
[ 173.201.69.42 ]
Duration: 12 ms
Type: unknown
Headers: RCODE : 0 AA : 1 TC : 0

Name servers

Name

IPs

97.74.101.42

Name

IPs

173.201.69.42

A and AAAA fields

IPv4: 153.126.165.85
TTL: 600 (10 minutes )

SOA

From: ns64.domaincontrol.com
Master server: ns63.domaincontrol.com
TTL: 600 (10 minutes)
Contact: eIKH@jomax.net
Serial: 2017100404
Refresh: 28800 (8 hours)
Retry: 7200 (2 hours)
Expire: 604800 (1 week)
Minimum: 600 (10 minutes)

Your domain is not protected by DNSSEC DNSSEC Definition

BIND version is hidden

Dns version is visible for ns63.domaincontrol.com with IP 97.74.101.42 : 9.11.22.

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

5.015s

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.

0.000s

All Dns servers are responding

Passed

Every DNS servers should be accessible and accept public query.

0.002s

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.

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.

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.

0.000s

SOA refresh is valid

Passed

The refresh value be must between 1200 and 43200.

0.000s

SOA retry, refresh and expire values are correct

Passed

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

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

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.

0.060s

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

DNS servers IP are not private

Passed

It is strictly forbidden to have private IP in DNS

Resume Whois Reputation Tests

0.000s

Same MX are returned

Passed

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

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: 10 Jan 2009
Changed at: 11 Jan 2021
Expires at: 10 Jan 2022

Reputation

Google Safe Browsing
Web of trust
Blacklists
Virus Total

Domain

Whois server

whois.afilias.net

Created at

10 Jan 2009

Changed at

11 Jan 2021

Expires at

10 Jan 2022

Name servers

Owner

Name: -
Organization: 123server
Address: -
City: -
Zip code: -
Country: JP
Phone: -
Email

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

Detection ratio: /

Scans

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

Resume Servers Autodiscover Tests

Mail servers

Name: u023.u023jp9938.info
IP: 153.126.165.85
Banner: 220-u023.u023jp9938.info ESMTP Exim 4.94 #2 Thu, 08 Apr 2021 17:51:12 +0900 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.

Name: u023.u023jp9938.info
IP: 153.126.165.85
Banner: 220-u023.u023jp9938.info ESMTP Exim 4.94 #2 Thu, 08 Apr 2021 17:51:12 +0900 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.
Starttls: yes
Dane: no
Mail size: 50 MB
Expn: no
Vrfy: no

Smtp simulation

Connection to u023.u023jp9938.info ...: 220-u023.u023jp9938.info ESMTP Exim 4.94 #2 Thu, 08 Apr 2021 17:51:12 +0900
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
HELO nstools.fr: 250 u023.u023jp9938.info Hello ns.tools [195.154.82.101]
EHLO nstools.fr: 250-u023.u023jp9938.info Hello ns.tools [195.154.82.101]
250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-X_PIPE_CONNECT
250-STARTTLS
250 HELP
QUIT: 221 u023.u023jp9938.info closing connection

Autodiscover not configured

MX servers accept abuse@ address

u023.u023jp9938.info [153.126.165.85] does not accept email to abuse@nahif.info.

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

42.201s

MX servers accept postmaster@ address

u023.u023jp9938.info [153.126.165.85] does not accept email to postmaster@nahif.info.

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

43.112s

SMTP server type is hidden

u023.u023jp9938.info with IP [153.126.165.85] displays the type of SMTP, exim founded

220-u023.u023jp9938.info ESMTP Exim 4.94 #2 Thu, 08 Apr 2021 17:51:12 +0900
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.

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

0.000s

HELO command is accepted

Passed

According to the RFC 2181, smtp server should accept HELO command

0.000s

EHLO command is accepted

Passed

According to the RFC 2181, smtp server should accept EHLO command

Resume Informations Tests

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.

43.091s

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

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

Web

Website

Url: https://ns2.nahif.info/
Https
Title: リゲルグランドのクチコミ・インドエステの口コミ情報
Description: Unknown
First paragraph: 今年も残り少なくなりましたね。この1年もいろいろな面で頑張ってきたと思います。家事はもちろんなんですが、ある資格を以前から取りたいなぁ～と思っていましたが、今年、念願かなって見事合格することができました。合格するには、やはり、それなりに勉強も大変でしたね。今年は、そんな自分にちょっとだけご褒美もいいかな～なんて思っております。エステに行ってちょっとセイプアップなんてどうかと思っていましたら、いい情報をゲット！インドエステ専門サロン「リゲルグランド」なんですが、こちらでは、痩身インドエステマッサージをやっていただけるそうで、これは、ぜひ受けてみたいですね。また、アロマオイルを使ってのマッサージですので、リラックスした雰囲気の中でやっていただけるのではと思います。初めてのところですと、やはり緊張しますのでこちらでしたら、心安らいでいいと思いますね。また、リゲルグランドクチコミでも皆さんになかなか評価もいいようですよ。痩身インドエステには専門的なマッサージ技術と知識が必要になってくるそうで、生半可なマッサージではうまくいかないそうです。こちらでしたら技術面でも安心できますね女性なら、エステに行きたいって思ってしまう人が多いと思います。私も興味はあるんですが、どこがいいんだろうって思って、迷って、なかなか行けないって言うタイプなんです。こういう人は、口コミを参考にするんですよ。今は、インターネットでいろいろな口コミを見ることができちゃいますから。リゲルグランドクチコミを見ると、行ってみようかなって思うんです。本格的なインドエステを堪能できるんですって。本格的って...

Url: http://ns2.nahif.info/

Title: Unknown
Description: Unknown
Response time: 0.558 second
Server: apache
Powered by: Unknown
Encoding: Unknown
HSTS

Headers

Accept-Ranges: bytes
Cache-Control: no-cache, no-store, must-revalidate
Connection: close
Content-Length: 163
Content-Type: text/html
Date: Thu, 08 Apr 2021 08:51:13 GMT
Expires: 0
Last-Modified: Sat, 06 Feb 2021 03:52:09 GMT
Pragma: no-cache
Server: Apache

Url: https://ns2.nahif.info/

Title: リゲルグランドのクチコミ・インドエステの口コミ情報
Description: Unknown
Response time: 1.065 seconds
Server: apache
Powered by: Unknown
Encoding: Unknown
HSTS

Headers

Accept-Ranges: bytes
Connection: close
Content-Length: 14162
Content-Type: text/html
Date: Thu, 08 Apr 2021 08:51:14 GMT
Last-Modified: Wed, 23 Mar 2016 13:40:59 GMT
Server: Apache

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

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

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.

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.

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).

0.000s

Domain have "A" field

Passed

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

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)