| 1. General Results, most used to calculate the result |
| A | name "impfzentren.bayern" is domain, public suffix is ".bayern", top-level-domain is ".bayern", top-level-domain-type is "generic", tld-manager is "Bayern Connect GmbH", num .bayern-domains preloaded: 7 (complete: 142558)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: impfzentren.bayern has only one ip address.
|
| Warning: Only one ip address found: www.impfzentren.bayern 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: impfzentren.bayern 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.impfzentren.bayern has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://149.97.65.20/ 149.97.65.20
| https://impfzentren.bayern/
| 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 https has a Strict Transport Security Header
|
| A | Good: HSTS max-age is long enough, 63072000 seconds = 730 days
|
| 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 (2 urls)
|
| https://impfzentren.bayern/ 149.97.65.20
|
| Url with incomplete Content-Type - header - missing charset
|
| https://impfzentren.bayern/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://impfzentren.bayern/ 149.97.65.20
| https://impfzentren.bayern/
| Correct redirect http - https with the same domain name
|
| A | http://www.impfzentren.bayern/ 149.97.65.20
| https://www.impfzentren.bayern/
| Correct redirect http - https with the same domain name
|
| N | https://149.97.65.20/ 149.97.65.20
| https://impfzentren.bayern/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| 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 impfzentren.bayern, 1 ip addresses, 1 different http results.
|
| 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.impfzentren.bayern, 1 ip addresses, 1 different http results.
|
| 2. Header-Checks |
| 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.a.ns14.net (62.116.131.31, 62.116.159.231), b.ns14.net (2001:8d8:580:401:217:160:113:231, 2001:8d8:580:401:217:160:113:32, 217.160.113.231, 217.160.113.32), c.ns14.net (195.34.161.195, 2a01:130:2000:118:195:34:161:195, 2a01:130:2000:118:89:146:248:231, 89.146.248.231), d.ns14.net (2607:f1c0:849:fe00:74:208:254:254, 74.208.254.254)
|
| 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:: 4 different Name Servers found: a.ns14.net, b.ns14.net, c.ns14.net, d.ns14.net, 4 Name Servers included in Delegation: a.ns14.net, b.ns14.net, c.ns14.net, d.ns14.net, 4 Name Servers included in 1 Zone definitions: a.ns14.net, b.ns14.net, c.ns14.net, d.ns14.net, 1 Name Servers listed in SOA.Primary: a.ns14.net.
|
| A | Good: Only one SOA.Primary Name Server found.: a.ns14.net.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: a.ns14.net.
|
| 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: a.ns14.net, b.ns14.net, c.ns14.net, d.ns14.net
|
| 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: 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: net
|
| 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: ns14.net
|
| A | Good: Name servers with different Country locations found: 4 Name Servers, 2 Countries: DE, US
|
| A | Info: Ipv4-Subnet-list: 7 Name Servers, 5 different subnets (first Byte): 195., 217., 62., 74., 89., 5 different subnets (first two Bytes): 195.34., 217.160., 62.116., 74.208., 89.146., 6 different subnets (first three Bytes): 195.34.161., 217.160.113., 62.116.131., 62.116.159., 74.208.254., 89.146.248.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 5 Name Servers with IPv6, 3 different subnets (first block): 2001:, 2607:, 2a01:, 3 different subnets (first two blocks): 2001:08d8:, 2607:f1c0:, 2a01:0130:, 3 different subnets (first three blocks): 2001:08d8:0580:, 2607:f1c0:0849:, 2a01:0130:2000:, 3 different subnets (first four blocks): 2001:08d8:0580:0401:, 2607:f1c0:0849:fe00:, 2a01:0130:2000:0118:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 12 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 12 good Nameserver
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: a.ns14.net
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 12 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: dns1.nic.bayern: 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: dns2.nic.bayern: 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: dns3.nic.bayern: 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: dns4.nic.bayern: 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.
|
| 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://impfzentren.bayern/ 149.97.65.20
|
| 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://impfzentren.bayern/ 149.97.65.20
|
| 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.
|
| 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
|
| https://impfzentren.bayern/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 2.287 seconds
| Warning: 404 needs more then one second
|
| A | Info: Different Server-Headers found
|
| A | Duration: 103350 milliseconds, 103.350 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)