| 1. General Results, most used to calculate the result |
| A | name "dksdroner.ga" is domain, public suffix is "ga", top-level-domain-type is "country-code", Country is Gabon, tld-manager is "Agence Nationale des Infrastructures Numériques et des Fréquences (ANINF)"
|
| A | Good: All ip addresses are public addresses
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (6 urls)
|
| http://dksdroner.ga/ 185.27.134.108
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.dksdroner.ga/ 185.27.134.108
|
| Url with incomplete Content-Type - header - missing charset
|
| https://dksdroner.ga/ 185.27.134.108
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.dksdroner.ga/ 185.27.134.108
|
| Url with incomplete Content-Type - header - missing charset
|
| http://dksdroner.ga/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.108
|
| Url with incomplete Content-Type - header - missing charset
|
| http://www.dksdroner.ga/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.108
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://dksdroner.ga/ 185.27.134.108
|
| Missing HSTS-Header
|
| B | https://www.dksdroner.ga/ 185.27.134.108
|
| Missing HSTS-Header
|
| 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.
|
| 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.
|
| J | https://dksdroner.ga/ 185.27.134.108
|
| Fatal: Script /aes.js found. Looks like your hoster has a Bot-Check-Detection, so Letsencrypt can't check your http-validation file.
|
| J | https://www.dksdroner.ga/ 185.27.134.108
|
| Fatal: Script /aes.js found. Looks like your hoster has a Bot-Check-Detection, so Letsencrypt can't check your http-validation file.
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| 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 |
| http://dksdroner.ga/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.108
|
| 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://www.dksdroner.ga/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.108
|
| 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.
|
| 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: 28013 milliseconds, 28.013 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)