Analysis report on domain: ripe.net favicon

ripe.net
Generated on
28 Jun 2018 08:32
Duration of the analysis
26.2s
Share

Score 72%
C
DNS
C
DOMAIN
A
MAIL
A
WEB
B

Resume

Transfer zone is disable

manus.authdns.ripe.net [193.0.9.7] allows DNS transfer zone.

BIND version is hidden

Dns version is visible for sns-pb.isc.org with IP 192.5.4.1 : 9.9.7-P2.

MX IPs are in different class C

The IP of some SMTP servers are from the same C class.

DMARC is configured for domain

The Domain does not have DMARC.

Cookies are secure

The HttpOnly flag was not found.

The Secure flag was not found.

X-XSS-Protection header is present

The X-XSS-Protection header was not found.

Content Security Policy header is present

The Content-Security-Policy header was not found.

Content Type Options header is present

The X-Content-Type-Options header was not found.

DKIM is configured for domain

We do not detect any DKIM record for this domain.

DNS

Dns servers for ripe.net

ripe.net was detected as domain

Query informations

Server
l.root-servers.net
[ 199.7.83.42 ]
Duration
52 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
a.gtld-servers.net
[ 192.5.6.30 ]
Duration
28 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
b.gtld-servers.net
[ 192.33.14.30 ]
Duration
254 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
c.gtld-servers.net
[ 192.26.92.30 ]
Duration
28 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

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

Response

Query informations

Server
e.gtld-servers.net
[ 192.12.94.30 ]
Duration
37 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
f.gtld-servers.net
[ 192.35.51.30 ]
Duration
37 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
g.gtld-servers.net
[ 192.42.93.30 ]
Duration
36 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
h.gtld-servers.net
[ 192.54.112.30 ]
Duration
30 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
i.gtld-servers.net
[ 192.43.172.30 ]
Duration
31 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
j.gtld-servers.net
[ 192.48.79.30 ]
Duration
31 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
k.gtld-servers.net
[ 192.52.178.30 ]
Duration
134 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
l.gtld-servers.net
[ 192.41.162.30 ]
Duration
132 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
m.gtld-servers.net
[ 192.55.83.30 ]
Duration
132 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
a1.verisigndns.com
[ 209.112.113.33 ]
Duration
21 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
a2.verisigndns.com
[ 209.112.114.33 ]
Duration
21 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
a3.verisigndns.com
[ 69.36.145.33 ]
Duration
23 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
manus.authdns.ripe.net
[ 193.0.9.7 ]
Duration
23 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
ns4.apnic.net
[ 202.12.31.53 ]
Duration
274 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
sns-pb.isc.org
[ 192.5.4.1 ]
Duration
23 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
tinnie.arin.net
[ 199.212.0.53 ]
Duration
94 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Name servers

Mx Servers

A and AAAA fields

IPv4
193.0.6.139
TTL
21600 (6 hours)
IPv6
2001:67c:2e8:22:0:0:c100:68b
TTL
300 (5 minutes)

Text Fields

Type
Spf (TXT)
TTL
300 (5 minutes)
Name
@
Raw data
v=spf1 mx:ripe.net a:tsetse.ripe.net include:mail.zendesk.com ~all
A
MX
ALL
~all

Includes

mail.zendesk.com
v=spf1 ip4:192.161.144.0/20 ip4:185.12.80.0/22 ip4:96.46.150.192/27 ip4:174.137.46.0/24 ip4:188.172.128.0/20 ip4:216.198.0.0/18 ~all
Type
Txt
TTL
300 (5 minutes)
Value
google-site-verification=8brVsJvMeSvFzAIgUz-1bsBnkYURhzGe5DypAEmTPcI

SOA

From
tinnie.arin.net
Master server
manus.authdns.ripe.net
TTL
3600 (1 hour)
Contact
eIKH@ripe.net
Serial
1530100322
Refresh
3600 (1 hour)
Retry
600 (10 minutes)
Expire
864000 (1 week)
Minimum
300 (5 minutes)

Hosts found

Transfer zone is disable

manus.authdns.ripe.net [193.0.9.7] allows DNS transfer zone.

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

1.432s

BIND version is hidden

Dns version is visible for sns-pb.isc.org with IP 192.5.4.1 : 9.9.7-P2.

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

0.389s

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

All servers return success

Passed

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

0.007s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.007s

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

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

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

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

DNS servers IP are not private

Passed

It is strictly forbidden to have private IP in DNS

documentation

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

Domain

Whois

Registrar
Gandi SAS
Owner
-
Created at
25 Feb 1992
Changed at
02 Mar 2018
Expires at
26 Feb 2019

Reputation

Google Safe Browsing
Web of trust
91%
Blacklists
Virus Total
Domain
Registrar
Id
81
Name
Gandi SAS
Phone
-
Email
Url
-

Google Safe Browsing

Status

Web of Trust

Trust Rate
91%
Child Safe Rate
92%
Categories
Good site

Blacklists

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

Virus Total

Detection ratio
0 / 68

Scans

