| 1. General Results, most used to calculate the result |
| A | name "success.docusign.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: 55723 (complete: 142558)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: success.docusign.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: success.docusign.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: HSTS has preload directive
|
| A | Excellent: Main Domain is in the Google-Preload-List
|
| A | Excellent: Main Domain is in the Mozilla/Firefox-Preload-List
|
| A | HSTS-Preload-Status: Preloaded. 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):6 complete Content-Type - header (11 urls)
|
| https://151.101.2.133/ 151.101.2.133
|
| Url with incomplete Content-Type - header - missing charset
|
| https://151.101.66.133/ 151.101.66.133
|
| Url with incomplete Content-Type - header - missing charset
|
| https://151.101.114.133/ 151.101.114.133
|
| Url with incomplete Content-Type - header - missing charset
|
| https://151.101.130.133/ 151.101.130.133
|
| Url with incomplete Content-Type - header - missing charset
|
| https://151.101.194.133/ 151.101.194.133
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://success.docusign.com/ 151.101.2.133
| https://success.docusign.com/
| Correct redirect http - https with the same domain name
|
| A | http://success.docusign.com/ 151.101.66.133
| https://success.docusign.com/
| Correct redirect http - https with the same domain name
|
| A | http://success.docusign.com/ 151.101.114.133
| https://success.docusign.com/
| Correct redirect http - https with the same domain name
|
| A | http://success.docusign.com/ 151.101.130.133
| https://success.docusign.com/
| Correct redirect http - https with the same domain name
|
| A | http://success.docusign.com/ 151.101.194.133
| https://success.docusign.com/
| Correct redirect http - https with the same domain name
|
| N | https://151.101.2.133/ 151.101.2.133
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://151.101.66.133/ 151.101.66.133
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://151.101.114.133/ 151.101.114.133
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://151.101.130.133/ 151.101.130.133
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://151.101.194.133/ 151.101.194.133
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| 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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain success.docusign.com, 1 ip addresses.
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| A | Info:: 20 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 5 Name Servers.
|
| A | Info:: 20 Queries complete, 20 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 5 different Name Servers found: a10-65.akam.net, a11-66.akam.net, a1-246.akam.net, a14-67.akam.net, a24-64.akam.net, 5 Name Servers included in Delegation: a1-246.akam.net, a10-65.akam.net, a11-66.akam.net, a14-67.akam.net, a24-64.akam.net, 5 Name Servers included in 1 Zone definitions: a1-246.akam.net, a10-65.akam.net, a11-66.akam.net, a14-67.akam.net, a24-64.akam.net, 1 Name Servers listed in SOA.Primary: a1-246.akam.net.
|
| A | Good: Only one SOA.Primary Name Server found.: a1-246.akam.net.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: a1-246.akam.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: 5 Name Servers, 5 different subnets (first Byte): 184., 193., 2., 84., 96., 5 different subnets (first two Bytes): 184.26., 193.108., 2.16., 84.53., 96.7., 5 different subnets (first three Bytes): 184.26.161., 193.108.91., 2.16.130., 84.53.139., 96.7.50.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2600:, 2 different subnets (first two blocks): 2600:1401:, 2600:1480:, 2 different subnets (first three blocks): 2600:1401:0002:, 2600:1480:0001:, 2 different subnets (first four blocks): 2600:1401:0002:0000:, 2600:1480:0001:0000:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 7 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 7 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 7 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 7 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: a1-246.akam.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.
|
| 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://success.docusign.com/.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: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://success.docusign.com/ 151.101.2.133
|
| 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://success.docusign.com/ 151.101.66.133
|
| 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://success.docusign.com/ 151.101.114.133
|
| 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://success.docusign.com/ 151.101.130.133
|
| 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://success.docusign.com/ 151.101.194.133
|
| 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://success.docusign.com/ 151.101.2.133
|
| 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://success.docusign.com/ 151.101.66.133
|
| 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://success.docusign.com/ 151.101.114.133
|
| 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://success.docusign.com/ 151.101.130.133
|
| 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://success.docusign.com/ 151.101.194.133
|
| 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.
|
| https://success.docusign.com/ 151.101.2.133
|
| 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.: 3 script elements without defer/async.
|
| https://success.docusign.com/ 151.101.66.133
|
| 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.: 3 script elements without defer/async.
|
| https://success.docusign.com/ 151.101.114.133
|
| 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.: 3 script elements without defer/async.
|
| https://success.docusign.com/ 151.101.130.133
|
| 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.: 3 script elements without defer/async.
|
| https://success.docusign.com/ 151.101.194.133
|
| 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.: 3 script elements without defer/async.
|
| A | Good: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 25 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. 0 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 5 with Cache-Control max-age too short (minimum 7 days), 20 with Cache-Control long enough, 25 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
|
| http://success.docusign.com/ 151.101.2.133
|
| Warning: HSTS header sent via http has no effect
|
| http://success.docusign.com/ 151.101.66.133
|
| Warning: HSTS header sent via http has no effect
|
| http://success.docusign.com/ 151.101.114.133
|
| Warning: HSTS header sent via http has no effect
|
| http://success.docusign.com/ 151.101.130.133
|
| Warning: HSTS header sent via http has no effect
|
| http://success.docusign.com/ 151.101.194.133
|
| Warning: HSTS header sent via http has no effect
|
| A | Info: Different Server-Headers found
|
| A | Duration: 208440 milliseconds, 208.440 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)