| 1. General Results, most used to calculate the result |
A | name "xieyonghui.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
|
A | Good: All ip addresses are public addresses
|
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: every https has a Strict Transport Security Header
|
A | Good: HSTS max-age is long enough, 31536000 seconds = 365 days
|
| 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 | http://xieyonghui.com/ 39.98.58.173
| https://xieyonghui.com/
| Correct redirect http - https with the same domain name
|
X | Fatal error: Nameserver doesn't support TCP connection: dns10.hichina.com / 106.11.141.116: Timeout
|
X | Fatal error: Nameserver doesn't support TCP connection: dns10.hichina.com / 106.11.141.126: Fatal error (0)
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
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: dns10.hichina.com,dns9.hichina.com
|
X | Nameserver Timeout checking Echo Capitalization: dns10.hichina.com / 106.11.141.116
|
X | Nameserver Timeout checking Echo Capitalization: dns10.hichina.com / 106.11.141.126
|
X | Nameserver Timeout checking Echo Capitalization: dns10.hichina.com / 140.205.41.16
|
X | Nameserver Timeout checking Echo Capitalization: dns10.hichina.com / 2400:3200:2000:29::1
|
X | Nameserver Timeout checking Echo Capitalization: dns9.hichina.com / 2400:3200:2000:28::1
|
X | Nameserver Timeout checking EDNS512: dns10.hichina.com / 106.11.141.116
|
X | Nameserver Timeout checking EDNS512: dns10.hichina.com / 106.11.211.66
|
X | Nameserver Timeout checking EDNS512: dns10.hichina.com / 2400:3200:2000:29::1
|
X | Nameserver Timeout checking EDNS512: dns9.hichina.com / 2400:3200:2000:28::1
|
| Nameserver doesn't pass all EDNS-Checks: dns10.hichina.com / 106.11.141.116: OP100: fatal timeout. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: ok. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: dns10.hichina.com / 106.11.141.126: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok. COOKIE: fatal timeout. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: dns10.hichina.com / 106.11.211.56: OP100: ok. FLAGS: fatal timeout. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: dns10.hichina.com / 106.11.211.66: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: fatal timeout. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: dns10.hichina.com / 140.205.41.26: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: dns10.hichina.com / 140.205.81.16: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: dns10.hichina.com / 2400:3200:2000:29::1: OP100: fatal timeout. FLAGS: fatal timeout. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: dns9.hichina.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: dns9.hichina.com / 2400:3200:2000:28::1: OP100: ok. FLAGS: fatal timeout. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
A | Good: All SOA have the same Serial Number
|
A | Good: CAA entries found, creating certificate is limited: no CAA is allowed to create certificates
|
A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create wildcard-certificates
|
| 4. Content- and Performance-critical Checks |
| https://xieyonghui.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| https://xieyonghui.com/ 39.98.58.173
|
| 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://xieyonghui.com/ 39.98.58.173
|
| 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://xieyonghui.com/ 39.98.58.173
|
| 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.
|
| Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 1 external CSS / JavaScript files without GZip found - 5 with GZip, 6 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, 2 with Cache-Control max-age too short (minimum 7 days), 4 with Cache-Control long enough, 6 complete.
|
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: 280353 milliseconds, 280.353 seconds
|