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



N

No trusted Certificate

Checked:
21.05.2019 10:02:14


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
clothestar.com
A
35.225.36.127
Hostname: 127.36.225.35.bc.googleusercontent.com
yes
2
0

AAAA

yes


www.clothestar.com
CNAME
clothestar.com
yes
1
0

A
35.225.36.127
Hostname: 127.36.225.35.bc.googleusercontent.com
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



Status: Valid because published



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 25266, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.06.2019, 00:00:00 +, Signature-Inception: 21.05.2019, 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



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.06.2019, 05:00:00 +, Signature-Inception: 21.05.2019, 04:00:00 +, KeyTag 25266, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 3800, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.05.2019, 18:25:33 +, Signature-Inception: 12.05.2019, 18:20:33 +, KeyTag 30909, Signer-Name: com



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



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

Zone: clothestar.com
clothestar.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "qebdspj1kb17big296aitl2dgrit5ugt" between the hashed NSEC3-owner "qebapduom52lfo3qo7asvcp4ivdpl93e" and the hashed NextOwner "qebecojd0s5rq11blorrnlai9jrte0hh". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner qebapduom52lfo3qo7asvcp4ivdpl93e.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 28.05.2019, 04:52:46 +, Signature-Inception: 21.05.2019, 03:42:46 +, KeyTag 3800, Signer-Name: com



0 DNSKEY RR found




Zone: www.clothestar.com
www.clothestar.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
clothestar.com
  ns-cloud-a1.googledomains.com
216.239.32.106

 
2001:4860:4802:32::6a

  ns-cloud-a2.googledomains.com
216.239.34.106

 
2001:4860:4802:34::6a

  ns-cloud-a3.googledomains.com
216.239.36.106

 
2001:4860:4802:36::6a

  ns-cloud-a4.googledomains.com
216.239.38.106

 
2001:4860:4802:38::6a
com
  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


4. SOA-Entries


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


Domain:clothestar.com
Zone-Name:
Primary:ns-cloud-a1.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://clothestar.com/
35.225.36.127
301
https://clothestar.com/
1.790
A
Date: Tue, 21 May 2019 08:02:50 GMT
Server: Apache
X-Redirect-By: WordPress
Location: https://clothestar.com/
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• http://www.clothestar.com/
35.225.36.127
301
https://clothestar.com/
0.780
E
Date: Tue, 21 May 2019 08:02:52 GMT
Server: Apache
X-Redirect-By: WordPress
Location: https://clothestar.com/
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• https://www.clothestar.com/
35.225.36.127
301
https://clothestar.com/
1.983
N
Certificate error: RemoteCertificateChainErrors
Date: Tue, 21 May 2019 08:03:10 GMT
Server: Apache
X-Redirect-By: WordPress
Location: https://clothestar.com/
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8

• https://clothestar.com/
35.225.36.127
-14

16.983
T
Timeout - The operation has timed out.

• http://clothestar.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
35.225.36.127
404

0.236
A
Not Found
Visible Content:
Date: Tue, 21 May 2019 08:03:12 GMT
Server: Apache
Content-Length: 267
Connection: close
Content-Type: text/html; charset=iso-8859-1

• http://www.clothestar.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
35.225.36.127
404

0.236
A
Not Found
Visible Content:
Date: Tue, 21 May 2019 08:03:12 GMT
Server: Apache
Content-Length: 267
Connection: close
Content-Type: text/html; charset=iso-8859-1

7. Comments


1. General Results, most used to calculate the result

Aname "clothestar.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Bhttps://www.clothestar.com/ 35.225.36.127
301

Missing HSTS-Header
CError - no version with Http-Status 200
Ehttp://www.clothestar.com/ 35.225.36.127
301
https://clothestar.com/
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.
Hfatal error: No https - result with http-status 200, no encryption
Nhttps://www.clothestar.com/ 35.225.36.127
301
https://clothestar.com/
Error - Certificate isn't trusted, RemoteCertificateChainErrors
OOld connection: SHA1 as Hash Algorithm is deprecated. Switch to SHA256 or SHA384. If your certificate has SHA256, first check your domain via ssllabs.com and update weak Cipher Suites. Forward Secrecy support is required. The part "Cipher Suites" should have a preference. First Cipher Suite with SHA instead of SHA256 or higher - that's the problem, change that. If that doesn't help, check if there is an old Firewall / router or something else, that supports only SHA1. Update that component.

2. DNS- and NameServer - Checks

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.

3. 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.
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: 58383 milliseconds, 58.383 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
www.clothestar.com
35.225.36.127
443
Certificate/chain invalid
Tls12
ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
www.clothestar.com
35.225.36.127
443
Certificate/chain invalid
Tls12

ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete
1CN=clothestar.com

2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


9. Certificates

1.
1.
CN=clothestar.com
22.12.2018
22.03.2019
1200 days expired
clothestar.com, www.clothestar.com - 2 entries
1.
1.
CN=clothestar.com
22.12.2018

22.03.2019
1200 days expired
clothestar.com, www.clothestar.com - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03E9A6DA7682A55664AB835B34208471CA80
Thumbprint:AB53C16F72A575EB57173926656F5E8C2B6FAAD8
SHA256 / Certificate:Js7L1k6QvXwkrLQtvaBWKPuYSfMpwsm38n2cRMFopME=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):dc7f4b2005c6382a5344bb7e3172e3d517e021d758a2d1c2d545990d97a8ed6e
SHA256 hex / Subject Public Key Information (SPKI):dc7f4b2005c6382a5344bb7e3172e3d517e021d758a2d1c2d545990d97a8ed6e
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Server Authentication (1.3.6.1.5.5.7.3.1), Client Authentication (1.3.6.1.5.5.7.3.2)

NotTimeValid: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
RevocationStatusUnknown: The revocation function was unable to check revocation for the certificate.
OfflineRevocation: The revocation function was unable to check revocation because the revocation server was offline.

2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
474 days expired


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
474 days expired


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
277 days expired


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
277 days expired


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:



10. Last Certificates - Certificate Transparency Log Check

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

No CertSpotter - CT-Log entries found


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

No CRT - CT-Log entries found


11. Html-Content - Entries

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


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.clothestar.com



1
0
clothestar.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
clothestar.com

ok
1
0
www.clothestar.com


1
0
_acme-challenge.clothestar.com

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

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

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

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

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.



Permalink: https://check-your-website.server-daten.de/?i=548e93f0-289e-46ff-a2d3-7827aa14e578


Last Result: https://check-your-website.server-daten.de/?q=clothestar.com - 2019-05-21 10:02:14


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

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