| 1. General Results, most used to calculate the result |
A | name "global.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: 94244 (complete: 244198)
|
A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: global.com has only one ip address.
|
| Warning: Only one ip address found: www.global.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: global.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.global.com 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: 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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
A | http://global.com/ 188.212.35.66
| https://global.com/
| Correct redirect http - https with the same domain name
|
A | http://www.global.com/ 188.212.35.66
| https://www.global.com/
| Correct redirect http - https with the same domain name
|
B | https://global.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| uk_region_suggest=yes; expires=Thu, 16-May-2024 17:46:19 GMT; Max-Age=86400; path=/; domain=.global.com
| Cookie sent via https, but not marked as secure
|
B | https://global.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| uk_region_suggest=yes; expires=Thu, 16-May-2024 17:46:19 GMT; Max-Age=86400; path=/; domain=.global.com
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
N | https://188.212.35.66/ 188.212.35.66
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
X | Fatal error: Nameserver doesn't support TCP connection: ns1.as39202.net / 81.20.49.60: Timeout
|
| 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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain global.com, 1 ip addresses.
|
| 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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain www.global.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.global.com
|
| 2. Header-Checks |
A | global.com 188.212.35.66
| Content-Security-Policy
| Ok: Header without syntax errors found: upgrade-insecure-requests
|
F |
|
| Bad: Missing default-src directive. A default-src directive is used if one of the specialized fetch directives (child-src, connect-src, font-src, frame-src, img-src, manifest-src, media-src, object-src, prefetch-src, script-src, style-src, worker-src) isn't defined. Missing default-src, all sources are allowed, that's bad. A default-src with 'none' or 'self' blocks that.
|
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.
|
E |
|
| Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in 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: No object-src and no default-src as fallback defined. So object / embed / applet can load every resource. That's fatal.
|
F |
|
| Critical: No script-src and no default-src as fallback defined. So scripts are unlimited. That's fatal.
|
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 | global.com 188.212.35.66
| X-Content-Type-Options
| Critical: Missing Header:
|
F | global.com 188.212.35.66
| Referrer-Policy
| Critical: Missing Header:
|
F | global.com 188.212.35.66
| Permissions-Policy
| Critical: Missing Header:
|
| 3. DNS- and NameServer - Checks |
A | Info:: 4 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
|
A | Info:: 4 Queries complete, 4 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.ns0.as39202.net (81.20.49.93), ns2.as39202.co.uk (81.20.48.93), ns1.as39202.net (81.20.49.60)
|
A | Good (1 - 3.0):: An average of 1.3 queries per domain name server required to find all ip addresses of all name servers.
|
A | Info:: 3 different Name Servers found: ns0.as39202.net, ns1.as39202.net, ns2.as39202.co.uk, 3 Name Servers included in Delegation: ns0.as39202.net, ns1.as39202.net, ns2.as39202.co.uk, 3 Name Servers included in 1 Zone definitions: ns0.as39202.net, ns1.as39202.net, ns2.as39202.co.uk, 1 Name Servers listed in SOA.Primary: ns0.as39202.net.
|
A | Good: Only one SOA.Primary Name Server found.: ns0.as39202.net.
|
A | Good: SOA.Primary Name Server included in the delegation set.: ns0.as39202.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: ns0.as39202.net, ns1.as39202.net, ns2.as39202.co.uk
|
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
|
A | Good: Name servers with different Top Level Domains / Public Suffix List entries found: 3 Name Servers, 2 Top Level Domains: net, co.uk
|
A | Good: Name Servers with different domain names found.: 2 different Domains found
|
| Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: GB
|
A | Info: Ipv4-Subnet-list: 3 Name Servers, 1 different subnets (first Byte): 81., 1 different subnets (first two Bytes): 81.20., 2 different subnets (first three Bytes): 81.20.48., 81.20.49.
|
A | Good: Name Server IPv4-addresses from different subnet found:
|
A | Good: Nameserver supports Echo Capitalization: 3 good Nameserver
|
A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 3 good Nameserver
|
A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 3 good Nameserver
|
A | Good: All SOA have the same Serial Number
|
A | Good: CAA entries found, creating certificate is limited: amazon.com is allowed to create certificates
|
A | Good: CAA entries found, creating certificate is limited: Digicert.com is allowed to create certificates
|
A | Good: CAA entries found, creating certificate is limited: globalsign.com is allowed to create certificates
|
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: pki.goog is allowed to create certificates
|
| 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).
|
| https://global.com/ 188.212.35.66
|
| 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
|
| https://global.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 3.794 seconds
| Warning: 404 needs more then one second
|
| https://www.global.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 3.587 seconds
| Warning: 404 needs more then one second
|
A | Duration: 288283 milliseconds, 288.283 seconds
|