| 1. General Results, most used to calculate the result |
| A | name "hive.fogelfrei.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 94787 (complete: 245733)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: hive.fogelfrei.com 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: hive.fogelfrei.com has no ipv6 address.
|
| 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 | 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):0 complete Content-Type - header (1 urls)
|
| http://hive.fogelfrei.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 84.149.132.236
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://hive.fogelfrei.com/ 84.149.132.236
|
| Missing HSTS-Header
|
| C | Error - no version with Http-Status 200
|
| D | http://hive.fogelfrei.com/ 84.149.132.236
| http://hive.fogelfrei.com/web/
| 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.
|
| H | Fatal error: No https - result with http-status 200, no encryption
|
| R | http://hive.fogelfrei.com/ 84.149.132.236
| http://hive.fogelfrei.com/web/
| Redirect to not existing domain
|
| R | https://hive.fogelfrei.com/ 84.149.132.236
| https://hive.fogelfrei.com/web/
| Redirect to not existing domain
|
| 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 hive.fogelfrei.com, 1 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.hive.fogelfrei.com
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| U |
|
| No https result with http status 2** or 4** (standard-check) found, no header checked.
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
|
| A | Info:: 13 Queries complete, 11 with IPv6, 2 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.
|
| 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.angus.ns.servercow.de (2a00:f820:417:153::, 5.1.76.153)
|
| Ok (4 - 8):: An average of 4.3 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 3 different Name Servers found: angus.ns.servercow.de, dexter.ns.servercow.net, galloway.ns.servercow.com, 3 Name Servers included in Delegation: angus.ns.servercow.de, dexter.ns.servercow.net, galloway.ns.servercow.com, 3 Name Servers included in 1 Zone definitions: angus.ns.servercow.de, dexter.ns.servercow.net, galloway.ns.servercow.com, 1 Name Servers listed in SOA.Primary: angus.ns.servercow.de.
|
| A | Good: Only one SOA.Primary Name Server found.: angus.ns.servercow.de.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: angus.ns.servercow.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 | Info: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 45., 5., 94., 3 different subnets (first two Bytes): 45.85., 5.1., 94.130., 3 different subnets (first three Bytes): 45.85.48., 5.1.76., 94.130.42.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 3 different subnets (first block): 2a00:, 2a01:, 2a0e:, 3 different subnets (first two blocks): 2a00:f820:, 2a01:04f8:, 2a0e:b680:, 3 different subnets (first three blocks): 2a00:f820:0417:, 2a01:04f8:fff2:, 2a0e:b680:000c:, 3 different subnets (first four blocks): 2a00:f820:0417:0153:, 2a01:04f8:fff2:0020:, 2a0e:b680:000c:0253:
|
| A | Excellent: Every Name Server IPv6-address starts with an unique Hex-block
|
| A | Good: Nameserver supports TCP connections: 6 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 6 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: angus.ns.servercow.de: 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.
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
|
| 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 | 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: 96574 milliseconds, 96.574 seconds
|