| 1. General Results, most used to calculate the result |
| A | name "oi.run.place" is subdomain, public suffix is ".place", top-level-domain is ".place", top-level-domain-type is "generic", tld-manager is "Binky Moon, LLC", num .place-domains preloaded: 18 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: oi.run.place has only one ip address.
|
| Warning: Only one ip address found: www.oi.run.place has only one ip address.
|
| Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: oi.run.place has no ipv6 address.
|
| Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: www.oi.run.place has no ipv6 address.
|
| A | Good: destination is https
|
| A | Good: No cookie sent via http.
|
| A | Good: every cookie sent via https is marked as secure
|
| 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):1 complete Content-Type - header (6 urls)
|
| https://oi.run.place/ 204.44.87.69
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.oi.run.place/ 204.44.87.69
|
| Url with incomplete Content-Type - header - missing charset
|
| https://oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| https://204.44.87.69/ 204.44.87.69
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://oi.run.place/ 204.44.87.69
| https://oi.run.place/
| Correct redirect http - https with the same domain name
|
| A | http://www.oi.run.place/ 204.44.87.69
| https://www.oi.run.place/
| Correct redirect http - https with the same domain name
|
| B | https://www.oi.run.place/ 64.182.209.151
|
| Missing HSTS-Header
|
| B | https://64.182.209.151/ 64.182.209.151
| JSESSIONID=5DCF244CC98317B5C36B27CB828F8689; Path=/; 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.
|
| C | Error - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
|
| C | Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
|
| D | http://www.oi.run.place/ 64.182.209.151
| http://oi.run.place/
| 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.oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 64.182.209.151
| http://oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-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.
|
| I | https://oi.run.place/ 204.44.87.69
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| I | https://www.oi.run.place/ 204.44.87.69
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| I | https://oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| I | https://www.oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| K | http://oi.run.place/ 139.99.66.103, Status -14
| http://oi.run.place/ 204.44.87.69, Status 301
| Configuration problem - different ip addresses with different status
|
| K | https://oi.run.place/ 139.99.66.103, Status -14
| https://oi.run.place/ 204.44.87.69, Status 200
| Configuration problem - different ip addresses with different status
|
| K | http://oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 139.99.66.103, Status -14
| http://oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 204.44.87.69, Status 301
| Configuration problem - different ip addresses with different status
|
| K | https://www.oi.run.place/ 64.182.209.151, Status 301
| https://www.oi.run.place/ 204.44.87.69, Status 200
| Configuration problem - different ip addresses with different status
|
| N | https://www.oi.run.place/ 64.182.209.151
| https://oi.run.place/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://204.44.87.69/ 204.44.87.69
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://64.182.209.151/ 64.182.209.151
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| O | 64.182.209.151 / 64.182.209.151 / 443
|
| Old connection: Ssl3 is insecure and must be disabled.
|
| O | www.oi.run.place / 64.182.209.151 / 443
|
| Old connection: Ssl3 is insecure and must be disabled.
|
| O | www.oi.run.place / 64.182.209.151 / 443
| ECDHE-RSA-RC4-SHA
| Old connection: Insecure Cipher Suite found. Such active Cipher Suites allow downgrades. Remove all insecure Cipher Suites
|
| O | www.oi.run.place / 64.182.209.151 / 443
| RC4-SHA
| Old connection: Insecure Cipher Suite found. Such active Cipher Suites allow downgrades. Remove all insecure Cipher Suites
|
| O | www.oi.run.place / 64.182.209.151 / 443
|
| Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 12 Cipher Suites without Forward Secrecy found
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns1.dnsexit.com / 31.14.40.88: NXDOMAIN
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns10.dnsexit.com / 204.12.239.138: Timeout
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns12.dnsexit.com / 69.30.210.154: Refused
|
| 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 www.oi.run.place, 1 ip addresses, 1 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 oi.run.place, 1 ip addresses.
|
| A | Good: _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Domainname: run.place
|
| B | Bad: _mta-sts TXT found, but invalid
|
| 2. Header-Checks |
| A | oi.run.place 204.44.87.69
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: origin
|
| 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 |
| 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 | www.oi.run.place 204.44.87.69
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: origin
|
| 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 |
| 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 | oi.run.place 204.44.87.69
| Content-Security-Policy
| Critical: Missing Header:
|
| F | oi.run.place 204.44.87.69
| Permissions-Policy
| Critical: Missing Header:
|
| B | oi.run.place 204.44.87.69
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | oi.run.place 204.44.87.69
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | oi.run.place 204.44.87.69
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.oi.run.place 204.44.87.69
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.oi.run.place 204.44.87.69
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.oi.run.place 204.44.87.69
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.oi.run.place 204.44.87.69
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.oi.run.place 204.44.87.69
| Cross-Origin-Resource-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 4 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.dnsexit.com (31.14.40.88), ns2.dnsexit.com (216.244.76.186), ns3.dnsexit.com (204.12.192.106), ns4.dnsexit.com (107.150.58.186)
|
| A | Good (1 - 3.0):: An average of 0.5 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 5 different Name Servers found: ns1.dnsexit.com, ns10.dnsexit.com, ns11.dnsexit.com, ns12.dnsexit.com, ns13.dnsexit.com, 1 Name Servers included in Delegation: ns1.dnsexit.com, ns2.dnsexit.com, ns3.dnsexit.com, ns4.dnsexit.com, 1 Name Servers included in 2 Zone definitions: ns1.dnsexit.com, ns1.dnsexit.com, ns2.dnsexit.com, ns3.dnsexit.com, ns4.dnsexit.com, 1 Name Servers listed in SOA.Primary: ns1.dnsexit.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.dnsexit.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.dnsexit.com.
|
| X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns11.dnsexit.com (69.30.249.130): Delegation: ns10.dnsexit.com, ns11.dnsexit.com, ns12.dnsexit.com, ns13.dnsexit.com, Zone: ns10.dnsexit.com, ns11.dnsexit.com, ns12.dnsexit.com. Name Servers defined in Delegation, missing in Zone: ns13.dnsexit.com.
|
| X | Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns13.dnsexit.com (216.244.93.66): Delegation: ns10.dnsexit.com, ns11.dnsexit.com, ns12.dnsexit.com, ns13.dnsexit.com, Zone: ns10.dnsexit.com, ns11.dnsexit.com, ns12.dnsexit.com. Name Servers defined in Delegation, missing in Zone: ns13.dnsexit.com.
|
|
|
| A | Good: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
|
| Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 4 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.: 4 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: dnsexit.com
|
| A | Good: Name servers with different Country locations found: 4 Name Servers, 2 Countries: RO, US
|
| A | Info: Ipv4-Subnet-list: 4 Name Servers, 4 different subnets (first Byte): 107., 204., 216., 31., 4 different subnets (first two Bytes): 107.150., 204.12., 216.244., 31.14., 4 different subnets (first three Bytes): 107.150.58., 204.12.192., 216.244.76., 31.14.40.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Good: Nameserver supports Echo Capitalization: 4 good Nameserver
|
| X | Nameserver Timeout checking Echo Capitalization: ns10.dnsexit.com / 204.12.239.138
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
|
| X | Nameserver Timeout checking EDNS512: ns10.dnsexit.com / 204.12.239.138
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns1.dnsexit.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: ns10.dnsexit.com / 204.12.239.138: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns11.dnsexit.com / 69.30.249.130: 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: ns12.dnsexit.com / 69.30.210.154: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: v2n1.nic.place: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (FRA4). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| 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 |
| https://oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| https://www.oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 139.99.66.103
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| https://oi.run.place/ 204.44.87.69
|
| 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://www.oi.run.place/ 204.44.87.69
|
| 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://oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| 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://www.oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| 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://oi.run.place/ 204.44.87.69
|
| 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://www.oi.run.place/ 204.44.87.69
|
| 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://oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-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://www.oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-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://204.44.87.69/ 204.44.87.69
|
| 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://64.182.209.151/ 64.182.209.151
|
| 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://oi.run.place/ 204.44.87.69
|
| 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://www.oi.run.place/ 204.44.87.69
|
| 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://oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-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://www.oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-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://204.44.87.69/ 204.44.87.69
|
| 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://64.182.209.151/ 64.182.209.151
|
| 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://64.182.209.151/ 64.182.209.151
|
| 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.
|
| 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://oi.run.place/ 204.44.87.69
|
| 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.: 2 script elements without defer/async.
|
| https://www.oi.run.place/ 204.44.87.69
|
| 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.: 2 script elements without defer/async.
|
| https://oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-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.: 2 script elements without defer/async.
|
| https://www.oi.run.place/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-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.: 2 script elements without defer/async.
|
| https://204.44.87.69/ 204.44.87.69
|
| 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.: 2 script elements without defer/async.
|
| https://64.182.209.151/ 64.182.209.151
|
| 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 Compression found - 4 with Compression, 12 complete
|
| 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. 12 external CSS / JavaScript files with long Cache-Control max-age found
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Info: No img element found, no alt attribute checked
|
| A | Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
|
| A | Info: Different Server-Headers found
|
| A | Duration: 486614 milliseconds, 486.614 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)