Analysis report on domain: gip-mds.fr favicon

gip-mds.fr
Generated on
20 Apr 2021 15:11
Duration of the analysis
14.0s
Share

Score 62%
C
DNS
C
DOMAIN
A
MAIL
C
WEB
C

Resume

DNS servers IP are in different class C

IPs have the same C class.

BIND version is hidden

Dns version is visible for ns500013.as16211.net with IP 62.193.51.141 : 9.10.3-P4-Debian.

MX servers accept abuse@ address

mail1.gip-mds.fr [176.57.36.220] does not accept email to abuse@gip-mds.fr.

mail2.gip-mds.fr [176.57.36.229] does not accept email to abuse@gip-mds.fr.

MX servers accept postmaster@ address

mail1.gip-mds.fr [176.57.36.220] does not accept email to postmaster@gip-mds.fr.

mail2.gip-mds.fr [176.57.36.229] does not accept email to postmaster@gip-mds.fr.

MX IPs are in different class C

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

SPF is configured for domain

The Domain does not have SPF.

DMARC is configured for domain

The Domain does not have DMARC.

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

Web server version is hidden

Version 2.4.6 has been found.

Web application technology is hidden

Server is powered by: PHP/7.3.1

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.

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 gip-mds.fr

gip-mds.fr was detected as domain

Query informations

Server
e.root-servers.net
[ 192.203.230.10 ]
Duration
7 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
d.nic.fr
[ 194.0.9.1 ]
Duration
25 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
e.ext.nic.fr
[ 193.176.144.22 ]
Duration
18 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
f.ext.nic.fr
[ 194.146.106.46 ]
Duration
13 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
g.ext.nic.fr
[ 194.0.36.1 ]
Duration
3 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns500013.as16211.net
[ 62.193.51.141 ]
Duration
4 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Query informations

Server
ns500014.as16211.net
[ 62.193.51.142 ]
Duration
5 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Name servers

Mx Servers

Name
mail1.gip-mds.fr
IPs
Priority
5
TTL
14400 (4 hours)
Name
mail2.gip-mds.fr
IPs
Priority
10
TTL
14400 (4 hours)

A and AAAA fields

IPv4
92.43.248.119
TTL
14400 (4 hours )

Text Fields

Type
Txt
TTL
14400 (4 hours)
Value
MS=ms37587772

SOA

From
ns500014.as16211.net
Master server
ns500013.as16211.net
TTL
14400 (4 hours)
Contact
eIKH@stella-telecom.fr
Serial
2020112001
Refresh
86400 (1 day)
Retry
7200 (2 hours)
Expire
3600000 (1 month)
Minimum
172800 (2 days)
Your domain is not protected by DNSSEC DNSSEC Definition

DNS servers IP are in different class C

IPs have the same C class.

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

BIND version is hidden

Dns version is visible for ns500013.as16211.net with IP 62.193.51.141 : 9.10.3-P4-Debian.

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

1.006s

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

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

2.009s

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

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

10.020s

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.

10.011s

Domain

Whois

Registrar
STELLA TELECOM SAS
Owner
MODERNISATION DES DECLARATIONS SOCIALES
Created at
22 May 2000
Changed at
24 Sep 2020
Expires at
24 Sep 2021

Reputation

Google Safe Browsing
Web of trust
Blacklists
Virus Total
Domain
Whois server
whois.afnic.fr
Created at
22 May 2000
Changed at
24 Sep 2020
Expires at
24 Sep 2021
Name servers
Registrar
Id
-
Name
STELLA TELECOM SAS
Phone
-
Email
fYJ6gw==@stella-telecom.fr
Url
https://www.stella-telecom.fr/
Owner
Name
MODERNISATION DES DECLARATIONS SOCIALES
Organization
-
Address
4-14, rue Ferrus
City
75014 Paris
Zip code
-
Country
FR
Phone
+33 1 58 10 47 00
Email
d311@gip-mds.fr
Admin
Name
Elisabeth Humber-Bottin
Organization
GIP-MDS
Address
4-14, rue Ferrus
City
75014 Paris
Zip code
-
Country
FR
Phone
+33 1 58 10 47 00
Email
h3d4@gip-mds.fr
Tech
Name
STELLA-NET
Organization
Stella Telecom
Address
245, route des Lucioles
City
06560 Valbonne
Zip code
-
Country
FR
Phone
+33 4 89 12 21 22
Email
fYJ6gw==@stella-telecom.fr

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

Mail servers

Name
mail1.gip-mds.fr
IP
176.57.36.220
Banner
220 mail1.gip-mds.fr ESMTP Sophos Email Appliance v4.5.3.2
Name
mail2.gip-mds.fr
IP
176.57.36.229
Banner
220 mail2.gip-mds.fr ESMTP Sophos Email Appliance v4.5.3.2

