| 1. General Results, most used to calculate the result |
| A | name "lehina.com" is domain, 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: 108094 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: lehina.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: lehina.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: one preferred version: non-www is preferred
|
| 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 (3 urls)
|
| http://lehina.com/ 176.96.92.90
|
| Url with incomplete Content-Type - header - missing charset
|
| https://lehina.com/ 176.96.92.90
|
| Url with incomplete Content-Type - header - missing charset
|
| http://lehina.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.96.92.90
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://lehina.com/ 176.96.92.90
|
| Missing HSTS-Header
|
| 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.
|
| 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 lehina.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.lehina.com
|
| 2. Header-Checks |
| F | lehina.com 176.96.92.90
| Content-Security-Policy
| Critical: Missing Header:
|
| F | lehina.com 176.96.92.90
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | lehina.com 176.96.92.90
| Referrer-Policy
| Critical: Missing Header:
|
| F | lehina.com 176.96.92.90
| Permissions-Policy
| Critical: Missing Header:
|
| B | lehina.com 176.96.92.90
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | lehina.com 176.96.92.90
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | lehina.com 176.96.92.90
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
|
| A | Info:: 16 Queries complete, 16 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 4 different Name Servers found: ns-1230.awsdns-25.org, ns-1634.awsdns-12.co.uk, ns-382.awsdns-47.com, ns-577.awsdns-08.net, 4 Name Servers included in Delegation: ns-1230.awsdns-25.org, ns-1634.awsdns-12.co.uk, ns-382.awsdns-47.com, ns-577.awsdns-08.net, 4 Name Servers included in 1 Zone definitions: ns-1230.awsdns-25.org, ns-1634.awsdns-12.co.uk, ns-382.awsdns-47.com, ns-577.awsdns-08.net, 1 Name Servers listed in SOA.Primary: ns-1230.awsdns-25.org.
|
| A | Good: Only one SOA.Primary Name Server found.: ns-1230.awsdns-25.org.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns-1230.awsdns-25.org.
|
| 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: ns-1230.awsdns-25.org, ns-1634.awsdns-12.co.uk, ns-382.awsdns-47.com, ns-577.awsdns-08.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
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 4 different Name Servers found
|
| A | Good: Name servers with different Top Level Domains / Public Suffix List entries found: 4 Name Servers, 4 Top Level Domains: org, net, com, co.uk
|
| A | Good: Name Servers with different domain names found.: 4 different Domains found
|
| Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: US
|
| A | Info: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 205., 1 different subnets (first two Bytes): 205.251., 4 different subnets (first three Bytes): 205.251.193., 205.251.194., 205.251.196., 205.251.198.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2600:, 1 different subnets (first two blocks): 2600:9000:, 4 different subnets (first three blocks): 2600:9000:5301:, 2600:9000:5302:, 2600:9000:5304:, 2600:9000:5306:, 4 different subnets (first four blocks): 2600:9000:5301:7e00:, 2600:9000:5302:4100:, 2600:9000:5304:ce00:, 2600:9000:5306:6200:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 8 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 8 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns-1230.awsdns-25.org: 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
|
| 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://lehina.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.96.92.90
|
| 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: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
|
| A | Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
|
| 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: 204714 milliseconds, 204.714 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)