| 1. General Results, most used to calculate the result |
| A | name "dnsforge.de" is domain, public suffix is ".de", top-level-domain is ".de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG", num .de-domains preloaded: 9496 (complete: 239099)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: dnsforge.de has 4 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.dnsforge.de has 4 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: dnsforge.de has 2 ipv4, 2 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.dnsforge.de has 2 ipv4, 2 ipv6 addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://dnsforge.de/ 176.9.1.117
|
| Good: Valid DANE - entry found: signed Data _443._tcp.dnsforge.de: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 9b9d50c0087334349adc6edcd58e9e384b2c933a7ac92cde3aacb42ca729b43c confirms the Certificate with the same value
|
| A | https://dnsforge.de/ 176.9.93.198
|
| Good: Valid DANE - entry found: signed Data _443._tcp.dnsforge.de: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 9b9d50c0087334349adc6edcd58e9e384b2c933a7ac92cde3aacb42ca729b43c confirms the Certificate with the same value
|
| A | https://dnsforge.de/ 2a01:4f8:141:316d::117
|
| Good: Valid DANE - entry found: signed Data _443._tcp.dnsforge.de: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 9b9d50c0087334349adc6edcd58e9e384b2c933a7ac92cde3aacb42ca729b43c confirms the Certificate with the same value
|
| A | https://dnsforge.de/ 2a01:4f8:151:34aa::198
|
| Good: Valid DANE - entry found: signed Data _443._tcp.dnsforge.de: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 9b9d50c0087334349adc6edcd58e9e384b2c933a7ac92cde3aacb42ca729b43c confirms the Certificate with the same value
|
| A | https://dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Good: Valid DANE - entry found: signed Data _443._tcp.dnsforge.de: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 9b9d50c0087334349adc6edcd58e9e384b2c933a7ac92cde3aacb42ca729b43c confirms the Certificate with the same value
|
| A | https://176.9.1.117/ 176.9.1.117
|
| Good: Valid DANE - entry found: signed Data _443._tcp.dnsforge.de: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 9b9d50c0087334349adc6edcd58e9e384b2c933a7ac92cde3aacb42ca729b43c confirms the Certificate with the same value
|
| A | https://dnsforge.de/login/
|
| Good: Valid DANE - entry found: signed Data _443._tcp.dnsforge.de: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 9b9d50c0087334349adc6edcd58e9e384b2c933a7ac92cde3aacb42ca729b43c confirms the Certificate with the same value
|
| A | https://176.9.93.198/ 176.9.93.198
|
| Good: Valid DANE - entry found: signed Data _443._tcp.dnsforge.de: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 9b9d50c0087334349adc6edcd58e9e384b2c933a7ac92cde3aacb42ca729b43c confirms the Certificate with the same value
|
| A | https://[2a01:04f8:0141:316d:0000:0000:0000:0117]/ 2a01:4f8:141:316d::117
|
| Good: Valid DANE - entry found: signed Data _443._tcp.dnsforge.de: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 9b9d50c0087334349adc6edcd58e9e384b2c933a7ac92cde3aacb42ca729b43c confirms the Certificate with the same value
|
| A | https://[2a01:04f8:0151:34aa:0000:0000:0000:0198]/ 2a01:4f8:151:34aa::198
|
| Good: Valid DANE - entry found: signed Data _443._tcp.dnsforge.de: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 9b9d50c0087334349adc6edcd58e9e384b2c933a7ac92cde3aacb42ca729b43c confirms the Certificate with the same value
|
| A | https://176.9.1.117/ 176.9.1.117
| https://dnsforge.de/login/
| Correct redirect https to https
|
| A | Good: destination is https
|
| A | Good - only one version with Http-Status 200
|
| A | Good: one preferred version: non-www is preferred
|
| A | Good: No cookie sent via http.
|
| A | Good: every cookie sent via https is marked as secure
|
| A | Good: Every cookie has a SameSite Attribute with a correct value Strict/Lax/None
|
| Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):4 complete Content-Type - header (13 urls)
|
| https://dnsforge.de/ 176.9.1.117
|
| Url with incomplete Content-Type - header - missing charset
|
| https://dnsforge.de/ 176.9.93.198
|
| Url with incomplete Content-Type - header - missing charset
|
| https://dnsforge.de/ 2a01:4f8:141:316d::117
|
| Url with incomplete Content-Type - header - missing charset
|
| https://dnsforge.de/ 2a01:4f8:151:34aa::198
|
| Url with incomplete Content-Type - header - missing charset
|
| http://dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.9.93.198
|
| Url with incomplete Content-Type - header - missing charset
|
| http://dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:151:34aa::198
|
| Url with incomplete Content-Type - header - missing charset
|
| https://dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| https://dnsforge.de/login/
|
| Url with incomplete Content-Type - header - missing charset
|
| https://[2a01:04f8:0141:316d:0000:0000:0000:0117]/ 2a01:4f8:141:316d::117
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://dnsforge.de/ 176.9.1.117
| https://dnsforge.de/
| Correct redirect http - https with the same domain name
|
| A | http://dnsforge.de/ 176.9.93.198
| https://dnsforge.de/
| Correct redirect http - https with the same domain name
|
| A | http://dnsforge.de/ 2a01:4f8:141:316d::117
| https://dnsforge.de/
| Correct redirect http - https with the same domain name
|
| A | http://dnsforge.de/ 2a01:4f8:151:34aa::198
| https://dnsforge.de/
| Correct redirect http - https with the same domain name
|
| B | https://www.dnsforge.de/ 176.9.1.117
|
| Missing HSTS-Header
|
| B | https://www.dnsforge.de/ 176.9.93.198
|
| Missing HSTS-Header
|
| B | https://www.dnsforge.de/ 2a01:4f8:141:316d::117
|
| Missing HSTS-Header
|
| B | https://www.dnsforge.de/ 2a01:4f8:151:34aa::198
|
| Missing HSTS-Header
|
| B | https://dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Missing HSTS-Header
|
| B | https://176.9.1.117/ 176.9.1.117
| max-age=31536000; includeSubDomains, max-age=31536000; includeSubdomains; preload
| Critical: HSTS-Header has Parse-Errors. Comma found, but Comma not allowed. Perhaps more then one HSTS-Header., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed.
|
| D | http://www.dnsforge.de/ 176.9.1.117
| http://dnsforge.de/
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| D | http://www.dnsforge.de/ 2a01:4f8:141:316d::117
| http://dnsforge.de/
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://www.dnsforge.de/ 176.9.93.198
| https://dnsforge.de/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://www.dnsforge.de/ 2a01:4f8:151:34aa::198
| https://dnsforge.de/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| K | http://www.dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.9.1.117, Status 404
| http://www.dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.9.93.198, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.9.1.117, Status 404
| http://www.dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:151:34aa::198, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.9.93.198, Status 301
| http://www.dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:141:316d::117, Status 404
| Configuration problem - different ip addresses with different status
|
| K | http://www.dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:141:316d::117, Status 404
| http://www.dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:151:34aa::198, Status 301
| Configuration problem - different ip addresses with different status
|
| M | https://dnsforge.de/login/
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://176.9.1.117/ 176.9.1.117
| https://dnsforge.de/login/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://176.9.93.198/ 176.9.93.198
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a01:04f8:0141:316d:0000:0000:0000:0117]/ 2a01:4f8:141:316d::117
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a01:04f8:0151:34aa:0000:0000:0000:0198]/ 2a01:4f8:151:34aa::198
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| Fatal: More then one ip address per domain name found, but checking all ip addresses different http status found.: Domain dnsforge.de, 4 ip addresses, 2 different http results.
|
| Fatal: More then one ip address per domain name found, but checking all ip addresses different http status found.: Domain www.dnsforge.de, 4 ip addresses, 2 different http results.
|
| Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain dnsforge.de, 4 ip addresses.
|
| Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.dnsforge.de, 4 ip addresses.
|
| 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.dnsforge.de
|
| 2. Header-Checks |
| A | dnsforge.de 176.9.1.117
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'none'; img-src 'self' https://piwik.dnsforge.de; style-src 'self'; script-src 'self' https://piwik.dnsforge.de; connect-src 'self'; font-src 'self'; base-uri 'none'; frame-ancestors 'none'; form-action 'self'; block-all-mixed-content
|
| B |
|
| Info: Header-Element is deprecated. block-all-mixed-content
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked.
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'.
|
| A |
|
| Good: form-action directive found. That reduces the risk sending data to unwanted domains. form-action is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: base-uri directive found. That limits the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: No object-src found, but the default-src used as fallback is defined and restricted.
|
| A |
|
| Good: script-src without 'unsafe-inline' and 'unsafe-eval' found. That's the recommended configuration.
|
| A |
|
| Good: script-src without * and a scheme found.
|
| A |
|
| Good: script-src without data: schema found. Why is this important? The data: schema allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: no-referrer
|
| 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: enforce, max-age=21600
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. enforce, max-age=21600
|
| A |
| Feature-Policy
| Ok: Header without syntax errors found: payment none
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. payment none
|
| 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
|
| A | dnsforge.de 176.9.93.198
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'none'; img-src 'self' https://piwik.dnsforge.de; style-src 'self'; script-src 'self' https://piwik.dnsforge.de; connect-src 'self'; font-src 'self'; base-uri 'none'; frame-ancestors 'none'; form-action 'self'; block-all-mixed-content
|
| B |
|
| Info: Header-Element is deprecated. block-all-mixed-content
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked.
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'.
|
| A |
|
| Good: form-action directive found. That reduces the risk sending data to unwanted domains. form-action is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: base-uri directive found. That limits the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: No object-src found, but the default-src used as fallback is defined and restricted.
|
| A |
|
| Good: script-src without 'unsafe-inline' and 'unsafe-eval' found. That's the recommended configuration.
|
| A |
|
| Good: script-src without * and a scheme found.
|
| A |
|
| Good: script-src without data: schema found. Why is this important? The data: schema allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: same-origin
|
| 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: enforce, max-age=21600
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. enforce, max-age=21600
|
| A |
| Feature-Policy
| Ok: Header without syntax errors found: payment none
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. payment none
|
| 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
|
| A | dnsforge.de 2a01:4f8:141:316d::117
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'none'; img-src 'self' https://piwik.dnsforge.de; style-src 'self'; script-src 'self' https://piwik.dnsforge.de; connect-src 'self'; font-src 'self'; base-uri 'none'; frame-ancestors 'none'; form-action 'self'; block-all-mixed-content
|
| B |
|
| Info: Header-Element is deprecated. block-all-mixed-content
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked.
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'.
|
| A |
|
| Good: form-action directive found. That reduces the risk sending data to unwanted domains. form-action is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: base-uri directive found. That limits the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: No object-src found, but the default-src used as fallback is defined and restricted.
|
| A |
|
| Good: script-src without 'unsafe-inline' and 'unsafe-eval' found. That's the recommended configuration.
|
| A |
|
| Good: script-src without * and a scheme found.
|
| A |
|
| Good: script-src without data: schema found. Why is this important? The data: schema allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: no-referrer
|
| 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: enforce, max-age=21600
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. enforce, max-age=21600
|
| A |
| Feature-Policy
| Ok: Header without syntax errors found: payment none
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. payment none
|
| 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
|
| A | dnsforge.de 2a01:4f8:151:34aa::198
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'none'; img-src 'self' https://piwik.dnsforge.de; style-src 'self'; script-src 'self' https://piwik.dnsforge.de; connect-src 'self'; font-src 'self'; base-uri 'none'; frame-ancestors 'none'; form-action 'self'; block-all-mixed-content
|
| B |
|
| Info: Header-Element is deprecated. block-all-mixed-content
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked.
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'.
|
| A |
|
| Good: form-action directive found. That reduces the risk sending data to unwanted domains. form-action is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: base-uri directive found. That limits the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: No object-src found, but the default-src used as fallback is defined and restricted.
|
| A |
|
| Good: script-src without 'unsafe-inline' and 'unsafe-eval' found. That's the recommended configuration.
|
| A |
|
| Good: script-src without * and a scheme found.
|
| A |
|
| Good: script-src without data: schema found. Why is this important? The data: schema allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: same-origin
|
| 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: enforce, max-age=21600
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. enforce, max-age=21600
|
| A |
| Feature-Policy
| Ok: Header without syntax errors found: payment none
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. payment none
|
| 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 | dnsforge.de 176.9.1.117
| Permissions-Policy
| Critical: Missing Header:
|
| F | dnsforge.de 176.9.93.198
| Permissions-Policy
| Critical: Missing Header:
|
| F | dnsforge.de 2a01:4f8:141:316d::117
| Permissions-Policy
| Critical: Missing Header:
|
| F | dnsforge.de 2a01:4f8:151:34aa::198
| Permissions-Policy
| Critical: Missing Header:
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
|
| A | Info:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| A | Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.cdom.de (176.9.1.103), ns3.cdom.de (176.9.93.183)
|
| A | Good (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: ns1.cdom.de, ns3.cdom.de, 2 Name Servers included in Delegation: ns1.cdom.de, ns3.cdom.de, 2 Name Servers included in 1 Zone definitions: ns1.cdom.de, ns3.cdom.de, 1 Name Servers listed in SOA.Primary: ns1.cdom.de.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.cdom.de.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.cdom.de.
|
| A | Good: Consistency 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. Ordered list of name servers: ns1.cdom.de, ns3.cdom.de
|
| A | Good: All Name Server Domain Names have a Public Suffix.
|
| A | Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
|
| A | Good: All Name Server ip addresses are public.
|
| A | Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 2 different Name Servers found
|
| Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: de
|
| Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: cdom.de
|
| Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: DE
|
| A | Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 176., 1 different subnets (first two Bytes): 176.9., 2 different subnets (first three Bytes): 176.9.1., 176.9.93.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2a01:, 1 different subnets (first two blocks): 2a01:04f8:, 2 different subnets (first three blocks): 2a01:04f8:0141:, 2a01:04f8:0151:, 2 different subnets (first four blocks): 2a01:04f8:0141:316d:, 2a01:04f8:0151:34aa:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 4 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 4 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
|
| 4. Content- and Performance-critical Checks |
| A | Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:141:316d::117, Status 404
| http://www.dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.9.93.198, Status 301
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:151:34aa::198, Status 301
| http://www.dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.9.1.117, Status 404
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| https://dnsforge.de/ 176.9.93.198
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://dnsforge.de/ 2a01:4f8:151:34aa::198
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://dnsforge.de/ 176.9.1.117
|
| 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://dnsforge.de/ 176.9.93.198
|
| 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://dnsforge.de/ 2a01:4f8:141:316d::117
|
| 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://dnsforge.de/ 2a01:4f8:151:34aa::198
|
| 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://[2a01:04f8:0141:316d:0000:0000:0000:0117]/ 2a01:4f8:141:316d::117
|
| 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 %.
|
| A | Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
|
| A | Good: Some script Elements (type text/javascript) with a src-Attribute have a defer / async - Attribute. So loading and executing these JavaScripts doesn't block parsing and rendering the Html-Output.
|
| https://dnsforge.de/ 176.9.1.117
|
| Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 3 script elements without defer/async.
|
| https://dnsforge.de/ 176.9.93.198
|
| Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 3 script elements without defer/async.
|
| https://dnsforge.de/ 2a01:4f8:141:316d::117
|
| Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 3 script elements without defer/async.
|
| https://dnsforge.de/ 2a01:4f8:151:34aa::198
|
| Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 3 script elements without defer/async.
|
| https://[2a01:04f8:0141:316d:0000:0000:0000:0117]/ 2a01:4f8:141:316d::117
|
| Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 3 script elements without defer/async.
|
| Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 8 external CSS / JavaScript files without GZip found - 12 with GZip, 20 complete
|
| A | Good: All images with internal compression not compressed. Some Images (.png, .jpg, .jpeg, .webp, .gif) are already compressed, so an additional compression isn't helpful. 32 images (type image/png, image/jpg) found without additional GZip. Not required because these images are already compressed
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 5 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 20 with Cache-Control long enough, 25 complete.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 9 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), 36 with Cache-Control long enough, 45 complete.
|
| A | Good: Some checked attribute values are enclosed in quotation marks (" or ').: 255 Html-Elements checked, 250 without problems.
|
| I | Wrong: Attribute values found, not enclosed in quotation marks (" or ').: 5 Html-Elements with attributes and missing enclosed quotation marks found. 5 wrong attributes.
|
| A | Good: Some img-elements have a valid alt-attribute.: 45 img-elements found, 25 img-elements with correct alt-attributes (defined, not an empty value).
|
| Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 20 img-elements without alt-attribute, 0 img-elements with empty alt-attribute 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
|
| https://176.9.1.117/ 176.9.1.117
| Strict-Transport-Security: max-age=31536000; includeSubDomains, max-age=31536000; includeSubdomains; preload
| Parse Error - Header can't be parsed
|
| https://dnsforge.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 3.190 seconds
| Warning: 404 needs more then one second
|
| https://dnsforge.de/login/
| 3.140 seconds
| Warning: 404 needs more then one second
|
| A | Info: Different Server-Headers found
|
| A | Duration: 282650 milliseconds, 282.650 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)