| 1. General Results, most used to calculate the result |
| A | name "itil5.one" is domain, public suffix is ".one", top-level-domain is ".one", top-level-domain-type is "generic", tld-manager is "One.com A/S", num .one-domains preloaded: 267 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: itil5.one has only one ip address.
|
| Warning: Only one ip address found: www.itil5.one 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: itil5.one 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.itil5.one has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | Good - only one version with Http-Status 200
|
| A | Good: No cookie sent via http.
|
| 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (3 urls)
|
| https://www.itil5.one/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://www.itil5.one/ 77.220.214.139
| https://www.itil5.one/
| Correct redirect http - https with the same domain name
|
| B | https://itil5.one/ 77.220.214.139
|
| Missing HSTS-Header
|
| B | https://www.itil5.one/ 77.220.214.139
|
| Missing HSTS-Header
|
| B | https://www.itil5.one/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Missing HSTS-Header
|
| B | https://itil5.one/ 77.220.214.139
| PHPSESSID=u1gdvdv84e60fpii9t8a6d2h3f; path=/
| Cookie sent via https, but not marked as secure
|
| B | https://itil5.one/ 77.220.214.139
| PHPSESSID=u1gdvdv84e60fpii9t8a6d2h3f; path=/
| 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.
|
| H | Fatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
|
| I | http://itil5.one/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.220.214.139
|
| 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.
|
| N | https://itil5.one/ 77.220.214.139
| https://proneks.com.ua/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://www.itil5.one/ 77.220.214.139
| https://proneks.com.ua/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://www.itil5.one/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://77.220.214.139/ 77.220.214.139
| https://proneks.com.ua/
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | www.itil5.one:25
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | itil5.one:25
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | itil5.one:587
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.itil5.one:587
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | www.itil5.one:8083
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | itil5.one:8083
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| O |
|
| R | https://itil5.one/ 77.220.214.139
| https://proneks.com.ua/
| Redirect to not existing domain
|
| R | https://www.itil5.one/ 77.220.214.139
| https://proneks.com.ua/
| Redirect to not existing domain
|
| R | https://77.220.214.139/ 77.220.214.139
| https://proneks.com.ua/
| Redirect to not existing domain
|
| 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 itil5.one, 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.itil5.one, 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.itil5.one
|
| 2. Header-Checks |
| U |
|
| No https result with http status 2** or 4** (standard-check) found, no header checked.
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 23 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
|
| A | Info:: 23 Queries complete, 23 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 7.7 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 4 different Name Servers found: ns1.zomro.net, ns2.zomro.ru, ns3.zomro.com, ns4.zomro.su, 4 Name Servers included in Delegation: ns1.zomro.net, ns2.zomro.ru, ns3.zomro.com, ns4.zomro.su, 4 Name Servers included in 2 Zone definitions: ns1.zomro.net, ns2.zomro.ru, ns3.zomro.com, ns4.zomro.su, 1 Name Servers listed in SOA.Primary: ns1.zomro.net.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.zomro.net.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.zomro.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 | Good: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
|
| A | Good: Some Name Servers have IPv6 addresses: 1 Name Servers with IPv6 found (3 Name Servers without IPv6)
|
| A | Good: Name servers with different Top Level Domains / Public Suffix List entries found: 4 Name Servers, 4 Top Level Domains: su, ru, net, com
|
| A | Good: Name Servers with different domain names found.: 4 different Domains found
|
| A | Good: Name servers with different Country locations found: 4 Name Servers, 4 Countries: BG, DE, NL, PL
|
| A | Info: Ipv4-Subnet-list: 4 Name Servers, 4 different subnets (first Byte): 116., 185., 212., 51., 4 different subnets (first two Bytes): 116.202., 185.82., 212.8., 51.38., 4 different subnets (first three Bytes): 116.202.0., 185.82.216., 212.8.245., 51.38.146.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 1 Name Servers with IPv6, 1 different subnets (first block): 2a00:, 1 different subnets (first two blocks): 2a00:1ca8:, 1 different subnets (first three blocks): 2a00:1ca8:00a7:, 1 different subnets (first four blocks): 2a00:1ca8:00a7:0000:
|
| Fatal: All Name Server IPv6 addresses from the same subnet.
|
| A | Good: Nameserver supports TCP connections: 5 good Nameserver
|
| X | Nameserver Timeout checking Echo Capitalization: ns3.zomro.com / 51.38.146.91
|
| X | Nameserver Timeout checking EDNS512: ns3.zomro.com / 51.38.146.91
|
| Nameserver doesn't pass all EDNS-Checks: b.nic.one: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (dns1.defra1). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns3.zomro.com / 51.38.146.91: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: ns4.zomro.su / 116.202.0.200: OP100: ok. FLAGS: fatal timeout. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (ns4.zomro.su). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: x.nic.one: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (Auth_Host4.Frankfurt_Node1). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: y.nic.one: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (Auth_Host4.Frankfurt_Node1). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: z.nic.one: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (Auth_Host2.Frankfurt_Node1). 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 |
| A | https://www.itil5.one/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Good: Acme-Check - Answer looks like a correct keyAuthorization - String: Filename + "." + base64url(Thumbprint(accountKey)). So creating a Letsencrypt certificate using that integrated solution should work. Don't use another client (like Certbot). Don't mix integrated solutions with own ACME-clients, that may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | Good: No https + http status 200 with inline CSS / JavaScript found
|
| A | Good: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
|
| https://www.itil5.one/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| 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.
|
| http://itil5.one/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.220.214.139
|
| 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 files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 1 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, 1 complete.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 1 image 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, 1 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: All img-elements have a valid alt-attribute.: 1 img-elements found.
|
| 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
|
| http://itil5.one/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.220.214.139
| 1.267 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 956777 milliseconds, 956.777 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)