Check DNS, Urls + Redirects, Certificates and Content of your Website

0 in Queue, 2 of max. 8 Checks (22:17:31)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

Q

 

http sent over port 443

 

Checked:
29.10.2025 19:58:33

 

Older results

 

Q - 29.10.2025 05:28:48
Q - 29.10.2025 05:24:25

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
xiaoguachinese.com
A
34.143.215.65
Singapore/Central Singapore/Singapore (SG) - Google LLC
Hostname: 65.215.143.34.bc.googleusercontent.com
yes
1
0

AAAA

yes


www.xiaoguachinese.com
CNAME
www.xiaoguachinese.com
yes
1
0

CNAME
www.xiaoguachinese.com
yes


*.xiaoguachinese.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=






• Status: Valid because published






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 38696, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 61809, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.11.2025, 00:00:00 +, Signature-Inception: 21.10.2025, 00:00:00 +, KeyTag 20326, Signer-Name: (root)






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: com

com
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=






1 RRSIG RR to validate DS RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 11.11.2025, 17:00:00 +, Signature-Inception: 29.10.2025, 16:00:00 +, KeyTag 61809, Signer-Name: (root)






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 61809 used to validate the DS RRSet in the parent zone






2 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 19718, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 13, KeyTag 46539, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 13.11.2025, 14:02:35 +, Signature-Inception: 29.10.2025, 13:57:35 +, KeyTag 19718, Signer-Name: com






• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 19718 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest "isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: xiaoguachinese.com

xiaoguachinese.com
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 51410, DigestType 2 and Digest oXrUjqZFUM+F4BBqlT6yMPSww6ZviweS3hrFfXjqldo=






1 RRSIG RR to validate DS RR found






RRSIG-Owner xiaoguachinese.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 05.11.2025, 04:23:01 +, Signature-Inception: 29.10.2025, 03:13:01 +, KeyTag 46539, Signer-Name: com






• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 46539 used to validate the DS RRSet in the parent zone






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 44445, Flags 256






Public Key with Algorithm 8, KeyTag 51410, Flags 257 (SEP = Secure Entry Point)






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner xiaoguachinese.com., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 19.11.2025, 04:23:00 +, Signature-Inception: 28.10.2025, 04:23:00 +, KeyTag 51410, Signer-Name: xiaoguachinese.com






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 51410 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 51410, DigestType 2 and Digest "oXrUjqZFUM+F4BBqlT6yMPSww6ZviweS3hrFfXjqldo=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone






RRSIG Type 1 validates the A - Result: 34.143.215.65
Validated: RRSIG-Owner xiaoguachinese.com., Algorithm: 8, 2 Labels, original TTL: 14400 sec, Signature-expiration: 19.11.2025, 04:23:00 +, Signature-Inception: 28.10.2025, 04:23:00 +, KeyTag 44445, Signer-Name: xiaoguachinese.com






