| 1. General Results, most used to calculate the result |
| A | name "wbde2.wienerberger.de" is subdomain, public suffix is ".de", top-level-domain is ".de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG", num .de-domains preloaded: 10860 (complete: 270180)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: wbde2.wienerberger.de 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: wbde2.wienerberger.de has no ipv6 address.
|
| A | DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
|
| A | Good: destination is https
|
| A | Good - only one version with Http-Status 200
|
| A | Good: one preferred version: non-www is preferred
|
| 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://wbde2.wienerberger.de/ 137.135.175.15
|
| Url with incomplete Content-Type - header - missing charset
|
| https://137.135.175.15/ 137.135.175.15
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://wbde2.wienerberger.de/ 137.135.175.15
|
| Missing HSTS-Header
|
| N | https://wbde2.wienerberger.de/ 137.135.175.15
|
| Error - Certificate isn't trusted, RemoteCertificateChainErrors
|
| N | https://137.135.175.15/ 137.135.175.15
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| 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 wbde2.wienerberger.de, 1 ip addresses, 1 different http results.
|
| 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.wbde2.wienerberger.de
|
| 2. Header-Checks |
| F | wbde2.wienerberger.de 137.135.175.15
| Content-Security-Policy
| Critical: Missing Header:
|
| F | wbde2.wienerberger.de 137.135.175.15
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | wbde2.wienerberger.de 137.135.175.15
| Referrer-Policy
| Critical: Missing Header:
|
| F | wbde2.wienerberger.de 137.135.175.15
| Permissions-Policy
| Critical: Missing Header:
|
| B | wbde2.wienerberger.de 137.135.175.15
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | wbde2.wienerberger.de 137.135.175.15
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | wbde2.wienerberger.de 137.135.175.15
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 4 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 5 Name Servers.
|
| A | Info:: 4 Queries complete, 4 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.lemarit.de (81.209.198.1), ns1.lemarit.net (207.158.52.87), ns2.lemarit.de (192.174.68.101, 2001:67c:1bc::101), ns2.lemarit.net (176.97.158.101, 2001:67c:10b8::101), ns3.lemarit.de (178.248.243.66)
|
| A | Good (1 - 3.0):: An average of 0.8 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 5 different Name Servers found: ns1.lemarit.de, ns1.lemarit.net, ns2.lemarit.de, ns2.lemarit.net, ns3.lemarit.de, 5 Name Servers included in Delegation: ns1.lemarit.de, ns1.lemarit.net, ns2.lemarit.de, ns2.lemarit.net, ns3.lemarit.de, 5 Name Servers included in 1 Zone definitions: ns1.lemarit.de, ns1.lemarit.net, ns2.lemarit.de, ns2.lemarit.net, ns3.lemarit.de, 1 Name Servers listed in SOA.Primary: ns1.lemarit.de.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.lemarit.de.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.lemarit.de.
|
| 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: ns1.lemarit.de, ns1.lemarit.net, ns2.lemarit.de, ns2.lemarit.net, ns3.lemarit.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 | Good: Minimal 2 different name servers (public suffix and public ip address) found: 5 different Name Servers found
|
| A | Good: Some Name Servers have IPv6 addresses: 2 Name Servers with IPv6 found (3 Name Servers without IPv6)
|
| A | Good: Name servers with different Top Level Domains / Public Suffix List entries found: 5 Name Servers, 2 Top Level Domains: de, net
|
| A | Good: Name Servers with different domain names found.: 2 different Domains found
|
| A | Good: Name servers with different Country locations found: 5 Name Servers, 3 Countries: AT, DE, US
|
| A | Info: Ipv4-Subnet-list: 5 Name Servers, 5 different subnets (first Byte): 176., 178., 192., 207., 81., 5 different subnets (first two Bytes): 176.97., 178.248., 192.174., 207.158., 81.209., 5 different subnets (first three Bytes): 176.97.158., 178.248.243., 192.174.68., 207.158.52., 81.209.198.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:067c:, 2 different subnets (first three blocks): 2001:067c:01bc:, 2001:067c:10b8:, 2 different subnets (first four blocks): 2001:067c:01bc:0000:, 2001:067c:10b8:0000:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 1 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 1 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns1.lemarit.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.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.lemarit.de / 81.209.198.1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: ok. 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 |
| http://wbde2.wienerberger.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 137.135.175.15
|
| 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.
|
| A | Good: No https + http status 200 with inline CSS / JavaScript found
|
| https://wbde2.wienerberger.de/ 137.135.175.15
|
| 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://137.135.175.15/ 137.135.175.15
|
| 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 images with internal compression not compressed. Some Images (.png, .jpg, .jpeg, .webp, .gif) are already compressed, so an additional compression isn't helpful. 1 images (type image/png, image/jpg, image/jpeg, image/webp, image/gif) found without additional Compression. Not required because these images are already compressed
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 image files without Cache-Control-Header, 1 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 1 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: All img-elements have a valid alt-attribute.: 2 img-elements found.
|
| 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: 157457 milliseconds, 157.457 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)