SPF

There is no SPF record for this domain

DKIM

Your domain has no DKIM selector found

Do you have one to analyse ?


Name
mail1.gip-mds.fr
IP
176.57.36.220
Banner
220 mail1.gip-mds.fr ESMTP Sophos Email Appliance v4.5.3.2
Starttls
yes
Dane
no
Mail size
20 MB
Expn
no
Vrfy
no

Smtp simulation

Connection to mail1.gip-mds.fr ...
220 mail1.gip-mds.fr ESMTP Sophos Email Appliance v4.5.3.2
HELO domain.com
250 mail1.gip-mds.fr
EHLO domain.com
250-mail1.gip-mds.fr
250-PIPELINING
250-SIZE 20971520
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
QUIT
221 2.0.0 Bye
Name
mail2.gip-mds.fr
IP
176.57.36.229
Banner
220 mail2.gip-mds.fr ESMTP Sophos Email Appliance v4.5.3.2
Starttls
yes
Dane
no
Mail size
20 MB
Expn
no
Vrfy
no

Smtp simulation

Connection to mail2.gip-mds.fr ...
220 mail2.gip-mds.fr ESMTP Sophos Email Appliance v4.5.3.2
HELO nstools.fr
250 mail2.gip-mds.fr
EHLO nstools.fr
250-mail2.gip-mds.fr
250-PIPELINING
250-SIZE 20971520
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
QUIT
221 2.0.0 Bye

Autodiscover not configured

MX servers accept abuse@ address

mail1.gip-mds.fr [176.57.36.220] does not accept email to abuse@gip-mds.fr.

mail2.gip-mds.fr [176.57.36.229] does not accept email to abuse@gip-mds.fr.

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

RFC

0.056s

MX servers accept postmaster@ address

mail1.gip-mds.fr [176.57.36.220] does not accept email to postmaster@gip-mds.fr.

mail2.gip-mds.fr [176.57.36.229] does not accept email to postmaster@gip-mds.fr.

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

RFC

0.056s

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

SPF is configured for domain

The Domain does not have SPF.

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

SPF definition

0.000s

DMARC is configured for domain

The Domain does not have DMARC.

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

DMARC definition

0.000s

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

0.209s

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

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

SPF record is TXT type

Skipped

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

Skipped

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

0.000s

SPF version exists

Skipped

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

RFC

0.000s

SPF version at first position

Skipped

SPF has to start with version's tag.

RFC

0.000s

SPF "all" exists

Skipped

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

Skipped

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

Skipped

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

RFC

0.000s

SPF haven't PTR

Skipped

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

RFC

0.000s

SPF "Redirect" at last position

Skipped

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

Skipped

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

Skipped

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

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.gip-mds.fr/
Https
Title
Accueil - GIP MDS
Description
First paragraph
Nous sommes un service public numérique. Au GIP-MDS, nous œuvrons pour simplifier la vie des entreprises. Nous digitalisons les formalités déclaratives des entreprises grâce à une plateforme et des composants industriels au service de l’intérêt général, de la collecte à l’usage des données sociales. Vous pensez que l’innovation doit se mettre au service de la collectivité ? Que la digitalisation a vocation à être utile à chacun et profitable à tous ? Nous aussi.   Découvrez les procédures en cours, les données essentielles et les consultations à venir des marchés publics du GIP-MDS. Nos sites : net-entreprises.fr | dsn-info.fr RGPD & CNIL | Mentions Lég...
Url
http://www.gip-mds.fr/
Redirect to
https://www.gip-mds.fr//
Redirect code
302 - found

Headers

  • Connection: close
  • Content-Length: 208
  • Content-Type: text/html; charset=iso-8859-1
  • Date: Wed, 17 Mar 2021 09:32:24 GMT
  • Location: https://www.gip-mds.fr//
  • Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.3.1
Url
https://www.gip-mds.fr/
Title
Accueil - GIP MDS
Description
Response time
0.487 second
Server
apache (version 2.4.6)
Powered by
php (version 7.3.1)
Encoding
utf-8
HSTS

Headers

  • Cache-Control: private, must-revalidate
  • Connection: close
  • Content-Type: text/html; charset=UTF-8
  • Date: Wed, 17 Mar 2021 09:32:24 GMT
  • Link: ; rel="https://api.w.org/", ; rel="alternate"; type="application/json", ; rel=shortlink
  • Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.3.1
  • Transfer-Encoding: chunked
  • X-Powered-By: PHP/7.3.1

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

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

0.000s

Web server version is hidden

Version 2.4.6 has been found.

To avoid giving details to malicious people, the version of the server should not be visible.

0.000s

Web application technology is hidden

Server is powered by: PHP/7.3.1

To avoid giving details to malicious people, the technology that supports the application should not be visible.

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

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