| 1. General Results, most used to calculate the result |
| A | name "verisignsecured.com.cn" is domain, public suffix is ".com.cn", top-level-domain is ".cn", top-level-domain-type is "country-code", Country is China, tld-manager is "China Internet Network Information Center (CNNIC)", num .cn-domains preloaded: 931 (complete: 270180)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: verisignsecured.com.cn has 8 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: verisignsecured.com.cn has 4 ipv4, 4 ipv6 addresses
|
| A | https://verisignsecured.com.cn/ 208.80.122.53
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Correct redirect https to https
|
| A | https://verisignsecured.com.cn/ 208.80.122.130
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Correct redirect https to https
|
| A | https://verisignsecured.com.cn/ 208.80.123.127
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Correct redirect https to https
|
| A | https://verisignsecured.com.cn/ 208.80.123.195
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Correct redirect https to https
|
| A | https://www.verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn&loc=en_US
| Correct redirect https to https
|
| A | https://www.verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de&loc=en_US
| Correct redirect https to https
|
| A | Good: No cookie sent via http.
|
| A | Good: every cookie sent via https is marked as secure
|
| 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):6 complete Content-Type - header (7 urls)
|
| http://lostredirect.dnsmadeeasy.com/lostredirect.html
|
| Url with incomplete Content-Type - header - missing charset
|
| B | https://verisignsecured.com.cn/ 208.80.122.53
|
| Missing HSTS-Header
|
| B | https://verisignsecured.com.cn/ 208.80.122.130
|
| Missing HSTS-Header
|
| B | https://verisignsecured.com.cn/ 208.80.123.127
|
| Missing HSTS-Header
|
| B | https://verisignsecured.com.cn/ 208.80.123.195
|
| Missing HSTS-Header
|
| B | https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| max-age=31536000; includeSubDomains;
| Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed.
|
| B | https://www.verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| max-age=31536000; includeSubDomains;
| Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed.
|
| B | https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn&loc=en_US
| max-age=31536000; includeSubDomains;
| Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed.
|
| B | https://www.verisignsecured.com.cn/ 69.58.187.75
| max-age=31536000; includeSubDomains;
| Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed.
|
| B | https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| max-age=31536000; includeSubDomains;
| Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed.
|
| B | https://www.verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| max-age=31536000; includeSubDomains;
| Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed.
|
| B | https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de&loc=en_US
| max-age=31536000; includeSubDomains;
| Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed.
|
| B | https://69.58.187.75/ 69.58.187.75
| max-age=31536000; includeSubDomains;
| Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed.
|
| B | https://www.verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| locale-name=en_US; Max-Age=7776000; Expires=Thu, 07 Aug 2025 18:56:27 GMT; Path=/; Secure
| 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://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn&loc=en_US
| locale-name=en_US; Max-Age=7776000; Expires=Thu, 07 Aug 2025 18:56:40 GMT; Path=/; Secure
| 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://www.verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| locale-name=en_US; Max-Age=7776000; Expires=Thu, 07 Aug 2025 18:56:34 GMT; Path=/; Secure
| 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://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de&loc=en_US
| locale-name=en_US; Max-Age=7776000; Expires=Thu, 07 Aug 2025 18:56:48 GMT; Path=/; Secure
| 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.
|
| C | Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
|
| E | http://verisignsecured.com.cn/ 208.80.122.53
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://verisignsecured.com.cn/ 208.80.122.130
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://verisignsecured.com.cn/ 208.80.123.127
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://verisignsecured.com.cn/ 208.80.123.195
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://verisignsecured.com.cn/ 2600:1803:10a::72
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://verisignsecured.com.cn/ 2600:1803:10b::8
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://verisignsecured.com.cn/ 2600:1803:10c::8
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| E | http://verisignsecured.com.cn/ 2600:1803:10d::40
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| F | https://208.80.122.53/ 208.80.122.53
| http://lostredirect.dnsmadeeasy.com/lostredirect.html
| Wrong redirect https - http - never redirect https to http
|
| F | https://208.80.122.130/ 208.80.122.130
| http://lostredirect.dnsmadeeasy.com/lostredirect.html
| Wrong redirect https - http - never redirect https to http
|
| F | https://208.80.123.127/ 208.80.123.127
| http://lostredirect.dnsmadeeasy.com/lostredirect.html
| Wrong redirect https - http - never redirect https to http
|
| F | https://208.80.123.195/ 208.80.123.195
| http://lostredirect.dnsmadeeasy.com/lostredirect.html
| Wrong redirect https - http - never redirect https to http
|
| 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 | https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn&loc=en_US
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| I | https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de&loc=en_US
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| K | https://verisignsecured.com.cn/ 208.80.122.130, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10a::72, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.122.130, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10b::8, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.122.53, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10a::72, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.122.53, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10b::8, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.122.130, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10c::8, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.122.130, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10d::40, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.123.127, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10a::72, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.123.195, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10a::72, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.123.195, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10b::8, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.123.127, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10b::8, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.123.127, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10c::8, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.122.53, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10c::8, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.122.53, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10d::40, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.123.127, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10d::40, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.123.195, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10c::8, Status -102
| Configuration problem - different ip addresses with different status
|
| K | https://verisignsecured.com.cn/ 208.80.123.195, Status 301
| https://verisignsecured.com.cn/ 2600:1803:10d::40, Status -102
| Configuration problem - different ip addresses with different status
|
| N | https://verisignsecured.com.cn/ 208.80.122.53
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://verisignsecured.com.cn/ 208.80.122.130
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://verisignsecured.com.cn/ 208.80.123.127
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://verisignsecured.com.cn/ 208.80.123.195
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://www.verisignsecured.com.cn/ 69.58.187.75
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://208.80.122.53/ 208.80.122.53
| http://lostredirect.dnsmadeeasy.com/lostredirect.html
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://208.80.122.130/ 208.80.122.130
| http://lostredirect.dnsmadeeasy.com/lostredirect.html
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://208.80.123.127/ 208.80.123.127
| http://lostredirect.dnsmadeeasy.com/lostredirect.html
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://208.80.123.195/ 208.80.123.195
| http://lostredirect.dnsmadeeasy.com/lostredirect.html
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://69.58.187.75/ 69.58.187.75
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| V | https://verisignsecured.com.cn/ 2600:1803:10a::72
|
| Connect failure - perhaps firewall
|
| V | https://verisignsecured.com.cn/ 2600:1803:10b::8
|
| Connect failure - perhaps firewall
|
| V | https://verisignsecured.com.cn/ 2600:1803:10c::8
|
| Connect failure - perhaps firewall
|
| V | https://verisignsecured.com.cn/ 2600:1803:10d::40
|
| Connect failure - perhaps firewall
|
| V | https://[2600:1803:010a:0000:0000:0000:0000:0072]/ 2600:1803:10a::72
|
| Connect failure - perhaps firewall
|
| V | https://[2600:1803:010b:0000:0000:0000:0000:0008]/ 2600:1803:10b::8
|
| Connect failure - perhaps firewall
|
| V | https://[2600:1803:010c:0000:0000:0000:0000:0008]/ 2600:1803:10c::8
|
| Connect failure - perhaps firewall
|
| V | https://[2600:1803:010d:0000:0000:0000:0000:0040]/ 2600:1803:10d::40
|
| Connect failure - perhaps firewall
|
| 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 verisignsecured.com.cn, 8 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.verisignsecured.com.cn
|
| 2. Header-Checks |
| F | www.verisign.com
| X-Content-Type-Options
| Critical: Header with syntax errors found: nosniff,nosniff
|
| F |
|
| Critical: Duplicated values found. Looks like the page sends multiple headers with the same name. nosniff,nosniff
|
| F |
|
| Critical: Unknown token found. Standard-token with additional characters are not defined. nosniff,nosniff
|
| F |
|
| Critical: Unknown token found. Standard-token with additional characters are not defined. nosniff,nosniff
|
| F |
| X-Frame-Options
| Critical: Header with syntax errors found: DENY,DENY
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. DENY,DENY. 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.
|
| F |
|
| Critical: Duplicated values found. Looks like the page sends multiple headers with the same name. DENY,DENY
|
| F |
|
| Critical: Unknown token found. Standard-token with additional characters are not defined. DENY,DENY
|
| F |
|
| Critical: Unknown token found. Standard-token with additional characters are not defined. DENY,DENY
|
| A | www.verisignsecured.com.cn 69.58.187.75
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: DENY
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. DENY. 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.
|
| F | www.verisign.com
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.verisign.com
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.verisign.com
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.verisign.com
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.verisign.com
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.verisign.com
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| F | www.verisignsecured.com.cn 69.58.187.75
| Content-Security-Policy
| Critical: Missing Header:
|
| F | www.verisignsecured.com.cn 69.58.187.75
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.verisignsecured.com.cn 69.58.187.75
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.verisignsecured.com.cn 69.58.187.75
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.verisignsecured.com.cn 69.58.187.75
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.verisignsecured.com.cn 69.58.187.75
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 10 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
|
| A | Info:: 10 Queries complete, 10 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 3 different Name Servers found: a1.verisigndns.com, a2.verisigndns.com, a3.verisigndns.com, 3 Name Servers included in Delegation: a1.verisigndns.com, a2.verisigndns.com, a3.verisigndns.com, 3 Name Servers included in 1 Zone definitions: a1.verisigndns.com, a2.verisigndns.com, a3.verisigndns.com, 1 Name Servers listed in SOA.Primary: a1.verisigndns.com.
|
| A | Good: Only one SOA.Primary Name Server found.: a1.verisigndns.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: a1.verisigndns.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: a1.verisigndns.com, a2.verisigndns.com, a3.verisigndns.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: 3 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 3 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.: 3 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: verisigndns.com
|
| A | Good: Name servers with different Country locations found: 3 Name Servers, 2 Countries: JP, US
|
| A | Info: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 43., 46., 96., 3 different subnets (first two Bytes): 43.247., 46.31., 96.45., 3 different subnets (first three Bytes): 43.247.170., 46.31.236., 96.45.80.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2600:, 3 different subnets (first two blocks): 2600:180a:, 2600:180b:, 2600:180c:, 3 different subnets (first three blocks): 2600:180a:1001:, 2600:180b:2001:, 2600:180c:3001:, 3 different subnets (first four blocks): 2600:180a:1001:0000:, 2600:180b:2001:0000:, 2600:180c:3001:0000:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 6 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 6 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: a.dns.cn: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: a.dns.cn / 203.119.25.1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: a.dns.cn / 2001:dc7::1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: b.dns.cn / 2001:dc7:1::1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: c.dns.cn: OP100: ok. FLAGS: fatal timeout. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: c.dns.cn / 203.119.27.1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: c.dns.cn / 2001:dc7:2::1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: d.dns.cn: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: d.dns.cn / 203.119.28.1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: d.dns.cn / 2001:dc7:1000::1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: e.dns.cn: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: e.dns.cn / 203.119.29.1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: e.dns.cn / 2001:dc7:3::1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: digicert.com is allowed to create certificates
|
| 4. Content- and Performance-critical Checks |
| http://www.verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 69.58.187.75
|
| 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.
|
| https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de&loc=en_US
|
| 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.
|
| https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn&loc=en_US
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de&loc=en_US
|
| Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
|
| https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn&loc=en_US
|
| 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://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de&loc=en_US
|
| 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://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn&loc=en_US
|
| 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://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de&loc=en_US
|
| 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://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn&loc=en_US
|
| 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.
|
| https://www.verisignsecured.com.cn/ 69.58.187.75
|
| 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.
|
| https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de&loc=en_US
|
| 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.
|
| https://69.58.187.75/ 69.58.187.75
|
| 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: Some script Elements (type text/javascript) with a src-Attribute have a defer / async - Attribute. So loading and executing these JavaScripts doesn't block parsing and rendering the Html-Output.
|
| https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn&loc=en_US
|
| 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.
|
| https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de&loc=en_US
|
| 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 Compression. Compress these ressources, gzip, deflate, br are checked. 2 external CSS / JavaScript files without Compression found - 10 with Compression, 12 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, 12 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 12 complete.
|
| Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 image 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 | Good: Some img-elements have a valid alt-attribute.: 4 img-elements found, 2 img-elements with correct alt-attributes (defined, not an empty value).
|
| Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 2 img-elements without alt-attribute, 0 img-elements with empty alt-attribute 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://www.verisignsecured.com.cn/ 69.58.187.75
| Strict-Transport-Security: max-age=31536000; includeSubDomains;
| Parse Error - Header can't be parsed
|
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Strict-Transport-Security: max-age=31536000; includeSubDomains;
| Parse Error - Header can't be parsed
|
| https://www.verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn
| Strict-Transport-Security: max-age=31536000; includeSubDomains;
| Parse Error - Header can't be parsed
|
| https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn&loc=en_US
| Strict-Transport-Security: max-age=31536000; includeSubDomains;
| Parse Error - Header can't be parsed
|
| https://www.verisignsecured.com.cn/ 69.58.187.75
| Strict-Transport-Security: max-age=31536000; includeSubDomains;
| Parse Error - Header can't be parsed
|
| http://www.verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 69.58.187.75
| Strict-Transport-Security: max-age=31536000; includeSubDomains;
| Parse Error - Header can't be parsed
|
| https://verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Strict-Transport-Security: max-age=31536000; includeSubDomains;
| Parse Error - Header can't be parsed
|
| https://www.verisign.com/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Strict-Transport-Security: max-age=31536000; includeSubDomains;
| Parse Error - Header can't be parsed
|
| https://www.verisign.com/en_US/website-presence/online/ssl-certificates/index.xhtml?dmn=verisignsecured.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de&loc=en_US
| Strict-Transport-Security: max-age=31536000; includeSubDomains;
| Parse Error - Header can't be parsed
|
| https://69.58.187.75/ 69.58.187.75
| Strict-Transport-Security: max-age=31536000; includeSubDomains;
| Parse Error - Header can't be parsed
|
| http://www.verisignsecured.com.cn/ 69.58.187.75
|
| Warning: HSTS header sent via http has no effect
|
| A | Info: Different Server-Headers found
|
| A | Duration: 408900 milliseconds, 408.900 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)