1. General Results, most used to calculate the result A name "portal.jibo.com" is subdomain, 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: 85538 (complete: 220007) A Good: All ip addresses are public 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 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://portal.jibo.com/ 34.227.185.174 Missing HSTS-Header B https://portal.jibo.com/ 44.214.98.85 Missing HSTS-Header N https://34.227.185.174/ 34.227.185.174 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://44.214.98.85/ 44.214.98.85 Error - Certificate isn't trusted, RemoteCertificateNameMismatch V http://portal.jibo.com/ 34.227.185.174 Connect failure - perhaps firewall V http://portal.jibo.com/ 44.214.98.85 Connect failure - perhaps firewall V http://portal.jibo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.227.185.174 Connect failure - perhaps firewall V http://portal.jibo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 44.214.98.85 Connect failure - perhaps firewall 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.portal.jibo.com 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) A portal.jibo.com 34.227.185.174 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 portal.jibo.com 44.214.98.85 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 portal.jibo.com 34.227.185.174 Content-Security-Policy Critical: Missing Header: F portal.jibo.com 34.227.185.174 X-Content-Type-Options Critical: Missing Header: F portal.jibo.com 34.227.185.174 Referrer-Policy Critical: Missing Header: F portal.jibo.com 34.227.185.174 Permissions-Policy Critical: Missing Header: F portal.jibo.com 44.214.98.85 Content-Security-Policy Critical: Missing Header: F portal.jibo.com 44.214.98.85 X-Content-Type-Options Critical: Missing Header: F portal.jibo.com 44.214.98.85 Referrer-Policy Critical: Missing Header: F portal.jibo.com 44.214.98.85 Permissions-Policy Critical: Missing Header: 3. DNS- and NameServer - Checks A Info:: 8 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers. A Info:: 8 Queries complete, 8 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-02.azure-dns.com (2603:1061:0:700::2, 40.90.4.2), ns2-02.azure-dns.net (2620:1ec:8ec:700::2, 64.4.48.2), ns3-02.azure-dns.org (204.14.183.2, 2a01:111:4000:700::2), ns4-02.azure-dns.info (208.84.5.2, 2620:1ec:bda:700::2) A Good (1 - 3.0):: An average of 2.0 queries per domain name server required to find all ip addresses of all name servers. A Info:: 4 different Name Servers found: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, 4 Name Servers included in Delegation: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, 4 Name Servers included in 1 Zone definitions: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, 1 Name Servers listed in SOA.Primary: ns1-02.azure-dns.com. A Good: Only one SOA.Primary Name Server found.: ns1-02.azure-dns.com. A Good: SOA.Primary Name Server included in the delegation set.: ns1-02.azure-dns.com. 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 Info: Ipv4-Subnet-list: 4 Name Servers, 4 different subnets (first Byte): 150., 204., 208., 40., 4 different subnets (first two Bytes): 150.171., 204.14., 208.84., 40.90., 4 different subnets (first three Bytes): 150.171.21., 204.14.183., 208.84.5., 40.90.4. A Excellent: Every Name Server IPv4-address starts with an unique Byte. A Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 3 different subnets (first block): 2603:, 2620:, 2a01:, 3 different subnets (first two blocks): 2603:1061:, 2620:01ec:, 2a01:0111:, 4 different subnets (first three blocks): 2603:1061:0000:, 2620:01ec:08ec:, 2620:01ec:0bda:, 2a01:0111:4000:, 4 different subnets (first four blocks): 2603:1061:0000:0700:, 2620:01ec:08ec:0700:, 2620:01ec:0bda:0700:, 2a01:0111:4000:0700: A Good: Name Server IPv6 addresses from different subnets found. A Good: Nameserver supports TCP connections: 16 good Nameserver A Good: Nameserver supports Echo Capitalization: 16 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 16 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 16 good Nameserver Nameserver doesn't pass all EDNS-Checks: ns1-02.azure-dns.com: 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 http://portal.jibo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.227.185.174 Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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://portal.jibo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 44.214.98.85 Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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. https://portal.jibo.com/ 34.227.185.174 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://portal.jibo.com/ 44.214.98.85 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. https://portal.jibo.com/ 34.227.185.174 Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 2 script elements without defer/async. https://portal.jibo.com/ 44.214.98.85 Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 2 script elements without defer/async. Warning: CSS / JavaScript found without GZip support. Send these ressources with GZip. 4 external CSS / JavaScript files without GZip found - 0 with GZip, 4 complete Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 4 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, 4 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: 144387 milliseconds, 144.387 seconds