RRSIG Type 16 validates the TXT - Result: v=spf1 -all
Validated: RRSIG-Owner xiaoguachinese.com., Algorithm: 8, 2 Labels, original TTL: 14400 sec, Signature-expiration: 19.11.2025, 04:23:00 +, Signature-Inception: 28.10.2025, 04:23:00 +, KeyTag 44445, Signer-Name: xiaoguachinese.com






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "iu1e9ccihdcs3vprucr27oncpikogcb0" equal the hashed NSEC3-owner "iu1e9ccihdcs3vprucr27oncpikogcb0" and the hashed NextOwner "o28emtkrj5mg1jdq1l31pltb2oh41bgb". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS, 65 Validated: RRSIG-Owner iu1e9ccihdcs3vprucr27oncpikogcb0.xiaoguachinese.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 19.11.2025, 04:23:00 +, Signature-Inception: 28.10.2025, 04:23:00 +, KeyTag 44445, Signer-Name: xiaoguachinese.com






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "iu1e9ccihdcs3vprucr27oncpikogcb0" equal the hashed NSEC3-owner "iu1e9ccihdcs3vprucr27oncpikogcb0" and the hashed NextOwner "o28emtkrj5mg1jdq1l31pltb2oh41bgb". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS, 65 Validated: RRSIG-Owner iu1e9ccihdcs3vprucr27oncpikogcb0.xiaoguachinese.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 19.11.2025, 04:23:00 +, Signature-Inception: 28.10.2025, 04:23:00 +, KeyTag 44445, Signer-Name: xiaoguachinese.com






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.xiaoguachinese.com) sends a valid NSEC3 RR as result with the hashed owner name "iu1e9ccihdcs3vprucr27oncpikogcb0" (unhashed: xiaoguachinese.com). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS, 65 Validated: RRSIG-Owner iu1e9ccihdcs3vprucr27oncpikogcb0.xiaoguachinese.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 19.11.2025, 04:23:00 +, Signature-Inception: 28.10.2025, 04:23:00 +, KeyTag 44445, Signer-Name: xiaoguachinese.com






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "8cfkktnvf5tkbo8023rdk7oq96rvlop4" (unhashed: _tcp.xiaoguachinese.com) with the owner "t5ugi6u63cgnuvi8m03ac12kpl4luo3i" and the NextOwner "iu1e9ccihdcs3vprucr27oncpikogcb0". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "3u5ogsqj1hqcs85cunabahb844379627" (unhashed: *.xiaoguachinese.com) with the owner "t5ugi6u63cgnuvi8m03ac12kpl4luo3i" and the NextOwner "iu1e9ccihdcs3vprucr27oncpikogcb0". So that NSEC3 confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.xiaoguachinese.com) sends a valid NSEC3 RR as result with the owner name "t5ugi6u63cgnuvi8m03ac12kpl4luo3i" greater the NextOwner-Name "iu1e9ccihdcs3vprucr27oncpikogcb0", so the NSEC3 covers the end of the zone. The hashed query name "deta1k8k1sg5b9pcbb723i1ejo0unci5" comes before the hashed NextOwner, so the zone confirmes the not-existence of that TLSA RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner t5ugi6u63cgnuvi8m03ac12kpl4luo3i.xiaoguachinese.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 19.11.2025, 04:23:00 +, Signature-Inception: 28.10.2025, 04:23:00 +, KeyTag 44445, Signer-Name: xiaoguachinese.com






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "iu1e9ccihdcs3vprucr27oncpikogcb0" equal the hashed NSEC3-owner "iu1e9ccihdcs3vprucr27oncpikogcb0" and the hashed NextOwner "o28emtkrj5mg1jdq1l31pltb2oh41bgb". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS, 65 Validated: RRSIG-Owner iu1e9ccihdcs3vprucr27oncpikogcb0.xiaoguachinese.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 19.11.2025, 04:23:00 +, Signature-Inception: 28.10.2025, 04:23:00 +, KeyTag 44445, Signer-Name: xiaoguachinese.com






Status: Good. NoData-Proof required and found.



Zone: www.xiaoguachinese.com

www.xiaoguachinese.com
0 DS RR in the parent zone found






RRSIG Type 5 validates the CNAME - Result: www.xiaoguachinese.com
Validated: RRSIG-Owner www.xiaoguachinese.com., Algorithm: 8, 3 Labels, original TTL: 14400 sec, Signature-expiration: 19.11.2025, 04:23:00 +, Signature-Inception: 28.10.2025, 04:23:00 +, KeyTag 44445, Signer-Name: xiaoguachinese.com

 

3. Name Servers

DomainNameserverNS-IP
xiaoguachinese.com
•  ns-cloud-e1.googledomains.com
216.239.32.110
Austell/Georgia/United States (US) - Google LLC		•

• 
2001:4860:4802:32::6e
Montreal/Quebec/Canada (CA) - Google LLC		•

•  ns-cloud-e2.googledomains.com
216.239.34.110
Austell/Georgia/United States (US) - Google LLC		•

• 
2001:4860:4802:34::6e
Montreal/Quebec/Canada (CA) - Google LLC		•

•  ns-cloud-e3.googledomains.com
216.239.36.110
Austell/Georgia/United States (US) - Google LLC		•

• 
2001:4860:4802:36::6e
Montreal/Quebec/Canada (CA) - Google LLC		•

•  ns-cloud-e4.googledomains.com
216.239.38.110
Austell/Georgia/United States (US) - Google LLC		•

• 
2001:4860:4802:38::6e
Montreal/Quebec/Canada (CA) - Google LLC		•
com
•  a.gtld-servers.net / nnn1-par6
•

•  b.gtld-servers.net / nnn1-elwaw4
•

•  c.gtld-servers.net / nnn1-par6
•

•  d.gtld-servers.net / nnn1-par6
•

