1. General Results, most used to calculate the result A name "techtinker.net" is domain, public suffix is ".net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 8481 (complete: 220007) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: techtinker.net has 4 different ip addresses (authoritative). A Good: Minimal 2 ip addresses per domain name found: www.techtinker.net has 4 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: techtinker.net has 2 ipv4, 2 ipv6 addresses A Good: Ipv4 and Ipv6 addresses per domain name found: www.techtinker.net has 2 ipv4, 2 ipv6 addresses A Good: No asked Authoritative Name Server had a timeout 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://techtinker.net/ 104.21.67.205 https://techtinker.net/ Correct redirect http - https with the same domain name A http://techtinker.net/ 172.67.180.150 https://techtinker.net/ Correct redirect http - https with the same domain name A http://techtinker.net/ 2606:4700:3035::ac43:b496 https://techtinker.net/ Correct redirect http - https with the same domain name A http://techtinker.net/ 2606:4700:3037::6815:43cd https://techtinker.net/ Correct redirect http - https with the same domain name A http://www.techtinker.net/ 104.21.67.205 https://www.techtinker.net/ Correct redirect http - https with the same domain name A http://www.techtinker.net/ 172.67.180.150 https://www.techtinker.net/ Correct redirect http - https with the same domain name A http://www.techtinker.net/ 2606:4700:3035::ac43:b496 https://www.techtinker.net/ Correct redirect http - https with the same domain name A http://www.techtinker.net/ 2606:4700:3037::6815:43cd https://www.techtinker.net/ Correct redirect http - https with the same domain name B https://techtinker.net/ 104.21.67.205 Missing HSTS-Header B https://techtinker.net/ 172.67.180.150 Missing HSTS-Header B https://techtinker.net/ 2606:4700:3035::ac43:b496 Missing HSTS-Header B https://techtinker.net/ 2606:4700:3037::6815:43cd Missing HSTS-Header B https://www.techtinker.net/ 104.21.67.205 Missing HSTS-Header B https://www.techtinker.net/ 172.67.180.150 Missing HSTS-Header B https://www.techtinker.net/ 2606:4700:3035::ac43:b496 Missing HSTS-Header B https://www.techtinker.net/ 2606:4700:3037::6815:43cd Missing HSTS-Header http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.21.67.205 XSRF-TOKEN=eyJpdiI6Ikt3Zy9Cc3lkWTBhdmFiRGgxOFU2aEE9PSIsInZhbHVlIjoiKzdWOXRTTXM3NlpWVGM4ZFFHODJFTStnSnRBbHBjVTFmRFozd3haV09OT2NkdW00TmwyUjgrSzFqVVpXaWlURGxnMVEyaXNMNUVNTCtFUUV0bjl3Qm9NTWhIaTduemFtUEIvdi9NbVZVaVR2MkxTZVg0VmpTSHVsWUVIdmhoZDAiLCJtYWMiOiI2ZDljMDNjYmI4ZTA4MDVlZDc0N2QwM2UyZTNmZWVmYjllMzA2ZDIyZDA1NmMyMGYxOTI0NjMyYTRlNzFjMmZjIiwidGFnIjoiIn0%3D; expires=Sat, 18-Mar-2023 18:20:55 GMT; Max-Age=43200; path=/; samesite=lax Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.21.67.205 pterodactyl_session=eyJpdiI6IlpEZ2xhb3Q0WVk3cTFPN3JVclZpZlE9PSIsInZhbHVlIjoiZE1PSTdKbmZCRjB1UEV0ajJHWE92OVQyWHlNSHAxVGUrdmVmQURTRVk4aDh5TnNpSmJSWEJXMHcvckl2bmJTdThGRGYxWm1VWFMvWDZKK1crRE9VeVF2eGI3YmpMcVpZbVVHRWFISFVVTmhWbG1yWFZnN2U4WWhobWtadnBSTXAiLCJtYWMiOiJmYzg3MDgwMGExMDJkZDYwNjFkMjY3MWJkODg4ZDU2MzdjYjkzMWFiOTAwYTIxOTI0M2QwNjNjNmM2NjcwZDM0IiwidGFnIjoiIn0%3D; expires=Sat, 18-Mar-2023 18:20:55 GMT; Max-Age=43200; path=/; httponly; samesite=lax Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 172.67.180.150 XSRF-TOKEN=eyJpdiI6IlBIbFVkRzBjOXVhOEo5QkM0bWFnRHc9PSIsInZhbHVlIjoiaXZCYmd1VTlvRG93N0krNy9Sb1JVazY5VkFQUVBmN3hwRTU5WkpKWFBGQ2EvNktKNDR6VW8vVU1Tbm5DSFZDU3REYWowQ0lid2JPZkdkQU9vWWR3OExZK0h0QWhVb0Rtdm5TQjBFVHh1T1NqZkxNWDZpS0x4MmJWOFZHa2V6YkYiLCJtYWMiOiIwNjExYjc1NTg5YjQ4MDE4ODI2MTExY2NkYzFhNjI3ZDRmZWFhNWEwMTdiZTU4MjdiY2QyM2EwNzdkMDYwZDY4IiwidGFnIjoiIn0%3D; expires=Sat, 18-Mar-2023 18:20:56 GMT; Max-Age=43200; path=/; samesite=lax Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 172.67.180.150 pterodactyl_session=eyJpdiI6IlBDSmp2V2FrZk9qcEF1ZUVqTy9TNHc9PSIsInZhbHVlIjoiTnYvSFcyanB3Qm5pUER4M1lySncvMWtWSDUrcmJRa2E2YzJIdW9lVUZIZkZsWU1MRVhIemF0ZXJ4eGtVaDJzT3ZZNHZ4UEtrNkhydUJzTDFjYWYrUVpvTTNnczVZdUdlTjNuSUNlcklTTEQvMGV6MXYzNm93VWI3Y1hya1RIaloiLCJtYWMiOiI3NzRkNTJhYjM3ZmE3NTdlZTM5NzUxZWFlZGNkN2UzMThiNmY1YzYzNDcwOTI4ZWFjNmZmMjVhYjFlNmMyZDU1IiwidGFnIjoiIn0%3D; expires=Sat, 18-Mar-2023 18:20:56 GMT; Max-Age=43200; path=/; httponly; samesite=lax Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3035::ac43:b496 XSRF-TOKEN=eyJpdiI6IlFoTHlKSnBTMUJQYUlLZ3MzaG9Yd2c9PSIsInZhbHVlIjoiTUY3dmRqSHZNcGFhejY3N0JOSGZEYmpMdVhSMFQ3R3U1RGNhUENYUjVpdkFLcFdvbXJHSFU4cG9zbzFJVytMSmViTDRJcm9MZGJGb1M3MzNic0RwU1h4SHk1dENNZ0tOVERsVzdHcktjQUtCWmVVL3ZiSS9MZC9qZHVxckVDOGgiLCJtYWMiOiIyNDYzZDJiNDUyZWE3NDY3MmM0OWFiZmFiZjI4NjE3Njc3OWE5MzhhNWNiYjQ0MjZkNmJjOGU5NDNkMWI1MzViIiwidGFnIjoiIn0%3D; expires=Sat, 18-Mar-2023 18:20:57 GMT; Max-Age=43200; path=/; samesite=lax Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3035::ac43:b496 pterodactyl_session=eyJpdiI6InNrOGxoT1pPdWl2WW5Xd2pCWk5iQ3c9PSIsInZhbHVlIjoiS1VhRlNpZEtXN2UyVVNYUU95cUh5WHBoSjU5ZGsvTTFwcFlzTFVnb3dRWS84SU5PdGI4bjI1a3dDVXJaL2FkdUdmMERDME00V2RTc290d09WREd2TFh4MnlDVlZESnBPckd0eFlrRE1ZekNkZWM2Tnc1MWZZUzk3cS95R3pJM0wiLCJtYWMiOiJmNWRmNDJkYmU2MDc1MTc2ZTJiNDZiZDg5ZDE4Y2NhNDQ5ODViMjhkOTBlNGZhMmYyZTAxNzhlNGI0NDM5ZWRlIiwidGFnIjoiIn0%3D; expires=Sat, 18-Mar-2023 18:20:57 GMT; Max-Age=43200; path=/; httponly; samesite=lax Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3037::6815:43cd XSRF-TOKEN=eyJpdiI6IkJxU3Y0RGJXMnV4TGY5cElsWTAreUE9PSIsInZhbHVlIjoiSEVrMDhwR25Nd2ZpcWZoOFhpOGNwaGsvUW9IOFhtNXg3UXJ6VlhmNTVlTlM2VjRsRmN0djJHQU1LSjRyRUFYSkl6bG85UWYvWFRIZVBUKzFpVzB6ODBGdmFZT3FqUHA1ZlNPdkVLYUgvMmZ5RFE1N2s5cDhNQXFYayszS3N5VnciLCJtYWMiOiJjODdkZDVhMmEwNTg3Zjg3OWE3NTUxZTQ3ZmMyOThmMjkyMmJkOWRiZGY1MjQzMzJjMTIxYWZkNWJmNjJkMzlhIiwidGFnIjoiIn0%3D; expires=Sat, 18-Mar-2023 18:20:58 GMT; Max-Age=43200; path=/; samesite=lax Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3037::6815:43cd pterodactyl_session=eyJpdiI6ImZjZUhLTGFxdi9yTVh6K1hURDMzZnc9PSIsInZhbHVlIjoiOU91S2F4ZU1IQTByTGdaZGpyNWkvTy9jbjM5bTdyL3F5K1V5MlA0MklzT2piek5YQUN1R1Q0VXRsTG9PZUd1anRROGROdURSamlOMTl1Zk5Hc2FtSExXc1diOVlXNWl0V2N0UUhFOUtDa0pzVXdISmdaQWVOb0hzcHA1cGtKTVkiLCJtYWMiOiI1ODVmNzk5ZmU5NDljOGE1M2QzMDIxNjUzNjgyYmJjZjUxODE0NWQ4ZDFjZjI2MTJjZGUwODBmODc0NjU3OWRhIiwidGFnIjoiIn0%3D; expires=Sat, 18-Mar-2023 18:20:58 GMT; Max-Age=43200; path=/; httponly; samesite=lax Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. B https://techtinker.net/ 104.21.67.205 cf_use_ob=0; path=/; expires=Sat, 18-Mar-23 06:21:01 GMT Cookie sent via https, but not marked as secure B https://techtinker.net/ 172.67.180.150 cf_use_ob=0; path=/; expires=Sat, 18-Mar-23 06:21:05 GMT Cookie sent via https, but not marked as secure B https://techtinker.net/ 2606:4700:3035::ac43:b496 cf_use_ob=0; path=/; expires=Sat, 18-Mar-23 06:21:07 GMT Cookie sent via https, but not marked as secure B https://techtinker.net/ 2606:4700:3037::6815:43cd cf_use_ob=0; path=/; expires=Sat, 18-Mar-23 06:21:10 GMT Cookie sent via https, but not marked as secure B https://techtinker.net/ 104.21.67.205 cf_use_ob=0; path=/; expires=Sat, 18-Mar-23 06:21:01 GMT 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://techtinker.net/ 172.67.180.150 cf_use_ob=0; path=/; expires=Sat, 18-Mar-23 06:21:05 GMT 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://techtinker.net/ 2606:4700:3035::ac43:b496 cf_use_ob=0; path=/; expires=Sat, 18-Mar-23 06:21:07 GMT 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://techtinker.net/ 2606:4700:3037::6815:43cd cf_use_ob=0; path=/; expires=Sat, 18-Mar-23 06:21:10 GMT 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. F https://www.techtinker.net/ 104.21.67.205 http://www.techtinker.net/ Wrong redirect https - http - never redirect https to http F https://www.techtinker.net/ 172.67.180.150 http://www.techtinker.net/ Wrong redirect https - http - never redirect https to http F https://www.techtinker.net/ 2606:4700:3035::ac43:b496 http://www.techtinker.net/ Wrong redirect https - http - never redirect https to http F https://www.techtinker.net/ 2606:4700:3037::6815:43cd http://www.techtinker.net/ Wrong redirect https - http - never redirect https to http H Fatal error: No https - result with http-status 200, no encryption I http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.21.67.205 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it. I http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 172.67.180.150 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it. I http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3035::ac43:b496 Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it. I http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3037::6815:43cd Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it. L http://www.techtinker.net/ 104.21.67.205 https://www.techtinker.net/ Error two - step - loop L http://www.techtinker.net/ 172.67.180.150 https://www.techtinker.net/ Error two - step - loop L http://www.techtinker.net/ 2606:4700:3035::ac43:b496 https://www.techtinker.net/ Error two - step - loop L http://www.techtinker.net/ 2606:4700:3037::6815:43cd https://www.techtinker.net/ Error two - step - loop P https://104.21.67.205/ 104.21.67.205 Error creating a TLS-Connection: No more details available. P https://172.67.180.150/ 172.67.180.150 Error creating a TLS-Connection: No more details available. P https://[2606:4700:3035:0000:0000:0000:ac43:b496]/ 2606:4700:3035::ac43:b496 Error creating a TLS-Connection: No more details available. P https://[2606:4700:3037:0000:0000:0000:6815:43cd]/ 2606:4700:3037::6815:43cd Error creating a TLS-Connection: No more details available. 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 techtinker.net, 4 ip addresses. 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 www.techtinker.net, 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 techtinker.net, 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 www.techtinker.net, 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.techtinker.net 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) U No https result with http status 2** or 4** (standard-check) found, no header checked. 3. DNS- and NameServer - Checks A Info:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers. A Info:: 7 Queries complete, 7 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers. A Info:: 2 different Name Servers found: guss.ns.cloudflare.com, lady.ns.cloudflare.com, 2 Name Servers included in Delegation: guss.ns.cloudflare.com, lady.ns.cloudflare.com, 2 Name Servers included in 1 Zone definitions: guss.ns.cloudflare.com, lady.ns.cloudflare.com, 1 Name Servers listed in SOA.Primary: guss.ns.cloudflare.com. A Good: Only one SOA.Primary Name Server found.: guss.ns.cloudflare.com. A Good: SOA.Primary Name Server included in the delegation set.: guss.ns.cloudflare.com. 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: guss.ns.cloudflare.com, lady.ns.cloudflare.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 Good: Minimal 2 different name servers (public suffix and public ip address) found: 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: com 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: cloudflare.com A Good: Name servers with different Country locations found: 2 Name Servers, 3 Countries: CA, CR, GB A Info: Ipv4-Subnet-list: 6 Name Servers, 3 different subnets (first Byte): 108., 172., 173., 3 different subnets (first two Bytes): 108.162., 172.64., 173.245., 6 different subnets (first three Bytes): 108.162.192., 108.162.193., 172.64.32., 172.64.33., 173.245.58., 173.245.59. A Good: Name Server IPv4-addresses from different subnet found: A Info: IPv6-Subnet-list: 6 Name Servers with IPv6, 3 different subnets (first block): 2606:, 2803:, 2a06:, 3 different subnets (first two blocks): 2606:4700:, 2803:f800:, 2a06:98c1:, 4 different subnets (first three blocks): 2606:4700:0050:, 2606:4700:0058:, 2803:f800:0050:, 2a06:98c1:0050:, 4 different subnets (first four blocks): 2606:4700:0050:0000:, 2606:4700:0058:0000:, 2803:f800:0050:0000:, 2a06:98c1:0050:0000: A Good: Name Server IPv6 addresses from different subnets found. A Good: Nameserver supports TCP connections: 12 good Nameserver A Good: Nameserver supports Echo Capitalization: 12 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 12 good Nameserver 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://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.21.67.205 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. http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 172.67.180.150 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. http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3035::ac43:b496 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. http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3037::6815:43cd 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. http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.21.67.205 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.: 1 script elements without defer/async. http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 172.67.180.150 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.: 1 script elements without defer/async. http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3035::ac43:b496 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.: 1 script elements without defer/async. http://techtinker.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3037::6815:43cd 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.: 1 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. 0 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 4 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: 115116 milliseconds, 115.116 seconds