Analysis report on domain: kett.pw favicon

kett.pw
Generated on
25 Nov 2021 16:18
Duration of the analysis
46.2s
Share

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

Resume

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

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

mx2.mailchannels.net with IP [34.223.167.51] does not contain the name of the server.

inbound-trex-0 (trex/6.4.3) ESMTP ready

mx2.mailchannels.net with IP [35.167.205.122] does not contain the name of the server.

inbound-trex-3 (trex/6.4.3) ESMTP ready

DKIM is configured for domain

We do not detect any DKIM record for this domain.

Host "www" have "AAAA" field

Host has no "AAAA" (IPv6) field for www.

Content Security Policy header is present

The Content-Security-Policy header was not found.

DNS

Dns servers for kett.pw

kett.pw was detected as domain

Query informations

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

Response

Query informations

Server
ns1.nic.pw
[ 194.169.218.12 ]
Duration
30 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns2.nic.pw
[ 185.24.64.12 ]
Duration
23 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns5.nic.pw
[ 212.18.248.12 ]
Duration
23 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns6.nic.pw
[ 212.18.249.12 ]
Duration
24 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns1.dreamhost.com
[ 162.159.26.14 ]
Duration
103 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Query informations

Server
ns2.dreamhost.com
[ 162.159.26.81 ]
Duration
110 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Query informations

Server
ns3.dreamhost.com
[ 162.159.27.84 ]
Duration
205 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Name servers

Mx Servers

Name
mx1.mailchannels.net
IPs
Priority
0
TTL
300 (5 minutes)
Name
mx2.mailchannels.net
IPs
Priority
0
TTL
300 (5 minutes)

A and AAAA fields

IPv4
69.163.227.125
TTL
300 (5 minutes )

Text Fields

Type
Spf (TXT)
TTL
300 (5 minutes)
Name
@
Raw data
v=spf1 mx include:netblocks.dreamhost.com include:relay.mailchannels.net -all
Mechanisms
mx
ALL
-all

Includes

netblocks.dreamhost.com
v=spf1 ip4:66.33.192.0/19 ip4:205.196.208.0/20 ip4:64.111.96.0/19 ip4:208.97.128.0/18 ip4:208.113.128.0/17 ip4:67.205.0.0/18 ip4:75.119.192.0/19 ip4:69.163.128.0/17 ip4:173.236.128.0/17 ip4:64.90.32.0/19 ip4:64.90.62.0/24 ip4:69.163.136.0/24 ip6:2607:F298::/32 include:relay.mailchannels.net ~all
Type
Dmarc
TTL
300 (5 minutes)
Raw data
v=DMARC1; p=reject; fo=1; rua=mailto:dmarc-agg8@kett.pw ;ruf=mailto:dmarc-forens8@kett.pw ;pct=100
Version
DMARC1
Percentage
100
Main Domain Procedure
reject
Error Report Policy
1
Forensic recipient
  • dmarc-forens8@kett.pw
Aggregate recipient
  • dmarc-agg8@kett.pw

SOA

From
ns3.dreamhost.com
Master server
ns1.dreamhost.com
TTL
300 (5 minutes)
Contact
fIOHiIF1h4h5hg==@dreamhost.com
Serial
2021112500
Refresh
16688 (4 hours)
Retry
600 (10 minutes)
Expire
1814400 (3 weeks)
Minimum
300 (5 minutes)

Hosts found

Name
www.kett.pw
IP
69.163.227.125
TTL
300 (5 minutes)
Name
ftp.kett.pw
IP
69.163.227.125
TTL
300 (5 minutes)
Name
mail.kett.pw
IP
64.90.62.162
TTL
300 (5 minutes)
Your domain is not protected by DNSSEC DNSSEC Definition

BIND version is hidden

Passed

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

0.009s

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

All servers return success

Passed

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

0.028s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.028s

DNS servers IP are differents

Passed

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

0.001s

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

DNS servers are synchronized

Passed

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

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

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

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

DNS servers IP are not private

Passed

It is strictly forbidden to have private IP in DNS

documentation

0.001s

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

Domain

Whois

Registrar
-
Owner
-
Created at
29 Nov 2013
Changed at
28 Jun 2020
Expires at
29 Nov 2023

Reputation

Google Safe Browsing
Web of trust
Blacklists
Virus Total
Domain
Whois server
whois.nic.pw
Created at
29 Nov 2013
Changed at
28 Jun 2020
Expires at
29 Nov 2023
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

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

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

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
mx2.mailchannels.net
IP
34.223.167.51
Banner
220 inbound-trex-0 (trex/6.4.3) ESMTP ready
Name
mx2.mailchannels.net
IP
35.167.205.122
Banner
220 inbound-trex-3 (trex/6.4.3) ESMTP ready