•  e.gtld-servers.net / nnn1-par6
•

•  f.gtld-servers.net / nnn1-defra-4
•

•  g.gtld-servers.net / nnn1-defra-4
•

•  h.gtld-servers.net / nnn1-defra-4
•

•  i.gtld-servers.net / nnn1-defra-4
•

•  j.gtld-servers.net / nnn1-frmrs-2
•

•  k.gtld-servers.net / nnn1-frmrs-2
•

•  l.gtld-servers.net / nnn1-frmrs-2
•

•  m.gtld-servers.net / nnn1-frmrs-2
•

 

4. SOA-Entries


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1761764289
Refresh:1800
Retry:900
Expire:604800
TTL:900
num Entries:8


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1761764304
Refresh:1800
Retry:900
Expire:604800
TTL:900
num Entries:5


Domain:xiaoguachinese.com
Zone-Name:xiaoguachinese.com
Primary:ns-cloud-e1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:1
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://xiaoguachinese.com/
34.143.215.65 gzip used - 696 / 1113 - 37.47 %
200

Html is minified: 100.18 %
0.547
H
Date: Wed, 29 Oct 2025 18:59:25 GMT
Server: Apache/2.4.65,(Debian)
ETag: "459-641fa19a2e800-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Last-Modified: Sat, 25 Oct 2025 11:38:08 GMT
Content-Encoding: gzip
Content-Length: 696
Content-Type: text/html

• https://xiaoguachinese.com/
34.143.215.65
-103


0.564
P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Cannot determine the frame size or a corrupted frame was received

• http://xiaoguachinese.com:443/
34.143.215.65 gzip used - 3041 / 10701 - 71.58 %
200

Html is minified: 221.69 %
0.540
Q
Visible Content:
Date: Wed, 29 Oct 2025 18:59:27 GMT
Server: Apache/2.4.65,(Debian)
ETag: "29cd-641e933e800f8-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Last-Modified: Fri, 24 Oct 2025 15:28:34 GMT
Content-Encoding: gzip
Content-Length: 3041
Content-Type: text/html

• http://xiaoguachinese.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.143.215.65
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 103.32 %
Other inline scripts (∑/total): 0/0		0.274
A
Not Found
Visible Content:
Date: Wed, 29 Oct 2025 18:59:26 GMT
Server: Apache/2.4.65,(Debian)
Content-Length: 280
Content-Type: text/html; charset=iso-8859-1

• https://34.143.215.65/
34.143.215.65
-103


0.576
P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Cannot determine the frame size or a corrupted frame was received

 

7. Comments


1. General Results, most used to calculate the result

Aname "xiaoguachinese.com" is domain, 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: 108094 (complete: 276475)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: xiaoguachinese.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: xiaoguachinese.com has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
AGood: 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.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):1 complete Content-Type - header (3 urls)
http://xiaoguachinese.com/ 34.143.215.65


Url with incomplete Content-Type - header - missing charset
http://xiaoguachinese.com:443/ 34.143.215.65


Url with incomplete Content-Type - header - missing charset
HFatal error: No https - result with http-status 200, no encryption
HFatal 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.
Qhttp://xiaoguachinese.com:443/ 34.143.215.65
200

Misconfiguration: http sent over port 443. Wrong port forwarding port 443 to port 80 or wrong vHost definition. If you use a virtual Host <VirtualHost ip-address:443>, try <VirtualHost *:443>.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain xiaoguachinese.com, 1 ip addresses.
BNo _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.xiaoguachinese.com

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 13 Queries complete, 13 with IPv6, 0 with IPv4.
AGood: 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.
AInfo:: 4 different Name Servers found: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-e1.googledomains.com.
AGood: Only one SOA.Primary Name Server found.: ns-cloud-e1.googledomains.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-cloud-e1.googledomains.com.
AGood: 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: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 4 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.: 4 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: googledomains.com
AGood: Name servers with different Country locations found: 4 Name Servers, 2 Countries: CA, US
AInfo: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 216., 1 different subnets (first two Bytes): 216.239., 4 different subnets (first three Bytes): 216.239.32., 216.239.34., 216.239.36., 216.239.38.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:4860:, 1 different subnets (first three blocks): 2001:4860:4802:, 4 different subnets (first four blocks): 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2001:4860:4802:0036:, 2001:4860:4802:0038:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
AGood: 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

