| 1. General Results, most used to calculate the result |
| A | name "curated-contents.fly.dev" is domain, public suffix is ".fly.dev", top-level-domain is ".dev", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc.", num .dev-domains preloaded: 15 (complete: 270180)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: curated-contents.fly.dev has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: curated-contents.fly.dev has 1 ipv4, 1 ipv6 addresses
|
| 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: 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 cookie has a SameSite Attribute with a correct value Strict/Lax/None
|
| 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.
|
| A | Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
| A | http://curated-contents.fly.dev/ 66.241.125.35
| https://curated-contents.fly.dev/
| Correct redirect http - https with the same domain name
|
| A | http://curated-contents.fly.dev/ 2a09:8280:1::6f:ec02:0
| https://curated-contents.fly.dev/
| Correct redirect http - https with the same domain name
|
| B | https://curated-contents.fly.dev/ 66.241.125.35
|
| Missing HSTS-Header
|
| B | https://curated-contents.fly.dev/ 2a09:8280:1::6f:ec02:0
|
| Missing HSTS-Header
|
| B | https://curated-contents.fly.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Missing HSTS-Header
|
| B | https://curated-contents.fly.dev/ 66.241.125.35
| _curated_contents_key=SFMyNTY.g3QAAAABbQAAAAtfY3NyZl90b2tlbm0AAAAYZm9EUjdMQmcyMHMySVVTVFRrd0pQVDQy.vyC6Qb5-EAn40VT4nJQKVCaINdV7WPO4V_2j0EXtF38; path=/; HttpOnly; SameSite=Lax
| Cookie sent via https, but not marked as secure
|
| B | https://curated-contents.fly.dev/ 2a09:8280:1::6f:ec02:0
| _curated_contents_key=SFMyNTY.g3QAAAABbQAAAAtfY3NyZl90b2tlbm0AAAAYVndzWk5RZmZaRU8xZTctNzczand0UWRP.XH4HkY5Yhut56g34id23wgnnCDVlnLlrd8DY84IBmBE; path=/; HttpOnly; SameSite=Lax
| Cookie sent via https, but not marked as secure
|
| 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 curated-contents.fly.dev, 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 curated-contents.fly.dev, 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.curated-contents.fly.dev
|
| 2. Header-Checks |
| A | curated-contents.fly.dev 66.241.125.35
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: strict-origin-when-cross-origin
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: SAMEORIGIN
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls.
|
| A | curated-contents.fly.dev 2a09:8280:1::6f:ec02:0
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: strict-origin-when-cross-origin
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: SAMEORIGIN
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls.
|
| F | curated-contents.fly.dev 66.241.125.35
| Content-Security-Policy
| Critical: Missing Header:
|
| F | curated-contents.fly.dev 66.241.125.35
| Permissions-Policy
| Critical: Missing Header:
|
| B | curated-contents.fly.dev 66.241.125.35
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | curated-contents.fly.dev 66.241.125.35
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | curated-contents.fly.dev 66.241.125.35
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | curated-contents.fly.dev 2a09:8280:1::6f:ec02:0
| Content-Security-Policy
| Critical: Missing Header:
|
| F | curated-contents.fly.dev 2a09:8280:1::6f:ec02:0
| Permissions-Policy
| Critical: Missing Header:
|
| B | curated-contents.fly.dev 2a09:8280:1::6f:ec02:0
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | curated-contents.fly.dev 2a09:8280:1::6f:ec02:0
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | curated-contents.fly.dev 2a09:8280:1::6f:ec02:0
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 18 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
|
| A | Info:: 18 Queries complete, 18 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Bad (greater 8):: An average of 9.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: ns1.flydns.net, ns2.flydns.net, 2 Name Servers included in Delegation: ns1.flydns.net, ns2.flydns.net, 2 Name Servers included in 1 Zone definitions: ns1.flydns.net, ns2.flydns.net, 1 Name Servers listed in SOA.Primary: ns1.flydns.net.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.flydns.net.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.flydns.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: ns1.flydns.net, ns2.flydns.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: 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: 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: flydns.net
|
| 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): 137., 1 different subnets (first two Bytes): 137.66., 1 different subnets (first three Bytes): 137.66.40.
|
| X | Fatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.:
|
| A | Good: Nameserver supports TCP connections: 1 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 1 good Nameserver
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.flydns.net
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.flydns.net
|
| Nameserver doesn't pass all EDNS-Checks: ns1.flydns.net: 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.flydns.net / 137.66.40.7: 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.flydns.net / 137.66.40.7: 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: ns2.flydns.net / 137.66.40.8: 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 |
| 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).
|
| A | Good: No https + http status 200 with inline CSS / JavaScript found
|
| https://curated-contents.fly.dev/ 66.241.125.35
|
| 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://curated-contents.fly.dev/ 2a09:8280:1::6f:ec02:0
|
| 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 script Elements (type text/javascript) and src-Attribute have a defer / async - Attribute. So loading and executing these JavaScripts doesn't block parsing and rendering the Html-Output.
|
| A | Good: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 4 external CSS / JavaScript files found
|
| A | Good: All svg-Images greater 1024 Bytes without internal compression are compressed. Svg is an Xml-Application, so Compression reduces the size of the file. 10 images (type image/svg+xml, image/x-icon, image/vnd.microsoft.icon) found with compression.
|
| A | Good: All CSS / JavaScript files are sent with a long Cache-Control header (minimum 7 days). So the browser can re-use these files, no download is required. 4 external CSS / JavaScript files with long Cache-Control max-age found
|
| 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, 12 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 12 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: Some img-elements have a valid alt-attribute.: 12 img-elements found, 8 img-elements with correct alt-attributes (defined, not an empty value).
|
| 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
|
| https://curated-contents.fly.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 3.043 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 305560 milliseconds, 305.560 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)