SPF

Find more informations about this SPF entry into the DNS > Zone tab

Raw data
v=spf1 mx include:netblocks.dreamhost.com include:relay.mailchannels.net -all

DKIM

Your domain has no DKIM selector found

Do you have one to analyse ?


DMARC

Find more informations about this DMARC entry into the DNS > Zone tab

Raw data
v=DMARC1; p=reject; fo=1; rua=mailto:dmarc-agg8@kett.pw ;ruf=mailto:dmarc-forens8@kett.pw ;pct=100
Name
mx2.mailchannels.net
IP
34.223.167.51
Banner
220 inbound-trex-0 (trex/6.4.3) ESMTP ready
Starttls
yes
Dane
no
Mail size
0 Bytes
Expn
no
Vrfy
no

Smtp simulation

Connection to mx2.mailchannels.net ...
220 inbound-trex-0 (trex/6.4.3) ESMTP ready
HELO domain.com
250 inbound-trex-0
EHLO domain.com
250-inbound-trex-0
250-8BITMIME
250-SMTPUTF8
250-STARTTLS
250 STARTTLS
QUIT
221 2.0.0 Bye
Name
mx2.mailchannels.net
IP
35.167.205.122
Banner
220 inbound-trex-3 (trex/6.4.3) ESMTP ready
Starttls
yes
Dane
no
Mail size
0 Bytes
Expn
no
Vrfy
no

Smtp simulation

Connection to mx2.mailchannels.net ...
220 inbound-trex-3 (trex/6.4.3) ESMTP ready
HELO domain.com
250 inbound-trex-3
EHLO domain.com
250-inbound-trex-3
250-8BITMIME
250-SMTPUTF8
250-STARTTLS
250 STARTTLS
QUIT
221 2.0.0 Bye

Autodiscover

DNS Config parsing
Name
_autodiscover._tcp.kett.pw
Priority
5
Weight
0
Port
443
Target
autoconfig.dreamhost.com
TTL
300 (5 minutes)
Autoconfig file not found
Autodiscover file not found

Banner return server name

mx2.mailchannels.net with IP [34.223.167.51] does not contain the name of the server.

inbound-trex-0 (trex/6.4.3) ESMTP ready

mx2.mailchannels.net with IP [35.167.205.122] does not contain the name of the server.

inbound-trex-3 (trex/6.4.3) ESMTP ready

Banner must contain the name of the server

0.008s

DKIM is configured for domain

We do not detect any DKIM record for this domain.

It is strongly recommended to configure DKIM. Note: You could use a service like Mailout to fix this problem. Click on below link to know more

mailout DKIM definition

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

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

MX servers accept abuse@ address

Passed

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

RFC

5.230s

MX servers accept postmaster@ address

Passed

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

RFC

4.861s

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

MX records are FQDN

Passed

MX must be a domain, not an IP.

RFC

0.000s

MX records are not CNAME

Passed

According to the RFC 1034 and 2181 CNAME records should not be used with NS and MX

RFC RFC

0.013s

SMTP server number

Passed

Domain should have at least 2 SMTP servers according to the RFC. Note: You can use a service like altospam to solve this problem. Click on the link below to learn more

0.000s

MX IPs are differents

Passed

The IP of the SMTP servers must be different if it is no longer reachable.

0.000s

MX IPs are in different class C

Passed

The class C of every IPs should be differents

0.001s

SPF is configured for domain

Passed

To avoid identity theft, it is strongly recommended to configure SPF.

0.000s

SPF record is TXT type

Passed

SPF record is no longer used, SPF must be into TXT record because many servers do not support SPF record. If SPF record exist, it should be the same as TXT

RFC

0.000s

Domain have only 1 SPF record

Passed

To avoid issue with SPF, it is strongly recommended to configure only one.

0.000s

SPF version exists

Passed

According to the RFC, the SPF version must be specified.

RFC

0.000s

SPF version at first position

Passed

SPF has to start with version's tag.

RFC

0.000s

SPF "all" exists

Passed

According to the RFC, the mecanism "all" must be specified in the SPF record, except if there is a Redirect tag.

RFC

0.000s

SPF "all" at last position

Passed

The mecanism "All" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.

RFC

0.000s

IPv4 & IPv6 syntaxes are corrects in SPF

Passed

IPs must be valid, otherwise the SPF will be useless.

RFC

0.000s

SPF haven't PTR

Passed

PTR has become obselete in SPF, should not be found in it.

RFC

0.000s

SPF "Redirect" at last position

Passed

The mecanism "Redirect" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.

RFC

0.000s

SPF records of type TXT & SPF are the same

Passed

SPF record has become obselete, if it is configured then it must be the same as the one present in the TXT record

0.000s

PTR must be just before All statement

