| 1. General Results, most used to calculate the result |
| A | name "moloch.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: moloch.com has only one ip address.
|
| Warning: Only one ip address found: www.moloch.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: moloch.com 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.moloch.com has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| 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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
| B | https://moloch.com/ 64.190.63.222
|
| Missing HSTS-Header
|
| B | https://www.moloch.com/ 64.190.63.222
|
| Missing HSTS-Header
|
| C | Error - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
|
| C | Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
|
| 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.
|
| I | https://moloch.com/ 64.190.63.222
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| I | https://www.moloch.com/ 64.190.63.222
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| I | http://moloch.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 64.190.63.222
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
|
| I | http://www.moloch.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 64.190.63.222
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
|
| 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 moloch.com, 1 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 www.moloch.com, 1 ip addresses.
|
| A | Good: _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Domainname: _mta-sts.moloch.com
|
| B | Bad: _mta-sts TXT found, but invalid
|
| 2. Header-Checks |
| F | moloch.com 64.190.63.222
| Content-Security-Policy
| Critical: Missing Header:
|
| F | moloch.com 64.190.63.222
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | moloch.com 64.190.63.222
| Referrer-Policy
| Critical: Missing Header:
|
| F | moloch.com 64.190.63.222
| Permissions-Policy
| Critical: Missing Header:
|
| B | moloch.com 64.190.63.222
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | moloch.com 64.190.63.222
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | moloch.com 64.190.63.222
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.moloch.com 64.190.63.222
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.moloch.com 64.190.63.222
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.moloch.com 64.190.63.222
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.moloch.com 64.190.63.222
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.moloch.com 64.190.63.222
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.moloch.com 64.190.63.222
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.moloch.com 64.190.63.222
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 19 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
|
| A | Info:: 19 Queries complete, 19 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Bad (greater 8):: An average of 9.5 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: ns1.sedoparking.com, ns2.sedoparking.com, 2 Name Servers included in Delegation: ns1.sedoparking.com, ns2.sedoparking.com, 2 Name Servers included in 1 Zone definitions: ns1.sedoparking.com, ns2.sedoparking.com, 1 Name Servers listed in SOA.Primary: ns1.sedoparking.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.sedoparking.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.sedoparking.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: ns1.sedoparking.com, ns2.sedoparking.com
|
| A | Good: All Name Server Domain Names have a Public Suffix.
|
| A | Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
|
| Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 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: sedoparking.com
|
| A | Good: Name servers with different Country locations found: 2 Name Servers, 2 Countries: DE, US
|
| A |
|
| 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 |
| http://moloch.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 64.190.63.222
|
| 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.
|
| http://www.moloch.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 64.190.63.222
|
| 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 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://moloch.com/ 64.190.63.222
|
| 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://www.moloch.com/ 64.190.63.222
|
| 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.
|
| 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.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 4 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 4 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 4 img-elements without alt-attribute, 0 img-elements with empty alt-attribute 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: 235217 milliseconds, 235.217 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)