| 1. General Results, most used to calculate the result |
| A | name "safaricom.et" is domain, public suffix is ".et", top-level-domain is ".et", top-level-domain-type is "country-code", Country is Ethiopia, tld-manager is "Ethio telecom", num .et-domains preloaded: 14 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: safaricom.et has 2 different ip addresses (authoritative).
|
| Warning: Only one ip address found: www.safaricom.et 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: safaricom.et 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.safaricom.et has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://safaricom.et/ 102.218.49.49
| https://safaricom.et/en
| Correct redirect https to https
|
| A | https://safaricom.et/ 102.218.49.116
| https://safaricom.et/en
| Correct redirect https to https
|
| A | https://www.safaricom.et/ 102.218.49.49
| https://www.safaricom.et/en
| Correct redirect https to https
|
| A | Good: destination is https
|
| 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 | Warning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15552000 seconds = 180 days found
|
| B | https://safaricom.et/ 102.218.49.49
| cookiesession1=678B76984B2347AC5B57BE5DAEC54749;Expires=Thu, 03 Sep 2026 09:26:29 GMT;Path=/;HttpOnly
| Cookie sent via https, but not marked as secure
|
| B | https://safaricom.et/ 102.218.49.116
| cookiesession1=678B7699993B13394366026D4CF2FC28;Expires=Thu, 03 Sep 2026 09:26:46 GMT;Path=/;HttpOnly
| Cookie sent via https, but not marked as secure
|
| B | https://safaricom.et/en
| cookiesession1=678B769837E928142764EDB0C615CA7B;Expires=Thu, 03 Sep 2026 09:27:26 GMT;Path=/;HttpOnly
| Cookie sent via https, but not marked as secure
|
| B | https://www.safaricom.et/en
| cookiesession1=678B769885F1049E7A1DB3B23F9CD227;Expires=Thu, 03 Sep 2026 09:27:40 GMT;Path=/;HttpOnly
| Cookie sent via https, but not marked as secure
|
| B | https://safaricom.et/ 102.218.49.49
| cookiesession1=678B76984B2347AC5B57BE5DAEC54749;Expires=Thu, 03 Sep 2026 09:26:29 GMT;Path=/;HttpOnly
| 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.
|
| B | https://safaricom.et/ 102.218.49.116
| cookiesession1=678B7699993B13394366026D4CF2FC28;Expires=Thu, 03 Sep 2026 09:26:46 GMT;Path=/;HttpOnly
| 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.
|
| B | https://safaricom.et/en
| cookiesession1=678B769837E928142764EDB0C615CA7B;Expires=Thu, 03 Sep 2026 09:27:26 GMT;Path=/;HttpOnly
| 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.
|
| B | https://www.safaricom.et/en
| cookiesession1=678B769885F1049E7A1DB3B23F9CD227;Expires=Thu, 03 Sep 2026 09:27:40 GMT;Path=/;HttpOnly
| 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.
|
| C | Error - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
|
| C | Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
|
| O | safaricom.et / 102.218.49.49 / 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. 17 Cipher Suites without Forward Secrecy found
|
| O | safaricom.et / 102.218.49.116 / 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. 17 Cipher Suites without Forward Secrecy found
|
| O | www.safaricom.et / 102.218.49.49 / 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. 17 Cipher Suites without Forward Secrecy found
|
| 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 safaricom.et, 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 safaricom.et, 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 www.safaricom.et, 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.safaricom.et
|
| 2. Header-Checks |
| A | safaricom.et
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'self'; script-src 'self' 'unsafe-inline' www.googletagmanager.com; worker-src 'self' blob:; connect-src 'self' www.google-analytics.com www.googletagmanager.com https://safaricom.bamboohr.com ; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' blob: data: resources.bamboohr.com flagsapi.com i.ytimg.com img.youtube.com ; font-src 'self' https://fonts.gstatic.com https://fonts.googleapis.com; object-src 'none'; base-uri 'self'; frame-src 'self' https://www.youtube.com/; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests;
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked.
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'.
|
| A |
|
| Good: form-action directive found. That reduces the risk sending data to unwanted domains. 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.
|
| A |
|
| Good: base-uri directive found. That limits 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: script-src with 'unsafe-inline' or 'unsafe-eval' and without a nonce found. That's dangerous, don't use it. If you really need one of these unsafe directives, add a nonce.
|
| A |
|
| Good: script-src without * and a scheme found.
|
| 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: same-origin
|
| A |
| Permissions-Policy
| Ok: Header without syntax errors found: camera=(), geolocation=(), microphone=()
|
| 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 |
| X-Xss-Protection
| Ok: Header without syntax errors found: 1
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. 1
|
| A | www.safaricom.et
| Content-Security-Policy
| Ok: Header without syntax errors found: default-src 'self'; script-src 'self' 'unsafe-inline' www.googletagmanager.com; worker-src 'self' blob:; connect-src 'self' www.google-analytics.com www.googletagmanager.com https://safaricom.bamboohr.com ; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' blob: data: resources.bamboohr.com flagsapi.com i.ytimg.com img.youtube.com ; font-src 'self' https://fonts.gstatic.com https://fonts.googleapis.com; object-src 'none'; base-uri 'self'; frame-src 'self' https://www.youtube.com/; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests;
|
| A |
|
| Good: default-src directive only with 'none' or 'self', additional sources are blocked.
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'.
|
| A |
|
| Good: form-action directive found. That reduces the risk sending data to unwanted domains. 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.
|
| A |
|
| Good: base-uri directive found. That limits 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: script-src with 'unsafe-inline' or 'unsafe-eval' and without a nonce found. That's dangerous, don't use it. If you really need one of these unsafe directives, add a nonce.
|
| A |
|
| Good: script-src without * and a scheme found.
|
| 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: same-origin
|
| A |
| Permissions-Policy
| Ok: Header without syntax errors found: camera=(), geolocation=(), microphone=()
|
| 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 |
| X-Xss-Protection
| Ok: Header without syntax errors found: 1
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. 1
|
| B | safaricom.et
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | safaricom.et
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | safaricom.et
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| B | www.safaricom.et
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.safaricom.et
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.safaricom.et
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
|
| A | Info:: 13 Queries complete, 5 with IPv6, 8 with IPv4.
|
| Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
|
| Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 4 different Name Servers found: ns1.safaricombusiness.co.ke, ns2.safaricombusiness.co.ke, ns3.safaricombusiness.co.ke, ns4.safaricombusiness.co.ke, 4 Name Servers included in Delegation: ns1.safaricombusiness.co.ke, ns2.safaricombusiness.co.ke, ns3.safaricombusiness.co.ke, ns4.safaricombusiness.co.ke, 4 Name Servers included in 1 Zone definitions: ns1.safaricombusiness.co.ke, ns2.safaricombusiness.co.ke, ns3.safaricombusiness.co.ke, ns4.safaricombusiness.co.ke, 1 Name Servers listed in SOA.Primary: ns1.safaricombusiness.co.ke.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.safaricombusiness.co.ke.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.safaricombusiness.co.ke.
|
| 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.safaricombusiness.co.ke, ns2.safaricombusiness.co.ke, ns3.safaricombusiness.co.ke, ns4.safaricombusiness.co.ke
|
| 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: 4 different Name Servers found
|
| Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 4 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.: 4 Name Servers, 1 Top Level Domain: co.ke
|
| 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: safaricombusiness.co.ke
|
| Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: KE
|
| A | Info: Ipv4-Subnet-list: 4 Name Servers, 2 different subnets (first Byte): 197., 41., 2 different subnets (first two Bytes): 197.248., 41.203., 2 different subnets (first three Bytes): 197.248.128., 41.203.208.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Good: Nameserver supports TCP connections: 4 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 4 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: adns1.safaricom.et: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: adns2.safaricom.et: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: sectigo.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: entrust.net is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: gandi.net is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: globalsign 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: intcaa.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
|
| A | Good: CAA entries found, creating certificate is limited: Playbet.et is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: sectigo.com is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: sectigo.com is allowed to create wildcard-certificates
|
| A | Good: CAA entries found, creating certificate is limited: digicert.com is allowed to create wildcard-certificates
|
| A | Good: CAA entries found, creating certificate is limited: entrust.net is allowed to create wildcard-certificates
|
| A | Good: CAA entries found, creating certificate is limited: globalsign is allowed to create wildcard-certificates
|
| A | Good: CAA entries found, creating certificate is limited: globalsign.com is allowed to create wildcard-certificates
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create wildcard-certificates
|
| A | Good: CAA entries found, creating certificate is limited: pki.goog is allowed to create wildcard-certificates
|
| A | Good: CAA entries found, creating certificate is limited: Playbet.et is allowed to create wildcard-certificates
|
| A | Good: CAA entries found, creating certificate is limited: sectigo.com is allowed to create wildcard-certificates
|
| Warning: Unknown CAA found: sectigo.com isn't defined. Unknown entry. May be wrong written, may be not longer valid. May be a missing entry in this tool.
|
| Warning: Unknown CAA found: gandi.net isn't defined. Unknown entry. May be wrong written, may be not longer valid. May be a missing entry in this tool.
|
| Warning: Unknown CAA found: globalsign isn't defined. Unknown entry. May be wrong written, may be not longer valid. May be a missing entry in this tool.
|
| Warning: Unknown CAA found: intcaa.com isn't defined. Unknown entry. May be wrong written, may be not longer valid. May be a missing entry in this tool.
|
| Warning: Unknown CAA found: Playbet.et isn't defined. Unknown entry. May be wrong written, may be not longer valid. May be a missing entry in this tool.
|
| Warning: Unknown CAA found: sectigo.com isn't defined. Unknown entry. May be wrong written, may be not longer valid. May be a missing entry in this tool.
|
| Warning: Unknown CAA found: globalsign isn't defined. Unknown entry. May be wrong written, may be not longer valid. May be a missing entry in this tool.
|
| Warning: Unknown CAA found: Playbet.et isn't defined. Unknown entry. May be wrong written, may be not longer valid. May be a missing entry in this tool.
|
| 4. Content- and Performance-critical Checks |
| http://safaricom.et/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 102.218.49.49
|
| 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://safaricom.et/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 102.218.49.116
|
| 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.safaricom.et/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 102.218.49.49
|
| 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 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://safaricom.et/en
|
| 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.safaricom.et/en
|
| 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
|
| A | Duration: 1436600 milliseconds, 1436.600 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)