Passed

The mecanism "PTR" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.

0.000s

DMARC is configured for domain

Passed

To avoid identity theft, it is strongly recommended to configure DMARC.

0.000s

Domain have only 1 DMARC record

Passed

To avoid issue with DMARC, it is strongly recommended to configure only one.

0.000s

DMARC version exist

Passed

According to the RFC 7489 section 6.3, the DMARC version is required.

RFC

0.000s

DMARC version at first position

Passed

According to the RFC 7489 section 6.3, the DMARC version must be the first tag in the list.

RFC

0.000s

DMARC procedure exists

Passed

According to the RFC 7489 section 6.3, the procedure is required.

RFC

0.000s

DMARC "p" field is valid

Passed

According to the RFC 7489 section 6.3, the procedure value must be none, quarantine or reject.

RFC

0.000s

DMARC "sp" field is valid

Passed

According to the RFC 7489 section 6.3, the subdomain procedure value must be none, quarantine or reject.

RFC

0.000s

DMARC "pct" field is valid

Passed

According to the RFC 7489 section 6.3, the percentage's value must be between 0 and 100.

RFC

0.000s

DMARC "adkim" field is valid

Passed

According to the RFC 7489 section 6.3, the adkim tag value must be the letter R or S.

RFC

0.000s

DMARC "aspf" field is valid

Passed

According to the RFC 7489 section 6.3, the aspf tag value must be the letter R or S.

RFC

0.000s

DMARC "rf" field is valid

Passed

According to the RFC 7489 section 6.3, the RF tag's value must be afrf or iodef.

RFC

0.000s

DMARC "ri" field is valid

Passed

According to the RFC 7489 section 6.3, the RI tag's value must be an integer.

RFC

0.000s

DMARC "ruf" field is valid

Passed

According to the RFC 7489 section 6.3, the RUF tag's value must be a valid email.

RFC

0.000s

DMARC "rua" field is valid

Passed

According to the RFC 7489 section 6.3, the RUA tag's value must be a valid email.

RFC

0.000s

DKIM version exist

Skipped

According to the RFC 6376 section 3.6.1, the DKIM version is required.

RFC

0.000s

DKIM Service Type is valid

Skipped

This Tag is optionnal but when use, it must be equal to "*" or "email".

RFC

0.000s

DKIM Testing flag is valid

Skipped

This Tag is optionnal but when use, it must be equal to "s", "y" or "y:s".

RFC

0.000s

DKIM public key is valid

Skipped

According to the RFC 6376 section 3.6.1, the public key is required and must be valid.

RFC

0.000s

DKIM public key is secure

Skipped

The size of the public key must be bigger than 1024 bits.

0.000s

Web

Website

Url
https://kett.pw/
Https
Title
kett.pw is almost here!
Description
The owner of this domain has not yet uploaded their website.
First paragraph
Upload your website to get started.
Url
http://www.kett.pw/
Redirect to
https://kett.pw/
Redirect code
301 - moved permanently

Headers

  • Connection: close
  • Content-Length: 224
  • Content-Type: text/html; charset=iso-8859-1
  • Date: Thu, 25 Nov 2021 16:18:34 GMT
  • Location: https://kett.pw/
  • Server: Apache
Url
https://kett.pw/
Title
kett.pw is almost here!
Description
The owner of this domain has not yet uploaded their website.
Response time
0.518 second
Server
apache
Powered by
Unknown
Encoding
Unknown
HSTS

Headers

  • Accept-Ranges: bytes
  • Connection: Upgrade, close
  • Content-Type: text/html
  • Date: Thu, 25 Nov 2021 16:18:35 GMT
  • ETag: "311-5d191aa872540"
  • Last-Modified: Thu, 25 Nov 2021 00:00:45 GMT
  • Server: Apache
  • Transfer-Encoding: chunked
  • Upgrade: h2
  • Vary: Accept-Encoding,User-Agent
Url
https://www.kett.pw/
Title
kett.pw is almost here!
Description
The owner of this domain has not yet uploaded their website.
Response time
0.495 second
Server
apache
Powered by
Unknown
Encoding
Unknown
HSTS

Headers

  • Accept-Ranges: bytes
  • Connection: Upgrade, close
  • Content-Type: text/html
  • Date: Thu, 25 Nov 2021 16:18:35 GMT
  • ETag: "311-5d191aa872540"
  • Last-Modified: Thu, 25 Nov 2021 00:00:45 GMT
  • Server: Apache
  • Transfer-Encoding: chunked
  • Upgrade: h2
  • Vary: Accept-Encoding,User-Agent

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

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

0.007s

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

Host "www" have "AAAA" field

Host has no "AAAA" (IPv6) field for www.

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

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

Host "www" have "A" field

Passed

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

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