| 1. General Results, most used to calculate the result |
| A | name "lotswerk.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: 11085 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: lotswerk.de has 2 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.lotswerk.de has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: lotswerk.de has 1 ipv4, 1 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.lotswerk.de has 1 ipv4, 1 ipv6 addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://159.195.20.252/login.php
| https://159.195.20.252/login_up.php
| Correct redirect https to https
|
| A | https://159.195.20.252/ 159.195.20.252
| https://159.195.20.252/login.php
| Correct redirect https to https
|
| A | https://[2a0a:4cc0:00c1:324c:a42d:7aff:fe7d:d4c1]/ 2a0a:4cc0:c1:324c:a42d:7aff:fe7d:d4c1
| https://glp-1forum.de/
| 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
|
| 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 (5 urls)
|
| https://lotswerk.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://lotswerk.de/ 159.195.20.252
| https://lotswerk.de/
| Correct redirect http - https with the same domain name
|
| A | http://lotswerk.de/ 2a0a:4cc0:c1:324c:a42d:7aff:fe7d:d4c1
| https://lotswerk.de/
| Correct redirect http - https with the same domain name
|
| B | https://www.lotswerk.de/ 159.195.20.252
|
| Missing HSTS-Header
|
| B | https://www.lotswerk.de/ 2a0a:4cc0:c1:324c:a42d:7aff:fe7d:d4c1
|
| Missing HSTS-Header
|
| B | https://lotswerk.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Missing HSTS-Header
|
| B | https://[2a0a:4cc0:00c1:324c:a42d:7aff:fe7d:d4c1]/ 2a0a:4cc0:c1:324c:a42d:7aff:fe7d:d4c1
| wsc_9a1b8e_user_session=587a3876e0bbe469581a7428888107179af35ac8e8f5a97ae086327ad9aaca0b-AUOBOieBLhUtd80v8u4RIsNrXkpSvg%3D%3D; path=/; domain=glp-1forum.de; secure; HttpOnly
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| B | https://glp-1forum.de/
| wsc_9a1b8e_user_session=ca367be8c354fce4f10f45abcb9c54ec6535d81722fd84d43cfa58da4f350cca-AYiXyJqdP8PNQ1%2F%2B4Nrb7BgEh7lWvg%3D%3D; path=/; domain=glp-1forum.de; secure; HttpOnly
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
| E | http://www.lotswerk.de/ 159.195.20.252
| https://lotswerk.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.lotswerk.de/ 2a0a:4cc0:c1:324c:a42d:7aff:fe7d:d4c1
| https://lotswerk.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.
|
| N | https://159.195.20.252/ 159.195.20.252
| https://159.195.20.252/login.php
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a0a:4cc0:00c1:324c:a42d:7aff:fe7d:d4c1]/ 2a0a:4cc0:c1:324c:a42d:7aff:fe7d:d4c1
| https://glp-1forum.de/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.lotswerk.de:25
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | lotswerk.de:25
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | lotswerk.de:8443
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | lotswerk.de:8443
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.lotswerk.de:8443
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.lotswerk.de:8443
|
| 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 lotswerk.de, 2 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.lotswerk.de, 2 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 lotswerk.de, 2 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.lotswerk.de, 2 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.lotswerk.de
|
| 2. Header-Checks |
| A | lotswerk.de 159.195.20.252
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'self'; script-src 'self' 'nonce-BYByn689vGDUNCdSK97dUA=='; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked. connect-src, font-src
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'. connect-src, font-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: object-src only with 'none' or 'self' found, no scheme, no other urls. That blocks object / embed / applet - elements.
|
| 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 |
|
| Ok: Nonce found.
|
| 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: connect-src, font-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 |
| 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 | lotswerk.de 2a0a:4cc0:c1:324c:a42d:7aff:fe7d:d4c1
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'self'; script-src 'self' 'nonce-5Vswi807inNo3Vl4nq8fPA=='; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked. connect-src, font-src
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'. connect-src, font-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: object-src only with 'none' or 'self' found, no scheme, no other urls. That blocks object / embed / applet - elements.
|
| 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 |
|
| Ok: Nonce found.
|
| 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: connect-src, font-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 |
| 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.
|
| F | lotswerk.de 159.195.20.252
| Permissions-Policy
| Critical: Missing Header:
|
| B | lotswerk.de 159.195.20.252
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | lotswerk.de 159.195.20.252
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | lotswerk.de 159.195.20.252
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | lotswerk.de 2a0a:4cc0:c1:324c:a42d:7aff:fe7d:d4c1
| Permissions-Policy
| Critical: Missing Header:
|
| B | lotswerk.de 2a0a:4cc0:c1:324c:a42d:7aff:fe7d:d4c1
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | lotswerk.de 2a0a:4cc0:c1:324c:a42d:7aff:fe7d:d4c1
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | lotswerk.de 2a0a:4cc0:c1:324c:a42d:7aff:fe7d:d4c1
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| A |
|
| Good: Different combinations of domain names and ip addresses checked, Content-Security-Policy - Header with a nonce declaration sent: Every combination domain + ip with an own, unique nonce.
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 23 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 5 Name Servers.
|
| A | Info:: 23 Queries complete, 22 with IPv6, 0 with IPv4.
|
| Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
|
| Ok (4 - 8):: An average of 4.6 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 5 different Name Servers found: netcup.fifthns.com, netcup.firstns.cc, netcup.fourthns.systems, netcup.secondns.at, netcup.thirdns.de, 5 Name Servers included in Delegation: netcup.fifthns.com, netcup.firstns.cc, netcup.fourthns.systems, netcup.secondns.at, netcup.thirdns.de, 5 Name Servers included in 1 Zone definitions: netcup.fifthns.com, netcup.firstns.cc, netcup.fourthns.systems, netcup.secondns.at, netcup.thirdns.de, 1 Name Servers listed in SOA.Primary: netcup.firstns.cc.
|
| A | Good: Only one SOA.Primary Name Server found.: netcup.firstns.cc.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: netcup.firstns.cc.
|
| 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: netcup.fifthns.com, netcup.firstns.cc, netcup.fourthns.systems, netcup.secondns.at, netcup.thirdns.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: 5 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 5 different Name Servers found
|
| A | Good: Name servers with different Top Level Domains / Public Suffix List entries found: 5 Name Servers, 5 Top Level Domains: cc, at, de, com, systems
|
| A | Good: Name Servers with different domain names found.: 5 different Domains found
|
| A | Good: Name servers with different Country locations found: 5 Name Servers, 4 Countries: AT, DE, FR, NL
|
| A | Info: Ipv4-Subnet-list: 5 Name Servers, 5 different subnets (first Byte): 188., 213., 217., 37., 45., 5 different subnets (first two Bytes): 188.172., 213.227., 217.146., 37.252., 45.84., 5 different subnets (first three Bytes): 188.172.219., 213.227.168., 217.146.22., 37.252.225., 45.84.253.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 5 Name Servers with IPv6, 1 different subnets (first block): 2a00:, 1 different subnets (first two blocks): 2a00:11c0:, 5 different subnets (first three blocks): 2a00:11c0:0002:, 2a00:11c0:000e:, 2a00:11c0:0063:, 2a00:11c0:0066:, 2a00:11c0:0082:, 5 different subnets (first four blocks): 2a00:11c0:0002:0998:, 2a00:11c0:000e:ffff:, 2a00:11c0:0063:0350:, 2a00:11c0:0066:0000:, 2a00:11c0:0082:0359:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Info: Nameserver mit different domain names found. May be a problem with DNS-Updates
|
| A | Good: Nameserver supports TCP connections: 10 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 10 good Nameserver
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: netcup.fifthns.com
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: netcup.firstns.cc
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: netcup.fourthns.systems
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: netcup.thirdns.de
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 10 good Nameserver
|
| 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 |
| 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.
|
| A | Good: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://lotswerk.de/ 159.195.20.252
|
| 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://lotswerk.de/ 2a0a:4cc0:c1:324c:a42d:7aff:fe7d:d4c1
|
| 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://glp-1forum.de/
|
| 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://159.195.20.252/login_up.php
|
| 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://lotswerk.de/ 159.195.20.252
|
| 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://lotswerk.de/ 2a0a:4cc0:c1:324c:a42d:7aff:fe7d:d4c1
|
| 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://glp-1forum.de/
|
| 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://159.195.20.252/login_up.php
|
| 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.
|
| A | Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
|
| https://lotswerk.de/ 159.195.20.252
|
| 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.: 1 script elements without defer/async.
|
| https://lotswerk.de/ 2a0a:4cc0:c1:324c:a42d:7aff:fe7d:d4c1
|
| 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.: 1 script elements without defer/async.
|
| https://glp-1forum.de/
|
| 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.: 7 script elements without defer/async.
|
| https://159.195.20.252/login_up.php
|
| 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.: 7 script elements without defer/async.
|
| A | Good: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 6 external CSS / JavaScript files found
|
| A | Good: All CSS / JavaScript files are sent with a long Cache-Control header (minimum 7 days). So the browser can re-use these files, no download is required. 4 external CSS / JavaScript files with long Cache-Control max-age found
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: Some img-elements have a valid alt-attribute.: 23 img-elements found, 1 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.: 0 img-elements without alt-attribute, 22 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://lotswerk.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 2.174 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 506587 milliseconds, 506.587 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)