| 1. General Results, most used to calculate the result |
| A | name "return-path.dk" is domain, public suffix is ".dk", top-level-domain is ".dk", top-level-domain-type is "country-code", Country is Denmark, tld-manager is "Dansk Internet Forum", num .dk-domains preloaded: 994 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: return-path.dk has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: return-path.dk has 1 ipv4, 1 ipv6 addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
|
| A | https://return-path.dk/ 89.150.133.221
|
| Good: Valid DANE - entry found: signed Data _443._tcp.return-path.dk: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 148e0642e8f6a3c70f70b20ed05643c729ffa7c7b091c87598531af8c0cbc897 confirms the Certificate with the same value
|
| A | https://return-path.dk/ 89.150.133.221
|
| Good: Valid DANE - entry found: signed Data _443._tcp.return-path.dk: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: b0292ae545978e0fbb98abbd94c861605e5b18bb32ed523f50d5b7b5c71d47bc confirms the Certificate with the same value
|
| A | https://return-path.dk/ 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| Good: Valid DANE - entry found: signed Data _443._tcp.return-path.dk: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: b0292ae545978e0fbb98abbd94c861605e5b18bb32ed523f50d5b7b5c71d47bc confirms the Certificate with the same value
|
| A | https://return-path.dk/ 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| Good: Valid DANE - entry found: signed Data _443._tcp.return-path.dk: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 148e0642e8f6a3c70f70b20ed05643c729ffa7c7b091c87598531af8c0cbc897 confirms the Certificate with the same value
|
| A | https://return-path.dk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Good: Valid DANE - entry found: signed Data _443._tcp.return-path.dk: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: b0292ae545978e0fbb98abbd94c861605e5b18bb32ed523f50d5b7b5c71d47bc confirms the Certificate with the same value
|
| A | https://return-path.dk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Good: Valid DANE - entry found: signed Data _443._tcp.return-path.dk: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 148e0642e8f6a3c70f70b20ed05643c729ffa7c7b091c87598531af8c0cbc897 confirms the Certificate with the same value
|
| A | https://89.150.133.221/ 89.150.133.221
|
| Good: Valid DANE - entry found: signed Data _443._tcp.return-path.dk: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: b0292ae545978e0fbb98abbd94c861605e5b18bb32ed523f50d5b7b5c71d47bc confirms the Certificate with the same value
|
| A | https://89.150.133.221/ 89.150.133.221
|
| Good: Valid DANE - entry found: signed Data _443._tcp.return-path.dk: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 148e0642e8f6a3c70f70b20ed05643c729ffa7c7b091c87598531af8c0cbc897 confirms the Certificate with the same value
|
| A | https://[2a05:f6c7:7613:0000:0011:32ff:fe25:7642]/ 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| Good: Valid DANE - entry found: signed Data _443._tcp.return-path.dk: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 148e0642e8f6a3c70f70b20ed05643c729ffa7c7b091c87598531af8c0cbc897 confirms the Certificate with the same value
|
| A | https://[2a05:f6c7:7613:0000:0011:32ff:fe25:7642]/ 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| Good: Valid DANE - entry found: signed Data _443._tcp.return-path.dk: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: b0292ae545978e0fbb98abbd94c861605e5b18bb32ed523f50d5b7b5c71d47bc confirms the Certificate with the same value
|
| A | https://mta-sts.return-path.dk/.well-known/mta-sts.txt 89.150.133.221
|
| Good: Valid DANE - entry found: signed Data _443._tcp.return-path.dk: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 148e0642e8f6a3c70f70b20ed05643c729ffa7c7b091c87598531af8c0cbc897 confirms the Certificate with the same value
|
| A | https://mta-sts.return-path.dk/.well-known/mta-sts.txt 89.150.133.221
|
| Good: Valid DANE - entry found: signed Data _443._tcp.return-path.dk: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: b0292ae545978e0fbb98abbd94c861605e5b18bb32ed523f50d5b7b5c71d47bc confirms the Certificate with the same value
|
| A | https://mta-sts.return-path.dk/.well-known/mta-sts.txt 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| Good: Valid DANE - entry found: signed Data _443._tcp.return-path.dk: CertUsage 2 (DANE-TA, Trust anchor assertion), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: b0292ae545978e0fbb98abbd94c861605e5b18bb32ed523f50d5b7b5c71d47bc confirms the Certificate with the same value
|
| A | https://mta-sts.return-path.dk/.well-known/mta-sts.txt 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| Good: Valid DANE - entry found: signed Data _443._tcp.return-path.dk: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 148e0642e8f6a3c70f70b20ed05643c729ffa7c7b091c87598531af8c0cbc897 confirms the Certificate with the same value
|
| A | https://89.150.133.221/ 89.150.133.221
| https://return-path.dk/
| Correct redirect https to https
|
| A | https://89.150.133.221/ 89.150.133.221
| https://return-path.dk/
| Correct redirect https to https
|
| A | https://[2a05:f6c7:7613:0000:0011:32ff:fe25:7642]/ 2a05:f6c7:7613:0:11:32ff:fe25:7642
| https://return-path.dk/
| Correct redirect https to https
|
| A | https://[2a05:f6c7:7613:0000:0011:32ff:fe25:7642]/ 2a05:f6c7:7613:0:11:32ff:fe25:7642
| https://return-path.dk/
| 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.
|
| 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):1 complete Content-Type - header (5 urls)
|
| https://return-path.dk/ 89.150.133.221
|
| Url with incomplete Content-Type - header - missing charset
|
| https://return-path.dk/ 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| Url with incomplete Content-Type - header - missing charset
|
| https://mta-sts.return-path.dk/.well-known/mta-sts.txt 89.150.133.221
|
| Url with incomplete Content-Type - header - missing charset
|
| https://mta-sts.return-path.dk/.well-known/mta-sts.txt 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://return-path.dk/ 89.150.133.221
| https://return-path.dk/
| Correct redirect http - https with the same domain name
|
| A | http://return-path.dk/ 2a05:f6c7:7613:0:11:32ff:fe25:7642
| https://return-path.dk/
| Correct redirect http - https with the same domain name
|
| N | https://89.150.133.221/ 89.150.133.221
| https://return-path.dk/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a05:f6c7:7613:0000:0011:32ff:fe25:7642]/ 2a05:f6c7:7613:0:11:32ff:fe25:7642
| https://return-path.dk/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| A | Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain return-path.dk, 2 ip addresses.
|
| 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 return-path.dk, 2 ip addresses, 1 different http results.
|
| A | Good: _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Domainname: _mta-sts.return-path.dk
|
| A | Good: _mta-sts TXT record is valid.
|
| A | Good: Subdomain mta-sts found: Subdomain-name: mta-sts.return-path.dk, ip : 89.150.133.221
|
| A | Good: Subdomain mta-sts found: Subdomain-name: mta-sts.return-path.dk, ip : 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| A | Good: Certificate of subdomain is valid. mta-sts.return-path.dk, ip : 89.150.133.221
|
| A | Good: Certificate of subdomain is valid. mta-sts.return-path.dk, ip : 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| A | Good: /.well-known/mta-sts.txt with http status 200 found. Complete path: https://mta-sts.return-path.dk/.well-known/mta-sts.txt - ip : 89.150.133.221
|
| A | Good: /.well-known/mta-sts.txt with http status 200 found. Complete path: https://mta-sts.return-path.dk/.well-known/mta-sts.txt - ip : 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| A | Good: mta-sts.txt has the required names "version", "mode", "max_age". mta-sts.return-path.dk, ip : 89.150.133.221
|
| A | Good: mta-sts.txt has the required names "version", "mode", "max_age". mta-sts.return-path.dk, ip : 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| A | Good: Minimal one mx definition found. mta-sts.return-path.dk, ip : 89.150.133.221
|
| A | Good: Minimal one mx definition found. mta-sts.return-path.dk, ip : 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| A | Excellent: Complete and valid MTA-STS found!
|
| 2. Header-Checks |
| A | return-path.dk 89.150.133.221
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'none';
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked. img-src, script-src, style-src
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'. img-src, script-src, style-src
|
| 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.
|
| C |
|
| Info: default-src and some other fetch directives have the same list of values. Remove the other fetch directive, default-src is used as fallback. Directives to remove: img-src, script-src, style-src
|
| A |
| 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=(), microphone=(), camera=()
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: DENY
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. DENY. 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 |
| Cross-Origin-Opener-Policy
| Ok: Header without syntax errors found: same-origin
|
| A |
| Cross-Origin-Resource-Policy
| Ok: Header without syntax errors found: same-origin
|
| A | return-path.dk 2a05:f6c7:7613:0:11:32ff:fe25:7642
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'none';
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked. img-src, script-src, style-src
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'. img-src, script-src, style-src
|
| 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.
|
| C |
|
| Info: default-src and some other fetch directives have the same list of values. Remove the other fetch directive, default-src is used as fallback. Directives to remove: img-src, script-src, style-src
|
| A |
| 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=(), microphone=(), camera=()
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: DENY
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. DENY. 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 |
| Cross-Origin-Opener-Policy
| Ok: Header without syntax errors found: same-origin
|
| A |
| Cross-Origin-Resource-Policy
| Ok: Header without syntax errors found: same-origin
|
| B | return-path.dk 89.150.133.221
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | return-path.dk 2a05:f6c7:7613:0:11:32ff:fe25:7642
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 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.simply.com (2a02:2339:1:15c::4562:4562, 91.197.248.78), ns2.simply.com (185.25.141.15, 2a02:2339:4006:101::4562:4562), ns3.simply.com (91.197.248.79)
|
| A | Good (1 - 3.0):: An average of 0.7 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 3 different Name Servers found: ns1.simply.com, ns2.simply.com, ns3.simply.com, 3 Name Servers included in Delegation: ns1.simply.com, ns2.simply.com, ns3.simply.com, 3 Name Servers included in 1 Zone definitions: ns1.simply.com, ns2.simply.com, ns3.simply.com, 1 Name Servers listed in SOA.Primary: ns1.simply.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.simply.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.simply.com.
|
| 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.simply.com, ns2.simply.com, ns3.simply.com
|
| 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: 3 different Name Servers found
|
| A | Good: Some Name Servers have IPv6 addresses: 2 Name Servers with IPv6 found (1 Name Servers without IPv6)
|
| 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.: 3 Name Servers, 1 Top Level Domain: com
|
| 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: simply.com
|
| Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: DK
|
| A | Info: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 185., 91., 2 different subnets (first two Bytes): 185.25., 91.197., 2 different subnets (first three Bytes): 185.25.141., 91.197.248.
|
| 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): 2a02:, 1 different subnets (first two blocks): 2a02:2339:, 2 different subnets (first three blocks): 2a02:2339:0001:, 2a02:2339:4006:, 2 different subnets (first four blocks): 2a02:2339:0001:015c:, 2a02:2339:4006:0101:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 5 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 5 good Nameserver
|
| X | Nameserver Timeout checking EDNS512: ns2.simply.com / 185.25.141.15
|
| Nameserver doesn't pass all EDNS-Checks: h.nic.dk: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.simply.com: 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: ns1.simply.com / 91.197.248.78: OP100: fatal timeout. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (ns1.simply.com). COOKIE: ok. CLIENTSUBNET: ok.
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
|
| Warning: Unknown CAA found: letsencrypt isn't defined. Unknown entry. May be wrong written, may be not longer valid. May be a missing entry in this tool.
|
| 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.
|
| https://return-path.dk/ 89.150.133.221
|
| Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
|
| https://return-path.dk/ 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
|
| https://mta-sts.return-path.dk/.well-known/mta-sts.txt 89.150.133.221
|
| 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://mta-sts.return-path.dk/.well-known/mta-sts.txt 2a05:f6c7:7613:0:11:32ff:fe25:7642
|
| 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: Svg-Images greater 1024 Bytes without internal compression are found. Svg is an Xml-Application, so Compression is required to reduce the size of the file. 4 images (type image/svg+xml, image/x-icon, image/vnd.microsoft.icon) found without compression.
|
| Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 2 external CSS / JavaScript files without Compression found - 0 with Compression, 2 complete
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 2 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), 0 with Cache-Control long enough, 2 complete.
|
| 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
|
| https://return-path.dk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 2.843 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 805193 milliseconds, 805.193 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)