| 1. General Results, most used to calculate the result |
A | name "env-7436529.zrh2.cloudsig.ma" is subdomain, public suffix is ".ma", top-level-domain is ".ma", top-level-domain-type is "country-code", Country is Morocco, tld-manager is "Agence Nationale de Réglementation des Télécommunications (ANRT)", num .ma-domains preloaded: 70 (complete: 240622)
|
A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: env-7436529.zrh2.cloudsig.ma has only one ip address.
|
| Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: env-7436529.zrh2.cloudsig.ma has no ipv6 address.
|
A | DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
|
A | Good: one preferred version: non-www is preferred
|
A | Good: No cookie sent via http.
|
A | Good: every https has a Strict Transport Security Header
|
A | Good: HSTS has includeSubdomains - directive
|
| HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
|
A | Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
B | Warning: HSTS max-age is too short - minimum 31536000 = 365 days required, 5 seconds = 0 days found
|
H | Fatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
|
N | https://env-7436529.zrh2.cloudsig.ma/ 178.22.66.115
|
| Error - Certificate isn't trusted, RemoteCertificateChainErrors
|
N | https://178.22.66.115/ 178.22.66.115
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
X | Fatal error: Nameserver isn't defined or has timeout
|
X | Fatal error: Nameserver doesn't support TCP connection: zrh2.cloudsig.ma: Timeout
|
| Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain env-7436529.zrh2.cloudsig.ma, 1 ip addresses, 1 different http results.
|
B | No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.env-7436529.zrh2.cloudsig.ma
|
| 2. Header-Checks |
A | env-7436529.zrh2.cloudsig.ma 178.22.66.115
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
A |
| Referrer-Policy
| Ok: Header without syntax errors found: strict-origin-when-cross-origin
|
A |
| Permissions-Policy
| Ok: Header without syntax errors found: geolocation=(self), payment=(self)
|
A |
| X-Frame-Options
| Ok: Header without syntax errors found: SAMEORIGIN
|
B |
|
| Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls.
|
A |
| Expect-CT
| Ok: Header without syntax errors found: max-age=3600, enforce
|
B |
|
| Info: Header is deprecated. May not longer work in modern browsers. max-age=3600, enforce
|
A |
| X-Xss-Protection
| Ok: Header without syntax errors found: 1; mode=block;
|
B |
|
| Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block;
|
F | env-7436529.zrh2.cloudsig.ma 178.22.66.115
| Content-Security-Policy
| Critical: Missing Header:
|
| 3. DNS- and NameServer - Checks |
A | Info:: 18 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 0 Name Servers.
|
A | Info:: 18 Queries complete, 18 with IPv6, 0 with IPv4.
|
A | Good: All DNS Queries done via IPv6.
|
A | Info:: 6 different Name Servers found: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma, ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma, zrh2.cloudsig.ma, 5 Name Servers included in Delegation: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma, ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma, 2 Name Servers included in 2 Zone definitions: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma, 1 Name Servers listed in SOA.Primary: zrh2.cloudsig.ma.
|
A | Good: Only one SOA.Primary Name Server found.: zrh2.cloudsig.ma.
|
| Error: SOA.Primary Name Server not included in the delegation set.: zrh2.cloudsig.ma.
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.zrh2.cloudsig.ma (178.22.67.63): Delegation: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma, ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma, Zone: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma. Name Servers defined in Delegation, missing in Zone: ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma.
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.zrh2.cloudsig.ma (178.22.67.97): Delegation: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma, ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma, Zone: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma. Name Servers defined in Delegation, missing in Zone: ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma.
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.zrh2.cloudsig.ma (178.22.67.63): Delegation: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma, ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma, Zone: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma. Name Servers defined in Delegation, missing in Zone: ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma.
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.zrh2.cloudsig.ma (178.22.67.97): Delegation: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma, ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma, Zone: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma. Name Servers defined in Delegation, missing in Zone: ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma.
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns4.zrh2.cloudsig.ma (178.22.67.63): Delegation: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma, ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma, Zone: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma. Name Servers defined in Delegation, missing in Zone: ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma.
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns4.zrh2.cloudsig.ma (178.22.67.97): Delegation: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma, ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma, Zone: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma. Name Servers defined in Delegation, missing in Zone: ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma.
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns5.zrh2.cloudsig.ma (178.22.67.63): Delegation: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma, ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma, Zone: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma. Name Servers defined in Delegation, missing in Zone: ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma.
|
X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns5.zrh2.cloudsig.ma (178.22.67.97): Delegation: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma, ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma, Zone: ns1.zrh2.cloudsig.ma, ns2.zrh2.cloudsig.ma. Name Servers defined in Delegation, missing in Zone: ns3.zrh2.cloudsig.ma, ns4.zrh2.cloudsig.ma, ns5.zrh2.cloudsig.ma.
|
A | Good: All Name Server Domain Names have a Public Suffix.
|
| Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1
|
|
|
A | Info: Ipv4-Subnet-list: 8 Name Servers, 1 different subnets (first Byte): 178., 1 different subnets (first two Bytes): 178.22., 1 different subnets (first three Bytes): 178.22.67.
|
X | Fatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.:
|
| Nameserver doesn't pass all EDNS-Checks: zrh2.cloudsig.ma: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
|
| Nameserver doesn't pass all EDNS-Checks: zrh2.cloudsig.ma: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: zrh2.cloudsig.ma: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
|
A | Good: All SOA have the same Serial Number
|
| Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
|
| 4. Content- and Performance-critical Checks |
| http://env-7436529.zrh2.cloudsig.ma/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.22.66.115
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
A | Good: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://env-7436529.zrh2.cloudsig.ma/ 178.22.66.115
|
| Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
|
| https://178.22.66.115/ 178.22.66.115
|
| Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
|
A | Good: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
|
| https://env-7436529.zrh2.cloudsig.ma/ 178.22.66.115
|
| Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
|
| https://178.22.66.115/ 178.22.66.115
|
| Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 4 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 4 complete.
|
A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
A | Good: All img-elements have a valid alt-attribute.: 4 img-elements found.
|
A | Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
|
A | Duration: 178944 milliseconds, 178.944 seconds
|