| 1. General Results, most used to calculate the result |
| A | name "goldharvest.my" is domain, public suffix is "my", top-level-domain-type is "country-code", Country is Malaysia, tld-manager is "MYNIC Berhad"
|
| A | Good: All ip addresses are public addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| 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):8 complete Content-Type - header (16 urls)
|
| http://goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.28.0.206
|
| Url with incomplete Content-Type - header - missing charset
|
| http://goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.28.1.206
|
| Url with incomplete Content-Type - header - missing charset
|
| http://goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3030::681c:1ce
|
| Url with incomplete Content-Type - header - missing charset
|
| http://goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3033::681c:ce
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.28.0.206
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.28.1.206
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3030::681c:1ce
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3033::681c:ce
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://goldharvest.my/ 104.28.0.206
|
| Missing HSTS-Header
|
| B | https://goldharvest.my/ 104.28.1.206
|
| Missing HSTS-Header
|
| B | https://goldharvest.my/ 2606:4700:3030::681c:1ce
|
| Missing HSTS-Header
|
| B | https://goldharvest.my/ 2606:4700:3033::681c:ce
|
| Missing HSTS-Header
|
| B | https://www.goldharvest.my/ 104.28.0.206
|
| Missing HSTS-Header
|
| B | https://www.goldharvest.my/ 104.28.1.206
|
| Missing HSTS-Header
|
| B | https://www.goldharvest.my/ 2606:4700:3030::681c:1ce
|
| Missing HSTS-Header
|
| B | https://www.goldharvest.my/ 2606:4700:3033::681c:ce
|
| Missing HSTS-Header
|
| 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.
|
| F | https://goldharvest.my/ 104.28.0.206
| http://goldharvest.my/
| Wrong redirect https - http - never redirect https to http
|
| F | https://goldharvest.my/ 104.28.1.206
| http://goldharvest.my/
| Wrong redirect https - http - never redirect https to http
|
| F | https://goldharvest.my/ 2606:4700:3030::681c:1ce
| http://goldharvest.my/
| Wrong redirect https - http - never redirect https to http
|
| F | https://goldharvest.my/ 2606:4700:3033::681c:ce
| http://goldharvest.my/
| Wrong redirect https - http - never redirect https to http
|
| F | https://www.goldharvest.my/ 104.28.0.206
| http://www.goldharvest.my/
| Wrong redirect https - http - never redirect https to http
|
| F | https://www.goldharvest.my/ 104.28.1.206
| http://www.goldharvest.my/
| Wrong redirect https - http - never redirect https to http
|
| F | https://www.goldharvest.my/ 2606:4700:3030::681c:1ce
| http://www.goldharvest.my/
| Wrong redirect https - http - never redirect https to http
|
| F | https://www.goldharvest.my/ 2606:4700:3033::681c:ce
| http://www.goldharvest.my/
| Wrong redirect https - http - never redirect https to http
|
| H | Fatal error: No https - result with http-status 200, no encryption
|
| H | Fatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| 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: gail.ns.cloudflare.com,kanye.ns.cloudflare.com
|
| 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
|
| 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 | http://goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.28.0.206
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | http://goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.28.1.206
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | http://goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3030::681c:1ce
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | http://goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3033::681c:ce
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | http://www.goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.28.0.206
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | http://www.goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.28.1.206
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | http://www.goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3030::681c:1ce
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | http://www.goldharvest.my/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3033::681c:ce
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| 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 | Duration: 302050 milliseconds, 302.050 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)