AGood: 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.
AInfo: No img element found, no alt attribute checked
AGood: 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
ADuration: 80600 milliseconds, 80.600 seconds

 

8. Connections

No connection informations found. Perhaps only http - connections.

 

9. Certificates

No certificate informations found. Perhaps only http - connections.

 

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Issuerlast 7 daysactivenum Certs
CN=R12, O=Let's Encrypt, C=US
0
2
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
12485836021
leaf cert		CN=R12, O=Let's Encrypt, C=US
2025-10-28 12:00:45
2026-01-26 12:00:44
www.xiaoguachinese.com - 1 entries


12485835286
leaf cert		CN=R12, O=Let's Encrypt, C=US
2025-10-28 12:00:44
2026-01-26 12:00:43
xiaoguachinese.com - 1 entries


 

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

Issuerlast 7 daysactivenum Certs
CN=R12, O=Let's Encrypt, C=US
0
2
2

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
22062175412
leaf cert		CN=R12, O=Let's Encrypt, C=US
2025-10-28 11:00:45
2026-01-26 11:00:44
www.xiaoguachinese.com
1 entries


22062172463
leaf cert		CN=R12, O=Let's Encrypt, C=US
2025-10-28 11:00:44
2026-01-26 11:00:43
xiaoguachinese.com
1 entries


 

11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404

 

12. Html-Parsing via https://validator.w3.org/nu/


No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com

 

QNr.DomainTypeNS used
1
com
NS
e.root-servers.net (2001:500:a8::e)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
ns-cloud-e1.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
3
ns-cloud-e2.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
4
ns-cloud-e3.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
5
ns-cloud-e4.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
6
ns-cloud-e1.googledomains.com: 216.239.32.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
7
ns-cloud-e1.googledomains.com: 2001:4860:4802:32::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
8
ns-cloud-e2.googledomains.com: 216.239.34.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
9
ns-cloud-e2.googledomains.com: 2001:4860:4802:34::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
10
ns-cloud-e3.googledomains.com: 216.239.36.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
11
ns-cloud-e3.googledomains.com: 2001:4860:4802:36::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
12
ns-cloud-e4.googledomains.com: 216.239.38.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
13
ns-cloud-e4.googledomains.com: 2001:4860:4802:38::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.xiaoguachinese.com



1
0
xiaoguachinese.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
xiaoguachinese.com
v=spf1 -all
ok
1
0
www.xiaoguachinese.com


1
0
_acme-challenge.xiaoguachinese.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.xiaoguachinese.com

Name Error - The domain name does not exist
1
0
_acme-challenge.xiaoguachinese.com.xiaoguachinese.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.xiaoguachinese.com.xiaoguachinese.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.xiaoguachinese.com.www.xiaoguachinese.com

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
SPF
TXT
xiaoguachinese.com

v=spf1 -all
ok
_dmarc
TXT
_dmarc.xiaoguachinese.com

v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s
ok

 

 

17. Cipher Suites

No results

 

18. Portchecks

DomainIPPortDescriptionResultAnswer
xiaoguachinese.com
34.143.215.65
21
FTP



xiaoguachinese.com
34.143.215.65
21
FTP



xiaoguachinese.com
34.143.215.65
22
SSH
open
SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u7

xiaoguachinese.com
34.143.215.65
22
SSH
open
SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u7
Bad: SSH without DNS SSHFP Record found
xiaoguachinese.com
34.143.215.65
25
SMTP



xiaoguachinese.com
34.143.215.65
25
SMTP



xiaoguachinese.com
34.143.215.65
53
DNS



xiaoguachinese.com
34.143.215.65
53
DNS



xiaoguachinese.com
34.143.215.65
110
POP3



xiaoguachinese.com
34.143.215.65
110
POP3



xiaoguachinese.com
34.143.215.65
143
IMAP



xiaoguachinese.com
34.143.215.65
143
IMAP



xiaoguachinese.com
34.143.215.65
465
SMTP (encrypted)



xiaoguachinese.com
34.143.215.65
465
SMTP (encrypted)



xiaoguachinese.com
34.143.215.65
587
SMTP (encrypted, submission)



xiaoguachinese.com
34.143.215.65
587
SMTP (encrypted, submission)



xiaoguachinese.com
34.143.215.65
993
IMAP (encrypted)



