| 1. General Results, most used to calculate the result |
| A | name "alifelived.app" is domain, public suffix is ".app", top-level-domain is ".app", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc.", num .app-domains preloaded: 46 (complete: 245733)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: alifelived.app has 2 different ip addresses (authoritative).
|
| 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: alifelived.app has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | Good: destination is https
|
| A | Good - only one version with Http-Status 200
|
| A | Good: one preferred version: www is preferred
|
| A | Good: No cookie sent via http.
|
| A | Excellent: Domain is in the Google-Preload-List
|
| A | Excellent: Domain is in the Mozilla/Firefox-Preload-List
|
| A | HSTS-Preload-Status: Preloaded. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
|
| https://www.alifelived.app/ 34.249.200.254
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.alifelived.app/ 52.17.119.105
|
| Url with incomplete Content-Type - header - missing charset
|
| https://www.alifelived.app/ 63.35.51.142
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://alifelived.app/ 75.2.70.75
| https://alifelived.app/
| Correct redirect http - https with the same domain name
|
| A | http://alifelived.app/ 99.83.190.102
| https://alifelived.app/
| Correct redirect http - https with the same domain name
|
| A | http://www.alifelived.app/ 34.249.200.254
| https://www.alifelived.app/
| Correct redirect http - https with the same domain name
|
| A | http://www.alifelived.app/ 52.17.119.105
| https://www.alifelived.app/
| Correct redirect http - https with the same domain name
|
| A | http://www.alifelived.app/ 63.35.51.142
| https://www.alifelived.app/
| Correct redirect http - https with the same domain name
|
| A | Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain alifelived.app, 2 ip addresses.
|
| 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 alifelived.app, 2 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.alifelived.app
|
| 2. Header-Checks |
| F | www.alifelived.app 34.249.200.254
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.alifelived.app 34.249.200.254
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.alifelived.app 34.249.200.254
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.alifelived.app 34.249.200.254
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.alifelived.app 34.249.200.254
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.alifelived.app 34.249.200.254
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.alifelived.app 34.249.200.254
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.alifelived.app 52.17.119.105
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.alifelived.app 52.17.119.105
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.alifelived.app 52.17.119.105
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.alifelived.app 52.17.119.105
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.alifelived.app 52.17.119.105
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.alifelived.app 52.17.119.105
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.alifelived.app 52.17.119.105
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.alifelived.app 63.35.51.142
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.alifelived.app 63.35.51.142
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.alifelived.app 63.35.51.142
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.alifelived.app 63.35.51.142
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.alifelived.app 63.35.51.142
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.alifelived.app 63.35.51.142
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.alifelived.app 63.35.51.142
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 24 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
|
| A | Info:: 24 Queries complete, 24 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Bad (greater 8):: An average of 12.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in Delegation: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in 1 Zone definitions: dns1.registrar-servers.com, dns2.registrar-servers.com, 1 Name Servers listed in SOA.Primary: dns1.registrar-servers.com.
|
| A | Good: Only one SOA.Primary Name Server found.: dns1.registrar-servers.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: dns1.registrar-servers.com.
|
| 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: dns1.registrar-servers.com, dns2.registrar-servers.com
|
| 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: 2 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 2 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.: 2 Name Servers, 1 Top Level Domain: com
|
| 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: registrar-servers.com
|
| Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
|
| A | Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 156., 1 different subnets (first two Bytes): 156.154., 2 different subnets (first three Bytes): 156.154.132., 156.154.133.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2610:, 1 different subnets (first two blocks): 2610:00a1:, 2 different subnets (first three blocks): 2610:00a1:1024:, 2610:00a1:1025:, 2 different subnets (first four blocks): 2610:00a1:1024:0000:, 2610:00a1:1025:0000:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| 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 |
| A | Good: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://www.alifelived.app/ 34.249.200.254
|
| 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://www.alifelived.app/ 52.17.119.105
|
| 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://www.alifelived.app/ 63.35.51.142
|
| 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 | 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: 247450 milliseconds, 247.450 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)