| 1. General Results, most used to calculate the result |
| A | name "lumo.proton.me" is subdomain, public suffix is ".me", top-level-domain is ".me", top-level-domain-type is "country-code", Country is Montenegro, tld-manager is "Government of Montenegro", num .me-domains preloaded: 2269 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: lumo.proton.me 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: lumo.proton.me 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: 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 sent via https is marked as secure
|
| A | Good: Every cookie has a SameSite Attribute with a correct value Strict/Lax/None
|
| A | Good: every https has a Strict Transport Security Header
|
| A | Good: HSTS max-age is long enough, 31536000 seconds = 365 days
|
| A | Good: HSTS has includeSubdomains - directive
|
| A | Good: HSTS has preload directive
|
| A | Excellent: Main Domain is in the Google-Preload-List
|
| A | Excellent: Main 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://lumo.proton.me/guest 185.70.42.51
| https://lumo.proton.me/guest
| Correct redirect http - https with the same domain name
|
| M | https://185.70.42.51/guest 185.70.42.51
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://185.70.42.51/guest 185.70.42.51
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| 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 lumo.proton.me, 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.lumo.proton.me
|
| 2. Header-Checks |
| A | lumo.proton.me 185.70.42.51
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'self'; connect-src 'self' blob: https://zrh-storage.proton.me https://osl-storage.proton.me https://fra-storage.proton.me; script-src 'self' 'wasm-unsafe-eval' blob: 'sha256-eAhF1Kdccp0BTXM6nMW7SYBdV0c3fZwzcC177TQ692g='; style-src 'self' 'unsafe-inline'; img-src http: https: data: blob: cid:; frame-src 'self' blob: https://account.proton.me https://verify.proton.me https://mail.proton.me https://drive.proton.me https://lumo.proton.me https://lumo-api.proton.me; object-src 'self' blob:; child-src 'self' data: blob:; report-uri https://reports.proton.me/reports/csp; frame-ancestors https://mail.proton.me https://calendar.proton.me https://drive.proton.me https://docs.proton.me https://lumo.proton.me https://wallet.proton.me https://sheets.proton.me https://account.proton.me/ https://account.protonvpn.com/;
|
| B |
|
| Info: Header-Element is deprecated. report-uri https://reports.proton.me/reports/csp
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked.
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'.
|
| E |
|
| Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used.
|
| A |
|
| Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| F |
|
| Critical: object-src with a scheme definition found. That's too global, don't use such a definition. Use a list of urls instead if you really want to use object / embed / applet.
|
| A |
|
| Good: script-src without 'unsafe-inline' and 'unsafe-eval' found. That's the recommended configuration.
|
| F |
|
| Critical: script-src with * or a scheme found. Never allow wildcard - sources.
|
| A |
|
| Good: script-src without data: schema found. Why is this important? The data: schema allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| A |
| 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 |
| Expect-CT
| Ok: Header without syntax errors found: max-age=2592000, enforce, report-uri="https://reports.proton.me/reports/tls"
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. max-age=2592000, enforce, report-uri="https://reports.proton.me/reports/tls"
|
| A |
| X-Xss-Protection
| Ok: Header without syntax errors found: 0
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. 0
|
| F | lumo.proton.me 185.70.42.51
| Permissions-Policy
| Critical: Missing Header:
|
| B | lumo.proton.me 185.70.42.51
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | lumo.proton.me 185.70.42.51
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | lumo.proton.me 185.70.42.51
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
|
| A | Info:: 2 Queries complete, 2 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.proton.me (185.70.42.150), ns2.proton.me (176.119.200.150), ns3.proton.me (205.132.47.1)
|
| A | Good (1 - 3.0):: An average of 0.7 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 3 different Name Servers found: ns1.proton.me, ns2.proton.me, ns3.proton.me, 3 Name Servers included in Delegation: ns1.proton.me, ns2.proton.me, ns3.proton.me, 3 Name Servers included in 1 Zone definitions: ns1.proton.me, ns2.proton.me, ns3.proton.me, 1 Name Servers listed in SOA.Primary: ns1.proton.me.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.proton.me.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.proton.me.
|
| 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.proton.me, ns2.proton.me, ns3.proton.me
|
| 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: 3 different Name Servers found
|
| Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 3 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.: 3 Name Servers, 1 Top Level Domain: me
|
| 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: proton.me
|
| A | Good: Name servers with different Country locations found: 3 Name Servers, 3 Countries: CH, DE, US
|
| A | Info: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 176., 185., 205., 3 different subnets (first two Bytes): 176.119., 185.70., 205.132., 3 different subnets (first three Bytes): 176.119.200., 185.70.42., 205.132.47.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| 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
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: a0.nic.me: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (fra1.micro.hosts.meta.redstone.afilias-nst.info-1740000113). COOKIE: fatal timeout. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.proton.me: 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
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: sectigo.com is allowed to create certificates
|
| 4. Content- and Performance-critical Checks |
| https://lumo.proton.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| 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://lumo.proton.me/guest 185.70.42.51
|
| 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://lumo.proton.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| 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://lumo.proton.me/guest 185.70.42.51
|
| 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://lumo.proton.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| 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. 8 external CSS / JavaScript files found
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 10 external CSS / JavaScript 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, 10 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| 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: 120883 milliseconds, 120.883 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)