1. General Results, most used to calculate the result A name "sudatel.sd" is domain, public suffix is ".sd", top-level-domain is ".sd", top-level-domain-type is "country-code", Country is Sudan (the), tld-manager is "Sudan Internet Society", num .sd-domains preloaded: 3 (complete: 231048) A Good: All ip addresses are public addresses Warning: Only one ip address found: sudatel.sd has only one ip address. Warning: Only one ip address found: www.sudatel.sd 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: sudatel.sd 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.sudatel.sd 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: every https has a Strict Transport Security Header A Good: HSTS max-age is long enough, 63072000 seconds = 730 days A Good: HSTS has preload directive Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive. 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) N https://212.0.142.33/ 212.0.142.33 https://www.sudatel.sd/ Error - Certificate isn't trusted, RemoteCertificateNameMismatch O sudatel.sd / 212.0.142.33 / 443 Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 10 Cipher Suites without Forward Secrecy found O www.sudatel.sd / 212.0.142.33 / 443 Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 10 Cipher Suites without Forward Secrecy found X Fatal error: Nameserver doesn't support TCP connection: ans1.canar.sd: Timeout X Fatal error: Nameserver doesn't support TCP connection: ans1.sis.sd: Timeout X Fatal error: Nameserver doesn't support TCP connection: ans2.canar.sd: Timeout X Fatal error: Nameserver doesn't support TCP connection: ans2.sis.sd: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns1.sudatel.sd / 2001:4228:0:2::6: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns2.sudatel.sd / 2001:4228:0:3::38: 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 the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain sudatel.sd, 1 ip addresses, 1 different http results. 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 www.sudatel.sd, 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.sudatel.sd 2. Header-Checks A www.sudatel.sd 212.0.142.33 Content-Security-Policy Ok: Header without syntax errors found: object-src 'none' 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. A Good: object-src only with 'none' or 'self' found, no scheme, no other urls. That blocks object / embed / applet - elements. F Critical: No script-src and no default-src as fallback defined. So scripts are unlimited. That's fatal. A X-Content-Type-Options Ok: Header without syntax errors found: nosniff F X-Frame-Options Critical: Header with syntax errors found: SAMEORIGIN,DENY; SAMEORIGIN; B Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN,DENY; 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. E Critical: Unknown Header-Element found SAMEORIGIN,DENY E Critical: Unknown Header-Element found SAMEORIGIN,DENY A X-Xss-Protection Ok: Header without syntax errors found: 1; mode=block B Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block F www.sudatel.sd 212.0.142.33 Referrer-Policy Critical: Missing Header: F www.sudatel.sd 212.0.142.33 Permissions-Policy Critical: Missing Header: 3. DNS- and NameServer - Checks A Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 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.sudatel.sd (196.202.139.230), ns2.sudatel.sd (196.202.139.234) A Good (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers. A Info:: 2 different Name Servers found: ns1.sudatel.sd, ns2.sudatel.sd, 2 Name Servers included in Delegation: ns1.sudatel.sd, ns2.sudatel.sd, 2 Name Servers included in 1 Zone definitions: ns1.sudatel.sd, ns2.sudatel.sd, 1 Name Servers listed in SOA.Primary: ns1.sudatel.sd. A Good: Only one SOA.Primary Name Server found.: ns1.sudatel.sd. A Good: SOA.Primary Name Server included in the delegation set.: ns1.sudatel.sd. 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.sudatel.sd, ns2.sudatel.sd 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: sd 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: sudatel.sd Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: SD A Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 196., 1 different subnets (first two Bytes): 196.202., 1 different subnets (first three Bytes): 196.202.139. 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 Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:4228:, 1 different subnets (first three blocks): 2001:4228:0000:, 2 different subnets (first four blocks): 2001:4228:0000:0002:, 2001:4228:0000:0003: A Good: Name Server IPv6 addresses from different subnets found. X Nameserver Timeout checking Echo Capitalization: ns1.sudatel.sd / 2001:4228:0:2::6 X Nameserver Timeout checking Echo Capitalization: ns2.sudatel.sd / 2001:4228:0:3::38 X Nameserver Timeout checking EDNS512: ns1.sudatel.sd / 2001:4228:0:2::6 X Nameserver Timeout checking EDNS512: ns2.sudatel.sd / 2001:4228:0:3::38 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://sudatel.sd/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 212.0.142.33 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://www.sudatel.sd/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 212.0.142.33 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. https://www.sudatel.sd/ 212.0.142.33 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.sudatel.sd/ 212.0.142.33 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. 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: 506514 milliseconds, 506.514 seconds