| 1. General Results, most used to calculate the result |
A | name "rp1.ssh.town" is subdomain, public suffix is ".town", top-level-domain is ".town", top-level-domain-type is "generic", tld-manager is "Binky Moon, LLC", num .town-domains preloaded: 14 (complete: 240622)
|
A | Good: All ip addresses are public addresses
|
A | Good: Minimal 2 ip addresses per domain name found: rp1.ssh.town has 8 different ip addresses (authoritative).
|
A | Good: Ipv4 and Ipv6 addresses per domain name found: rp1.ssh.town has 4 ipv4, 4 ipv6 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
|
A | Good: No cookie sent via http.
|
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)
|
A | http://rp1.ssh.town/ 45.140.42.13
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 45.140.42.13
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 45.140.42.13
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 45.140.42.13
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 89.58.0.232
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 89.58.0.232
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 89.58.0.232
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 89.58.0.232
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 2602:fc24:11:31d7::1
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 2602:fc24:11:31d7::1
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 2602:fc24:11:31d7::1
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 2602:fc24:11:31d7::1
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 2a03:4000:5d:f9c:d47c:9ff:feea:215a
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 2a03:4000:5d:f9c:d47c:9ff:feea:215a
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 2a03:4000:5d:f9c:d47c:9ff:feea:215a
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
A | http://rp1.ssh.town/ 2a03:4000:5d:f9c:d47c:9ff:feea:215a
| https://rp1.ssh.town/
| Correct redirect http - https with the same domain name
|
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 rp1.ssh.town, 4 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 rp1.ssh.town, 4 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.rp1.ssh.town
|
| 2. Header-Checks |
A | rp1.ssh.town 45.140.42.13
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
A |
| Referrer-Policy
| Ok: Header without syntax errors found: no-referrer-when-downgrade
|
A | rp1.ssh.town 45.140.42.13
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
A |
| Referrer-Policy
| Ok: Header without syntax errors found: no-referrer-when-downgrade
|
A | rp1.ssh.town 89.58.0.232
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
A |
| Referrer-Policy
| Ok: Header without syntax errors found: no-referrer-when-downgrade
|
A | rp1.ssh.town 89.58.0.232
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
A |
| Referrer-Policy
| Ok: Header without syntax errors found: no-referrer-when-downgrade
|
A | rp1.ssh.town 2602:fc24:11:31d7::1
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
A |
| Referrer-Policy
| Ok: Header without syntax errors found: no-referrer-when-downgrade
|
A | rp1.ssh.town 2602:fc24:11:31d7::1
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
A |
| Referrer-Policy
| Ok: Header without syntax errors found: no-referrer-when-downgrade
|
A | rp1.ssh.town 2a03:4000:5d:f9c:d47c:9ff:feea:215a
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
A |
| Referrer-Policy
| Ok: Header without syntax errors found: no-referrer-when-downgrade
|
A | rp1.ssh.town 2a03:4000:5d:f9c:d47c:9ff:feea:215a
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
A |
| Referrer-Policy
| Ok: Header without syntax errors found: no-referrer-when-downgrade
|
F | rp1.ssh.town 45.140.42.13
| Content-Security-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 45.140.42.13
| Permissions-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 45.140.42.13
| Content-Security-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 45.140.42.13
| Permissions-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 89.58.0.232
| Content-Security-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 89.58.0.232
| Permissions-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 89.58.0.232
| Content-Security-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 89.58.0.232
| Permissions-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 2602:fc24:11:31d7::1
| Content-Security-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 2602:fc24:11:31d7::1
| Permissions-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 2602:fc24:11:31d7::1
| Content-Security-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 2602:fc24:11:31d7::1
| Permissions-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 2a03:4000:5d:f9c:d47c:9ff:feea:215a
| Content-Security-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 2a03:4000:5d:f9c:d47c:9ff:feea:215a
| Permissions-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 2a03:4000:5d:f9c:d47c:9ff:feea:215a
| Content-Security-Policy
| Critical: Missing Header:
|
F | rp1.ssh.town 2a03:4000:5d:f9c:d47c:9ff:feea:215a
| 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 2 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.ns1.gcorelabs.net (2a03:90c0:9990::1053, 92.223.100.53), ns2.gcdn.services (2a03:90c0:9990::2053, 92.223.77.53)
|
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:: 2 different Name Servers found: ns1.gcorelabs.net, ns2.gcdn.services, 2 Name Servers included in Delegation: ns1.gcorelabs.net, ns2.gcdn.services, 2 Name Servers included in 1 Zone definitions: ns1.gcorelabs.net, ns2.gcdn.services, 1 Name Servers listed in SOA.Primary: ns1.gcorelabs.net.
|
A | Good: Only one SOA.Primary Name Server found.: ns1.gcorelabs.net.
|
A | Good: SOA.Primary Name Server included in the delegation set.: ns1.gcorelabs.net.
|
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: 2 Name Servers, 1 different subnets (first Byte): 92., 1 different subnets (first two Bytes): 92.223., 2 different subnets (first three Bytes): 92.223.100., 92.223.77.
|
A | Good: Name Server IPv4-addresses from different subnet found:
|
A | Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2a03:, 1 different subnets (first two blocks): 2a03:90c0:, 1 different subnets (first three blocks): 2a03:90c0:9990:, 1 different subnets (first four blocks): 2a03:90c0:9990:0000:
|
| Fatal: All Name Server IPv6 addresses from the same subnet.
|
A | Good: Nameserver supports TCP connections: 8 good Nameserver
|
A | Good: Nameserver supports Echo Capitalization: 8 good Nameserver
|
A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns1.gcorelabs.net: 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.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.gcorelabs.net / 92.223.100.53: OP100: SOA expected and found, NOERR expectend and NOERR found, Version 0 expectend and found, NO OPT100 expected, OPT100 echoed. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (am3-hw-edge-gc121). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.gcorelabs.net / 92.223.100.53: OP100: SOA expected and found, NOERR expectend and NOERR found, Version 0 expectend and found, NO OPT100 expected, OPT100 echoed. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (am3-hw-edge-gc61). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.gcorelabs.net / 92.223.100.53: OP100: SOA expected and found, NOERR expectend and NOERR found, Version 0 expectend and found, NO OPT100 expected, OPT100 echoed. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (am3-hw-edge-gc78). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.gcorelabs.net / 2a03:90c0:9990::1053: OP100: SOA expected and found, NOERR expectend and NOERR found, Version 0 expectend and found, NO OPT100 expected, OPT100 echoed. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (am3-hw-edge-gc120). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.gcorelabs.net / 2a03:90c0:9990::1053: OP100: SOA expected and found, NOERR expectend and NOERR found, Version 0 expectend and found, NO OPT100 expected, OPT100 echoed. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (am3-hw-edge-gc110). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.gcorelabs.net / 2a03:90c0:9990::1053: OP100: SOA expected and found, NOERR expectend and NOERR found, Version 0 expectend and found, NO OPT100 expected, OPT100 echoed. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (am3-hw-edge-gc62). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns2.gcdn.services / 92.223.77.53: OP100: SOA expected and found, NOERR expectend and NOERR found, Version 0 expectend and found, NO OPT100 expected, OPT100 echoed. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (am3-hw-edge-gc113). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns2.gcdn.services / 92.223.77.53: OP100: SOA expected and found, NOERR expectend and NOERR found, Version 0 expectend and found, NO OPT100 expected, OPT100 echoed. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (am3-hw-edge-gc96). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns2.gcdn.services / 2a03:90c0:9990::2053: OP100: SOA expected and found, NOERR expectend and NOERR found, Version 0 expectend and found, NO OPT100 expected, OPT100 echoed. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (am3-hw-edge-gc76). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns2.gcdn.services / 2a03:90c0:9990::2053: OP100: SOA expected and found, NOERR expectend and NOERR found, Version 0 expectend and found, NO OPT100 expected, OPT100 echoed. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (am3-hw-edge-gc121). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: v2n1.nic.town: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (FRA5). COOKIE: ok. CLIENTSUBNET: ok.
|
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 |
| https://rp1.ssh.town/.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://rp1.ssh.town/ 45.140.42.13
|
| 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://rp1.ssh.town/ 45.140.42.13
|
| 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://rp1.ssh.town/ 89.58.0.232
|
| 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://rp1.ssh.town/ 89.58.0.232
|
| 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://rp1.ssh.town/ 2602:fc24:11:31d7::1
|
| 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://rp1.ssh.town/ 2602:fc24:11:31d7::1
|
| 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://rp1.ssh.town/ 2a03:4000:5d:f9c:d47c:9ff:feea:215a
|
| 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://rp1.ssh.town/ 2a03:4000:5d:f9c:d47c:9ff:feea:215a
|
| 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://rp1.ssh.town/.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://rp1.ssh.town/ 45.140.42.13
|
| 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://rp1.ssh.town/ 45.140.42.13
|
| 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://rp1.ssh.town/ 89.58.0.232
|
| 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://rp1.ssh.town/ 89.58.0.232
|
| 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://rp1.ssh.town/ 2602:fc24:11:31d7::1
|
| 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://rp1.ssh.town/ 2602:fc24:11:31d7::1
|
| 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://rp1.ssh.town/ 2a03:4000:5d:f9c:d47c:9ff:feea:215a
|
| 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://rp1.ssh.town/ 2a03:4000:5d:f9c:d47c:9ff:feea:215a
|
| 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://rp1.ssh.town/.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. 9 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. 9 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, 9 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: 210547 milliseconds, 210.547 seconds
|