xiaoguachinese.com
34.143.215.65
993
IMAP (encrypted)



xiaoguachinese.com
34.143.215.65
995
POP3 (encrypted)



xiaoguachinese.com
34.143.215.65
995
POP3 (encrypted)



xiaoguachinese.com
34.143.215.65
1433
MS SQL



xiaoguachinese.com
34.143.215.65
1433
MS SQL



xiaoguachinese.com
34.143.215.65
2082
cPanel (http)



xiaoguachinese.com
34.143.215.65
2082
cPanel (http)



xiaoguachinese.com
34.143.215.65
2083
cPanel (https)



xiaoguachinese.com
34.143.215.65
2083
cPanel (https)



xiaoguachinese.com
34.143.215.65
2086
WHM (http)



xiaoguachinese.com
34.143.215.65
2086
WHM (http)



xiaoguachinese.com
34.143.215.65
2087
WHM (https)



xiaoguachinese.com
34.143.215.65
2087
WHM (https)



xiaoguachinese.com
34.143.215.65
2089
cPanel Licensing



xiaoguachinese.com
34.143.215.65
2089
cPanel Licensing



xiaoguachinese.com
34.143.215.65
2095
cPanel Webmail (http)



xiaoguachinese.com
34.143.215.65
2095
cPanel Webmail (http)



xiaoguachinese.com
34.143.215.65
2096
cPanel Webmail (https)



xiaoguachinese.com
34.143.215.65
2096
cPanel Webmail (https)



xiaoguachinese.com
34.143.215.65
2222
DirectAdmin (http)



xiaoguachinese.com
34.143.215.65
2222
DirectAdmin (http)



xiaoguachinese.com
34.143.215.65
2222
DirectAdmin (https)



xiaoguachinese.com
34.143.215.65
2222
DirectAdmin (https)



xiaoguachinese.com
34.143.215.65
3306
mySql



xiaoguachinese.com
34.143.215.65
3306
mySql



xiaoguachinese.com
34.143.215.65
5224
Plesk Licensing



xiaoguachinese.com
34.143.215.65
5224
Plesk Licensing



xiaoguachinese.com
34.143.215.65
5432
PostgreSQL
open


xiaoguachinese.com
34.143.215.65
5432
PostgreSQL
open


xiaoguachinese.com
34.143.215.65
8080
Ookla Speedtest (http)



xiaoguachinese.com
34.143.215.65
8080
Ookla Speedtest (http)



xiaoguachinese.com
34.143.215.65
8080
Ookla Speedtest (https)



xiaoguachinese.com
34.143.215.65
8080
Ookla Speedtest (https)



xiaoguachinese.com
34.143.215.65
8083
VestaCP http



xiaoguachinese.com
34.143.215.65
8083
VestaCP http



xiaoguachinese.com
34.143.215.65
8083
VestaCP https



xiaoguachinese.com
34.143.215.65
8083
VestaCP https



xiaoguachinese.com
34.143.215.65
8443
Plesk Administration (https)



xiaoguachinese.com
34.143.215.65
8443
Plesk Administration (https)



xiaoguachinese.com
34.143.215.65
8447
Plesk Installer + Updates



xiaoguachinese.com
34.143.215.65
8447
Plesk Installer + Updates



xiaoguachinese.com
34.143.215.65
8880
Plesk Administration (http)



xiaoguachinese.com
34.143.215.65
8880
Plesk Administration (http)



xiaoguachinese.com
34.143.215.65
10000
Webmin (http)



xiaoguachinese.com
34.143.215.65
10000
Webmin (http)



xiaoguachinese.com
34.143.215.65
10000
Webmin (https)



xiaoguachinese.com
34.143.215.65
10000
Webmin (https)



 

 

Permalink: https://check-your-website.server-daten.de/?i=e3e3f76b-9c71-4a3f-8ff6-3a908459ed4a

 

Last Result: https://check-your-website.server-daten.de/?q=xiaoguachinese.com - 2025-10-29 19:58:33

 

Do you like this page? Support this tool, add a link on your page:

 

<a href="https://check-your-website.server-daten.de/?q=xiaoguachinese.com" target="_blank">Check this Site: xiaoguachinese.com</a>

 

 

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=xiaoguachinese.com

 

 

Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • USt-IdNr.: DE221734518

 

Errors, ideas, questions? Use the Contact form • A project using Server-Daten - Web Database solutions