ADMINUSLabs
AegisLab WebGuard
AlienVault
Antiy-AVL
Avira
BADWARE.INFO
Baidu-International
BitDefender
Blueliv
CLEAN MX
Certly
Comodo Site Inspector
CyRadar
CyberCrime
DNS8
Dr.Web
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
FraudScore
FraudSense
G-Data
Google Safebrowsing
K7AntiVirus
Kaspersky
Malc0de Database
Malekal
Malware Domain Blocklist
MalwareDomainList
MalwarePatrol
Malwarebytes hpHosts
Malwared
Nucleon
OpenPhish
Opera
Phishtank
Quttera
Rising
SCUMWARE.org
SecureBrain
Spam404
Spamhaus
Sucuri SiteCheck
Tencent
ThreatHive
Trustwave
URLQuery
VX Vault
Virusdie External Site Scan
Web Security Guard
Webutation
Yandex Safebrowsing
ZCloudsec
ZDB Zeus
ZeroCERT
Zerofox
ZeusTracker
desenmascara.me
malwares.com URL checker
securolytics
zvelo
AutoShun
Netcraft
NotMining
PhishLabs
Sophos
StopBadware

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
mahimahi.ripe.net
IP
193.0.19.114
Banner
220 mahimahi.ripe.net ESMTP Thu, 28 Jun 2018 10:32:57 +0200
Name
molamola.ripe.net
IP
193.0.19.113
Banner
220 molamola.ripe.net ESMTP Thu, 28 Jun 2018 10:32:57 +0200

SPF

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

Raw data
v=spf1 mx:ripe.net a:tsetse.ripe.net include:mail.zendesk.com ~all
Name
mahimahi.ripe.net
IP
193.0.19.114
Banner
220 mahimahi.ripe.net ESMTP Thu, 28 Jun 2018 10:32:57 +0200
Starttls
yes
Mail size
50 MB
Expn
no
Vrfy
no

Smtp simulation

Connection to mahimahi.ripe.net ...
220 mahimahi.ripe.net ESMTP Thu, 28 Jun 2018 10:32:57 +0200
HELO nstools.fr
250 mahimahi.ripe.net Hello ns.tools [195.154.82.101]
EHLO nstools.fr
250-mahimahi.ripe.net Hello ns.tools [195.154.82.101]
250-SIZE 52428800
250-8BITMIME
250-ETRN
250-PIPELINING
250-STARTTLS
250 HELP
QUIT
221 mahimahi.ripe.net closing connection
Name
molamola.ripe.net
IP
193.0.19.113
Banner
220 molamola.ripe.net ESMTP Thu, 28 Jun 2018 10:32:57 +0200
Starttls
yes
Mail size
50 MB
Expn
no
Vrfy
no

Smtp simulation

Connection to molamola.ripe.net ...
220 molamola.ripe.net ESMTP Thu, 28 Jun 2018 10:32:57 +0200
HELO nstools.fr
250 molamola.ripe.net Hello ns.tools [195.154.82.101]
EHLO nstools.fr
250-molamola.ripe.net Hello ns.tools [195.154.82.101]
250-SIZE 52428800
250-8BITMIME
250-ETRN
250-PIPELINING
250-STARTTLS
250 HELP
QUIT
221 molamola.ripe.net closing connection

MX IPs are in different class C

The IP of some SMTP servers are from the same C class.

The class C of every IPs should be differents

0.000s

DMARC is configured for domain

The Domain does not have DMARC.

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

0.000s

DKIM is configured for domain

We do not detect any DKIM record for this domain.

It is strongly recommended to configure DKIM.

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.

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.

0.346s

MX servers accept abuse@ address

Passed

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

RFC

0.465s

MX servers accept postmaster@ address

Passed

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

RFC

0.195s

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

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

SMTP server number

Passed

Domain should have at least 2 SMTP servers according to the RFC

0.000s

MX IPs are differents

Passed

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

0.000s

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

Domain have only 1 DMARC record

Skipped

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

0.000s

DMARC version exist

Skipped

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

RFC

0.000s

DMARC version at first position

Skipped

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

Skipped

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

RFC

0.000s

DMARC "p" field is valid

Skipped

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

Skipped

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

Skipped

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

Skipped

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

Skipped

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

Skipped

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

Skipped

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

Skipped

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

Skipped

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://www.ripe.net/
Https
Title
RIPE Network Coordination Centre
Description
The RIPE NCC is one of five Regional Internet Registries (RIRs) providing Internet resource allocations, registration services and coordination activities that support the operation of the Internet globally.
First paragraph
We distribute Internet number resources to our members and provide tools to help them manage their allocations and assignments. More information about Manage IPs and ASNs We collect a wide range of Internet data and provide statistics and tools that our members and the wider Internet community can use for their own operations and analyses. More information about Analyse The smooth running of the Internet depends on the involvement of those who give their input on membership and policy issues. And there are many ways to get involved, online and in person. More information about Participate We support members and the RIPE community through several channels to offer timely and ...
Url
http://www.ripe.net/
Redirect to
https://www.ripe.net/
Redirect code
301 - moved permanently

Headers

  • Connection: close
  • Content-Length: 229
  • Content-Type: text/html; charset=iso-8859-1
  • Date: Thu, 28 Jun 2018 08:32:57 GMT
  • Location: https://www.ripe.net/
  • Server: Apache
Url
https://www.ripe.net/
Title
RIPE Network Coordination Centre
Description
The RIPE NCC is one of five Regional Internet Registries (RIRs) providing Internet resource allocations, registration services and coordination activities that support the operation of the Internet globally.
Response time
0.091 second
Server
apache
Powered by
Unknown
Encoding
utf-8
HSTS

Headers

  • Cache-control: private
  • Connection: close
  • Content-Language: en-gb
  • Content-Length: 88807
  • Content-Type: text/html;charset=utf-8
  • Date: Thu, 28 Jun 2018 08:32:57 GMT
  • Expires: Sat, 1 Jan 2000 00:00:00 GMT
  • Server: Apache
  • Set-Cookie: serverid=www-plone-2; path=/
  • X-Frame-Options: SAMEORIGIN
  • X-Ua-Compatible: IE=edge

Cookies are secure

The HttpOnly flag was not found.

The Secure flag was not found.

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

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

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

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

Domain have "AAAA" field

Passed

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

0.000s

Host "www" have "AAAA" field

Passed

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

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