| 1. General Results, most used to calculate the result |
| A | name "connect.avnet.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: 105960 (complete: 271405)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: connect.avnet.com 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: connect.avnet.com has no ipv6 address.
|
| 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: every https has a Strict Transport Security Header
|
| A | Good: HSTS max-age is long enough, 31536000 seconds = 365 days
|
| A | Good: HSTS has includeSubdomains - directive
|
| 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (3 urls)
|
| https://connect.avnet.com/ 12.9.136.156
|
| Url with incomplete Content-Type - header - missing charset
|
| https://connect.avnet.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| https://12.9.136.156/ 12.9.136.156
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://connect.avnet.com/ 12.9.136.156
| https://connect.avnet.com/
| Correct redirect http - https with the same domain name
|
| M | https://12.9.136.156/ 12.9.136.156
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://12.9.136.156/ 12.9.136.156
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| O | connect.avnet.com / 12.9.136.156 / 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. 8 Cipher Suites without Forward Secrecy found
|
| 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 connect.avnet.com, 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.connect.avnet.com
|
| 2. Header-Checks |
| A | connect.avnet.com 12.9.136.156
| Content-Security-Policy
| Ok: Header without syntax errors found: frame-ancestors 'self'; upgrade-insecure-requests; block-all-mixed-content
|
| B |
|
| Info: Header-Element is deprecated. block-all-mixed-content
|
| F |
|
| Bad: Missing default-src directive. A default-src directive is used if one of the specialized fetch directives (child-src, connect-src, font-src, frame-src, img-src, manifest-src, media-src, object-src, prefetch-src, script-src, style-src, worker-src) isn't defined. Missing default-src, all sources are allowed, that's bad. A default-src with 'none' or 'self' blocks that.
|
| E |
|
| Bad: No form-action directive found. Use one to limit the form - action - destinations. 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.
|
| E |
|
| Bad: No base-uri directive found. Use one to limit 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.
|
| F |
|
| Critical: No object-src and no default-src as fallback defined. So object / embed / applet can load every resource. That's fatal.
|
| F |
|
| Critical: No script-src and no default-src as fallback defined. So scripts are unlimited. That's fatal.
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: origin
|
| A |
| Permissions-Policy
| Ok: Header without syntax errors found: geolocation=(self), midi=(self), push=(self), sync-xhr=(self), microphone=(self), camera=(self), magnetometer=(self), gyroscope=(self), speaker=(self), vibrate=(self), fullscreen=(self), payment=(self)
|
| 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.
|
| B | connect.avnet.com 12.9.136.156
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | connect.avnet.com 12.9.136.156
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | connect.avnet.com 12.9.136.156
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 19 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 Name Servers.
|
| A | Info:: 19 Queries complete, 19 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 3.2 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 7 different Name Servers found: a1-13.akam.net, a12-66.akam.net, a13-67.akam.net, a14-64.akam.net, a22-65.akam.net, a5-66.akam.net, horse.avnet.com, 6 Name Servers included in Delegation: a1-13.akam.net, a12-66.akam.net, a13-67.akam.net, a14-64.akam.net, a22-65.akam.net, a5-66.akam.net, 6 Name Servers included in 2 Zone definitions: a1-13.akam.net, a12-66.akam.net, a13-67.akam.net, a14-64.akam.net, a22-65.akam.net, a5-66.akam.net, 1 Name Servers listed in SOA.Primary: horse.avnet.com.
|
| A | Good: Only one SOA.Primary Name Server found.: horse.avnet.com.
|
| Error: SOA.Primary Name Server not included in the delegation set.: horse.avnet.com.
|
| A | Good: All Name Server Domain Names have a Public Suffix.
|
| Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1
|
|
|
| A | Info: Ipv4-Subnet-list: 6 Name Servers, 5 different subnets (first Byte): 184., 193., 2., 23., 95., 5 different subnets (first two Bytes): 184.26., 193.108., 2.22., 23.211., 95.100., 6 different subnets (first three Bytes): 184.26.160., 184.26.161., 193.108.91., 2.22.230., 23.211.61., 95.100.168.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 6 Name Servers with IPv6, 1 different subnets (first block): 2600:, 2 different subnets (first two blocks): 2600:1401:, 2600:1480:, 6 different subnets (first three blocks): 2600:1401:0002:, 2600:1480:0800:, 2600:1480:1800:, 2600:1480:7800:, 2600:1480:b000:, 2600:1480:f000:, 6 different subnets (first four blocks): 2600:1401:0002:0000:, 2600:1480:0800:0000:, 2600:1480:1800:0000:, 2600:1480:7800:0000:, 2600:1480:b000:0000:, 2600:1480:f000:0000:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 24 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 24 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 24 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: horse.avnet.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.
|
| Nameserver doesn't pass all EDNS-Checks: horse.avnet.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.
|
| Nameserver doesn't pass all EDNS-Checks: horse.avnet.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 |
| A | Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. 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://connect.avnet.com/ 12.9.136.156
|
| 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.
|
| 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
|
| https://connect.avnet.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 5.873 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 401104 milliseconds, 401.104 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)