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


 

 

A

 

Top config

 

Checked:
12.04.2022 08:56:37

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
clinicaltrials.hearthealthtech.com
A
35.200.238.249
Mumbai/Maharashtra/India (IN) - Google LLC
Hostname: 249.238.200.35.bc.googleusercontent.com
yes
1
0

AAAA

yes


www.clinicaltrials.hearthealthtech.com

Name Error
yes
1
0
*.hearthealthtech.com
A
174.138.121.24
yes



AAAA

yes



CNAME

yes


*.clinicaltrials.hearthealthtech.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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 47671, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 02.05.2022, 00:00:00 +, Signature-Inception: 11.04.2022, 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 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=






1 RRSIG RR to validate DS RR found






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






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






3 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 37269, Flags 256






Public Key with Algorithm 8, KeyTag 38535, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 20.04.2022, 18:24:21 +, Signature-Inception: 05.04.2022, 18:19:21 +, 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: hearthealthtech.com

hearthealthtech.com
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 32014, DigestType 2 and Digest ArF2ZniQY7gVUfccDKTxS4/GVZcK0GwnSJGxOUzqKPM=






1 RRSIG RR to validate DS RR found






RRSIG-Owner hearthealthtech.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 19.04.2022, 04:29:52 +, Signature-Inception: 12.04.2022, 03:19:52 +, KeyTag 38535, Signer-Name: com






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 17505, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner hearthealthtech.com., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 02.05.2022, 21:00:11 +, Signature-Inception: 10.04.2022, 21:00:11 +, KeyTag 32014, Signer-Name: hearthealthtech.com






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






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



Zone: clinicaltrials.hearthealthtech.com

clinicaltrials.hearthealthtech.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 "78iasdchev8vdkcemqkvviufeqfvc9j1" between the hashed NSEC3-owner "78iasdchev8vdkcemqkvviufeqfvc9j1" and the hashed NextOwner "a2045hdqcik1epgtr036pudnkhldr51a". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner 78iasdchev8vdkcemqkvviufeqfvc9j1.hearthealthtech.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.05.2022, 21:00:11 +, Signature-Inception: 10.04.2022, 21:00:11 +, KeyTag 17505, Signer-Name: hearthealthtech.com






0 DNSKEY RR found












RRSIG Type 1 validates the A - Result: 35.200.238.249
Validated: RRSIG-Owner clinicaltrials.hearthealthtech.com., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 02.05.2022, 21:00:11 +, Signature-Inception: 10.04.2022, 21:00:11 +, KeyTag 17505, Signer-Name: hearthealthtech.com






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "78iasdchev8vdkcemqkvviufeqfvc9j1" equal the hashed NSEC3-owner "78iasdchev8vdkcemqkvviufeqfvc9j1" and the hashed NextOwner "a2045hdqcik1epgtr036pudnkhldr51a". 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, RRSIG Validated: RRSIG-Owner 78iasdchev8vdkcemqkvviufeqfvc9j1.hearthealthtech.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.05.2022, 21:00:11 +, Signature-Inception: 10.04.2022, 21:00:11 +, KeyTag 17505, Signer-Name: hearthealthtech.com






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed query name "78iasdchev8vdkcemqkvviufeqfvc9j1" equal the hashed NSEC3-owner "78iasdchev8vdkcemqkvviufeqfvc9j1" and the hashed NextOwner "a2045hdqcik1epgtr036pudnkhldr51a". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner 78iasdchev8vdkcemqkvviufeqfvc9j1.hearthealthtech.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.05.2022, 21:00:11 +, Signature-Inception: 10.04.2022, 21:00:11 +, KeyTag 17505, Signer-Name: hearthealthtech.com






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "78iasdchev8vdkcemqkvviufeqfvc9j1" equal the hashed NSEC3-owner "78iasdchev8vdkcemqkvviufeqfvc9j1" and the hashed NextOwner "a2045hdqcik1epgtr036pudnkhldr51a". 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, RRSIG Validated: RRSIG-Owner 78iasdchev8vdkcemqkvviufeqfvc9j1.hearthealthtech.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.05.2022, 21:00:11 +, Signature-Inception: 10.04.2022, 21:00:11 +, KeyTag 17505, Signer-Name: hearthealthtech.com






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.clinicaltrials.hearthealthtech.com) sends a valid NSEC3 RR as result with the hashed owner name "78iasdchev8vdkcemqkvviufeqfvc9j1" (unhashed: clinicaltrials.hearthealthtech.com). So that's the Closest Encloser of the query name.
Bitmap: A, RRSIG Validated: RRSIG-Owner 78iasdchev8vdkcemqkvviufeqfvc9j1.hearthealthtech.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.05.2022, 21:00:11 +, Signature-Inception: 10.04.2022, 21:00:11 +, KeyTag 17505, Signer-Name: hearthealthtech.com






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "33eiqv13tia12tfqr8hcn3njf5tgia4o" (unhashed: _tcp.clinicaltrials.hearthealthtech.com) with the owner "vodtj49d4g42971lrp7orif9fritin3l" and the NextOwner "3ckjc1n7jlj7vdhvrqg02c8463jhlkvl". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, RRSIG Validated: RRSIG-Owner vodtj49d4g42971lrp7orif9fritin3l.hearthealthtech.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.05.2022, 21:00:11 +, Signature-Inception: 10.04.2022, 21:00:11 +, KeyTag 17505, Signer-Name: hearthealthtech.com






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "m30t4rnejp2of7kgi9kk0nna9qgmshci" (unhashed: *.clinicaltrials.hearthealthtech.com) with the owner "dcvn7qt4dal6nf7lpmc7i2i81696d5mv" and the NextOwner "qfcvb6ro4pfr6b7atksnnm290hl78jeh". So that NSEC3 confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.clinicaltrials.hearthealthtech.com) sends a valid NSEC3 RR as result with the hashed query name "irp463a41lv6vo482rl0mhogee6rj86j" between the hashed NSEC3-owner "dcvn7qt4dal6nf7lpmc7i2i81696d5mv" and the hashed NextOwner "qfcvb6ro4pfr6b7atksnnm290hl78jeh". So the zone confirmes the not-existence of that TLSA RR.
Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner dcvn7qt4dal6nf7lpmc7i2i81696d5mv.hearthealthtech.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.05.2022, 21:00:11 +, Signature-Inception: 10.04.2022, 21:00:11 +, KeyTag 17505, Signer-Name: hearthealthtech.com






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "78iasdchev8vdkcemqkvviufeqfvc9j1" equal the hashed NSEC3-owner "78iasdchev8vdkcemqkvviufeqfvc9j1" and the hashed NextOwner "a2045hdqcik1epgtr036pudnkhldr51a". 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, RRSIG Validated: RRSIG-Owner 78iasdchev8vdkcemqkvviufeqfvc9j1.hearthealthtech.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.05.2022, 21:00:11 +, Signature-Inception: 10.04.2022, 21:00:11 +, KeyTag 17505, Signer-Name: hearthealthtech.com






Status: Good. NoData-Proof required and found.



Zone: www.clinicaltrials.hearthealthtech.com

www.clinicaltrials.hearthealthtech.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 "jvrsdanfcsn1kv05mjqlftjuehc0150j" between the hashed NSEC3-owner "dcvn7qt4dal6nf7lpmc7i2i81696d5mv" and the hashed NextOwner "qfcvb6ro4pfr6b7atksnnm290hl78jeh". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner dcvn7qt4dal6nf7lpmc7i2i81696d5mv.hearthealthtech.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.05.2022, 21:00:11 +, Signature-Inception: 10.04.2022, 21:00:11 +, KeyTag 17505, Signer-Name: hearthealthtech.com






Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner dcvn7qt4dal6nf7lpmc7i2i81696d5mv.hearthealthtech.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.05.2022, 21:00:11 +, Signature-Inception: 10.04.2022, 21:00:11 +, KeyTag 17505, Signer-Name: hearthealthtech.com






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "78iasdchev8vdkcemqkvviufeqfvc9j1" as Owner. That's the Hash of "clinicaltrials.hearthealthtech.com" with the NextHashedOwnerName "a2045hdqcik1epgtr036pudnkhldr51a". So that domain name is the Closest Encloser of "www.clinicaltrials.hearthealthtech.com". Opt-Out: False.
Bitmap: A, RRSIG Validated: RRSIG-Owner 78iasdchev8vdkcemqkvviufeqfvc9j1.hearthealthtech.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.05.2022, 21:00:11 +, Signature-Inception: 10.04.2022, 21:00:11 +, KeyTag 17505, Signer-Name: hearthealthtech.com






The ClosestEncloser says, that "*.clinicaltrials.hearthealthtech.com" with the Hash "m30t4rnejp2of7kgi9kk0nna9qgmshci" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "dcvn7qt4dal6nf7lpmc7i2i81696d5mv" and the Next Owner "qfcvb6ro4pfr6b7atksnnm290hl78jeh", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner dcvn7qt4dal6nf7lpmc7i2i81696d5mv.hearthealthtech.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.05.2022, 21:00:11 +, Signature-Inception: 10.04.2022, 21:00:11 +, KeyTag 17505, Signer-Name: hearthealthtech.com

 

3. Name Servers

DomainNameserverNS-IP
www.clinicaltrials.hearthealthtech.com
  ns-cloud-a1.googledomains.com

clinicaltrials.hearthealthtech.com
  ns-cloud-a1.googledomains.com
2001:4860:4802:32::6a
Mountain View/California/United States (US) - Google LLC

hearthealthtech.com
  ns-cloud-a1.googledomains.com
2001:4860:4802:32::6a
Mountain View/California/United States (US) - Google LLC


  ns-cloud-a2.googledomains.com
2001:4860:4802:34::6a
Mountain View/California/United States (US) - Google LLC


  ns-cloud-a3.googledomains.com
2001:4860:4802:36::6a
Mountain View/California/United States (US) - Google LLC


  ns-cloud-a4.googledomains.com
2001:4860:4802:38::6a
Mountain View/California/United States (US) - Google LLC

com
  a.gtld-servers.net / nnn1-fra6


  b.gtld-servers.net / nnn1-eltxl2


  c.gtld-servers.net / nnn1-fra6


  d.gtld-servers.net / nnn1-fra6


  e.gtld-servers.net / nnn1-fra6


  f.gtld-servers.net / nnn1-fra5


  g.gtld-servers.net / nnn1-fra5


  h.gtld-servers.net / nnn1-fra5


  i.gtld-servers.net / nnn1-fra5


  j.gtld-servers.net / nnn1-nlams-1d


  k.gtld-servers.net / nnn1-nlams-1c


  l.gtld-servers.net / nnn1-nlams-1c


  m.gtld-servers.net / nnn1-nlams-1d

 

4. SOA-Entries


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


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


Domain:hearthealthtech.com
Zone-Name:hearthealthtech.com
Primary:ns-cloud-a1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:29
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:4


Domain:clinicaltrials.hearthealthtech.com
Zone-Name:hearthealthtech.com
Primary:ns-cloud-a1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:29
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:1


Domain:www.clinicaltrials.hearthealthtech.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

Startaddress: https://clinicaltrials.hearthealthtech.com, address used: https://clinicaltrials.hearthealthtech.com/, Screenshot created 2022-04-12 08:58:20 +00:0

 

Mobil (412px x 732px)

 

869 milliseconds

 

Screenshot mobile - https://clinicaltrials.hearthealthtech.com/
Mobil + Landscape (732px x 412px)

 

503 milliseconds

 

Screenshot mobile landscape - https://clinicaltrials.hearthealthtech.com/
Screen (1280px x 1680px)

 

3746 milliseconds

 

Screenshot Desktop - https://clinicaltrials.hearthealthtech.com/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport412716
content Size452716

 

Fatal: Horizontal scrollbar detected. Content-size width is greater then visual Viewport width.

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://clinicaltrials.hearthealthtech.com/
35.200.238.249
301
https://clinicaltrials.hearthealthtech.com/
Html is minified: 109.03 %
0.530
A
Server: nginx/1.20.1
Date: Tue, 12 Apr 2022 06:57:26 GMT
Content-Type: text/html
Content-Length: 169
Connection: close
Location: https://clinicaltrials.hearthealthtech.com/

• https://clinicaltrials.hearthealthtech.com/
35.200.238.249
Inline-JavaScript (∑/total): 1/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 114.31 %
Other inline scripts (∑/total): 0/0
7.610
A
small visible content (num chars: 46)
You need to enable JavaScript to run this app.
Server: nginx/1.20.1
Date: Tue, 12 Apr 2022 06:57:27 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Last-Modified: Sat, 12 Feb 2022 06:42:26 GMT
Vary: Accept-Encoding
ETag: W/"620756d2-307"
Content-Encoding: gzip
Strict-Transport-Security: max-age=31536000

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

Html is minified: 110.07 %
Other inline scripts (∑/total): 0/0
0.530
A
Not Found
Visible Content: 404 Not Found nginx/1.20.1
Server: nginx/1.20.1
Date: Tue, 12 Apr 2022 06:57:36 GMT
Content-Type: text/html
Content-Length: 153
Connection: close

• https://35.200.238.249/
35.200.238.249
503

Html is minified: 107.65 %
6.436
N
Service Temporarily Unavailable
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Server: nginx/1.20.1
Date: Tue, 12 Apr 2022 06:57:37 GMT
Content-Type: text/html
Content-Length: 197
Connection: close

 

7. Comments


1. General Results, most used to calculate the result

Aname "clinicaltrials.hearthealthtech.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 63591 (complete: 175327)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: clinicaltrials.hearthealthtech.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: clinicaltrials.hearthealthtech.com has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
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):0 complete Content-Type - header (2 urls)
https://clinicaltrials.hearthealthtech.com/ 35.200.238.249


Url with incomplete Content-Type - header - missing charset
http://clinicaltrials.hearthealthtech.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 35.200.238.249


Url with incomplete Content-Type - header - missing charset
Ahttp://clinicaltrials.hearthealthtech.com/ 35.200.238.249
301
https://clinicaltrials.hearthealthtech.com/
Correct redirect http - https with the same domain name
Nhttps://35.200.238.249/ 35.200.238.249
503

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain clinicaltrials.hearthealthtech.com, 1 ip addresses.

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)


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-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-a1.googledomains.com.
AGood: Only one SOA.Primary Name Server found.: ns-cloud-a1.googledomains.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-cloud-a1.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-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.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
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
Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: US
A
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: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns-cloud-a1.googledomains.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.
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.
https://clinicaltrials.hearthealthtech.com/ 35.200.238.249
200

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://clinicaltrials.hearthealthtech.com/ 35.200.238.249
200

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.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
https://clinicaltrials.hearthealthtech.com/ 35.200.238.249
200

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.
AGood: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 3 external CSS / JavaScript files found
Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 1 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 1 with Cache-Control max-age too short (minimum 7 days), 1 with Cache-Control long enough, 3 complete.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
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: 117470 milliseconds, 117.470 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
clinicaltrials.hearthealthtech.com
35.200.238.249
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
supported
ok
clinicaltrials.hearthealthtech.com
35.200.238.249
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
supported
ok
http/2 via ALPN supported 
SNI required
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
SNI required
Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - too much certificates, don't send root certificates

1CN=clinicaltrials.hearthealthtech.com


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US


35.200.238.249
35.200.238.249
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

35.200.238.249
35.200.238.249
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
http/2 via ALPN supported 
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
Self signed certificate

1CN=letsencrypt-nginx-proxy-companion

 

9. Certificates

1.
1.
CN=clinicaltrials.hearthealthtech.com
11.04.2022
10.07.2022
878 days expired
clinicaltrials.hearthealthtech.com - 1 entry
1.
1.
CN=clinicaltrials.hearthealthtech.com
11.04.2022

10.07.2022
878 days expired


clinicaltrials.hearthealthtech.com - 1 entry

KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03B30007E70FA74F25928958CB0BAA32C758
Thumbprint:A92ACB5DB29B81686FA0B447BD7DBAE11F43CB5A
SHA256 / Certificate:wgMJx5F7392j6PgsA3bEgTpeEIWOeOKxQl+2F9CuSS8=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):29e8d50d4d90650a318a4a675fdc9316415c7f8ca89d0821ad343e18d37a94f2
SHA256 hex / Subject Public Key Information (SPKI):29e8d50d4d90650a318a4a675fdc9316415c7f8ca89d0821ad343e18d37a94f2 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://r3.o.lencr.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020
15.09.2025
expires in 285 days


2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020

15.09.2025
expires in 285 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00912B084ACF0C18A753F6D62E25A75F5A
Thumbprint:A053375BFE84E8B748782C7CEE15827A6AF5A405
SHA256 / Certificate:Z63RFmsCCuYbj1/JaBPATCqliZYHloZVcqPH5zdhPf0=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SHA256 hex / Subject Public Key Information (SPKI):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Clientauthentifizierung (1.3.6.1.5.5.7.3.2), Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015
04.06.2035
expires in 3834 days


3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015

04.06.2035
expires in 3834 days




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008210CFB0D240E3594463E0BB63828B00
Thumbprint:CABD2A79A1076A31F21D253635CB039D4329A5E8
SHA256 / Certificate:lrzsBiZJdvN0YHeazyjFp8/oo8Cq4RqP/O4FwL3fCMY=
SHA256 hex / Cert (DANE * 0 1):96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SHA256 hex / PublicKey (DANE * 1 1):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SHA256 hex / Subject Public Key Information (SPKI):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
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:




2.
1.
CN=letsencrypt-nginx-proxy-companion
18.08.2021
18.08.2022
839 days expired

2.
1.
CN=letsencrypt-nginx-proxy-companion
18.08.2021

18.08.2022
839 days expired




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:09BA18CCF41403663759F3D99F84AA0407EA9C88
Thumbprint:60AED330A0F342DEA2A1B6A456D394844B0CE70A
SHA256 / Certificate:5L3yYh54dEwBSanu3jG7GQNkgTGuHeBDD2mqIlrxkm4=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):06f62ed62c0fcc9eb5cf93d8e9af3f2e525753a13a3f9ae0dda2a866c08ed2b9
SHA256 hex / Subject Public Key Information (SPKI):06f62ed62c0fcc9eb5cf93d8e9af3f2e525753a13a3f9ae0dda2a866c08ed2b9 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:


UntrustedRoot: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.


 

10. Last Certificates - Certificate Transparency Log Check

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

Small Code Update - wait one minute

 

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

Small Code Update - wait one minute

 

11. Html-Content - Entries

Summary


Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
https://clinicaltrials.hearthealthtech.com/
35.200.238.249
link
stylesheet
2
6,874 Bytes
0
0
2
2
0
0
-2

link
other
2
2,300 Bytes
0
2
0
0
0
0


meta
other
3

0


0
0
0


script

1

0
1
0
0
0
0

 

Details

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsgStatus
https://clinicaltrials.hearthealthtech.com/
35.200.238.249
link
icon
/assets/logo_main.ico
200

1
ok
image/x-icon
missing X-Content-Type-Options nosniff





No Cache-Control header
No Compression - 1150 Bytes








link
shortcut icon
logo_main.ico
200

1
ok
image/x-icon
missing X-Content-Type-Options nosniff





No Cache-Control header
No Compression - 1150 Bytes








link
stylesheet
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css
200

1
ok
text/css; charset=utf-8
X-Content-Type-Options nosniff found





Cache-Control: public, max-age=30672000 - with long duration found.
Compression required: 6874 Bytes






Server-Header Access-Control-Allow-Origin: *
Cross-Origin Resource Sharing (CORS) supported

missing crossorigin=anonymous|use-credentials and integrity - attribute, possible hash-values:

 

sha256-eZrrJcwDc/3uDhsdt61sL2oOBY362qM3lon1gyExkL0=
sha384-wvfXpqpZZVQGK6TAh5PVlGOfQNHSoD2xbE+QkPxCAFlNEevoEH3Sl0sibVcOQVnN
sha512-SfTiTlX6kk+qitfevl/7LibUOeJWlt9rbyDn92a1DqWOw9vWG2MFoays0sgObmWazO5BQPiFucnnEAjpAB+/Sw==

 

<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css" crossorigin="anonymous" integrity="sha256-eZrrJcwDc/3uDhsdt61sL2oOBY362qM3lon1gyExkL0=" />


Content loaded via url("...")

 

../fonts/fontawesome-webfont.eot?#iefix&v=4.7.01
../fonts/fontawesome-webfont.eot?v=4.7.01
../fonts/fontawesome-webfont.svg?v=4.7.0#fontawesomeregular1
../fonts/fontawesome-webfont.ttf?v=4.7.01
../fonts/fontawesome-webfont.woff?v=4.7.01
../fonts/fontawesome-webfont.woff2?v=4.7.01

link
stylesheet
https://fonts.googleapis.com/css2?family=Nunito&display=swap
200

1
ok
text/css; charset=utf-8
X-Content-Type-Options nosniff found





197 Bytes






Server-Header Access-Control-Allow-Origin: *
Cross-Origin Resource Sharing (CORS) supported

missing crossorigin=anonymous|use-credentials and integrity - attribute, possible hash-values:

 

sha256-DgSNdm4hECu3NGBAa7TogzTdzpjRziKVp8talYbarKE=
sha384-hHtTQj9yp/fjeAixhsOdhA3fNQSsYmRvhLkMmqcj5mu0ebPWQIns0TSHNs2zVH3Q
sha512-xJSAeWSXFQ/l+21yi9cMaHrUHOZYsLcL23cYidnhEdNb6t4nHj42eTl35AK5a7ffkBastCoJqdjFGpoe1XPwDw==

 

<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Nunito&display=swap" crossorigin="anonymous" integrity="sha256-DgSNdm4hECu3NGBAa7TogzTdzpjRziKVp8talYbarKE=" />


Content loaded via url("...")

 

https://fonts.gstatic.com/s/nunito/v23/XRXI3I6Li01BKofiOc5wtlZ2di8HDLshRTM.ttf1

meta
charset
utf-8


1
ok















meta
theme-color
#000000


1
ok















meta
viewport
width=device-width, initial-scale=1


1
ok















script
src
bundle.js
200

1
ok
Missing defer / async attribute. application/javascript
missing X-Content-Type-Options nosniff





No Cache-Control - header
Compression required: 1523516 Bytes






local SRI possible, possible hash-values:

 

sha256-r144i9fWj/kO/MXsozsM1AtHN3Nn5/YN67eWE9tBT0M=
sha384-jrd4+BonvH7dqxYS/0hm+Hmnc80/r46cBKziTsihbotaoLcwU0rMeqqSr0famzrK
sha512-xcjhPBsUacz0pHzS0dJCLezMSBZQ2HiNUeiHyYio8hQwW/WHnfEEZlVpPcaIIru55MAx3M5lgkefo6cPUT6K0w==

 

<script src="bundle.js" crossorigin="anonymous" integrity="sha256-r144i9fWj/kO/MXsozsM1AtHN3Nn5/YN67eWE9tBT0M=" />


 

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

  Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.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-a1.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-a2.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-a3.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-a4.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-a1.googledomains.com: 216.239.32.106
A
ns5.googledomains.com (2001:4860:4802:32::a)
7
ns-cloud-a1.googledomains.com: 2001:4860:4802:32::6a
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
8
ns-cloud-a2.googledomains.com: 216.239.34.106
A
ns5.googledomains.com (2001:4860:4802:32::a)
9
ns-cloud-a2.googledomains.com: 2001:4860:4802:34::6a
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
10
ns-cloud-a3.googledomains.com: 216.239.36.106
A
ns5.googledomains.com (2001:4860:4802:32::a)
11
ns-cloud-a3.googledomains.com: 2001:4860:4802:36::6a
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
12
ns-cloud-a4.googledomains.com: 216.239.38.106
A
ns5.googledomains.com (2001:4860:4802:32::a)
13
ns-cloud-a4.googledomains.com: 2001:4860:4802:38::6a
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
clinicaltrials.hearthealthtech.com
0

no CAA entry found
1
0
hearthealthtech.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
hearthealthtech.com

ok
1
0
clinicaltrials.hearthealthtech.com

ok
1
0
_acme-challenge.clinicaltrials.hearthealthtech.com

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

perhaps wrong
1
0
_acme-challenge.clinicaltrials.hearthealthtech.com.clinicaltrials.hearthealthtech.com

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

DomainIPPortDescriptionResultAnswer
clinicaltrials.hearthealthtech.com
35.200.238.249
21
FTP



clinicaltrials.hearthealthtech.com
35.200.238.249
21
FTP



clinicaltrials.hearthealthtech.com
35.200.238.249
22
SSH



clinicaltrials.hearthealthtech.com
35.200.238.249
22
SSH



clinicaltrials.hearthealthtech.com
35.200.238.249
25
SMTP



clinicaltrials.hearthealthtech.com
35.200.238.249
25
SMTP



clinicaltrials.hearthealthtech.com
35.200.238.249
53
DNS



clinicaltrials.hearthealthtech.com
35.200.238.249
53
DNS



clinicaltrials.hearthealthtech.com
35.200.238.249
110
POP3



clinicaltrials.hearthealthtech.com
35.200.238.249
110
POP3



clinicaltrials.hearthealthtech.com
35.200.238.249
143
IMAP



clinicaltrials.hearthealthtech.com
35.200.238.249
143
IMAP



clinicaltrials.hearthealthtech.com
35.200.238.249
465
SMTP (encrypted)



clinicaltrials.hearthealthtech.com
35.200.238.249
465
SMTP (encrypted)



clinicaltrials.hearthealthtech.com
35.200.238.249
587
SMTP (encrypted, submission)



clinicaltrials.hearthealthtech.com
35.200.238.249
587
SMTP (encrypted, submission)



clinicaltrials.hearthealthtech.com
35.200.238.249
993
IMAP (encrypted)



clinicaltrials.hearthealthtech.com
35.200.238.249
993
IMAP (encrypted)



clinicaltrials.hearthealthtech.com
35.200.238.249
995
POP3 (encrypted)



clinicaltrials.hearthealthtech.com
35.200.238.249
995
POP3 (encrypted)



clinicaltrials.hearthealthtech.com
35.200.238.249
1433
MS SQL



clinicaltrials.hearthealthtech.com
35.200.238.249
1433
MS SQL



clinicaltrials.hearthealthtech.com
35.200.238.249
2082
cPanel (http)



clinicaltrials.hearthealthtech.com
35.200.238.249
2082
cPanel (http)



clinicaltrials.hearthealthtech.com
35.200.238.249
2083
cPanel (https)



clinicaltrials.hearthealthtech.com
35.200.238.249
2083
cPanel (https)



clinicaltrials.hearthealthtech.com
35.200.238.249
2086
WHM (http)



clinicaltrials.hearthealthtech.com
35.200.238.249
2086
WHM (http)



clinicaltrials.hearthealthtech.com
35.200.238.249
2087
WHM (https)



clinicaltrials.hearthealthtech.com
35.200.238.249
2087
WHM (https)



clinicaltrials.hearthealthtech.com
35.200.238.249
2089
cPanel Licensing



clinicaltrials.hearthealthtech.com
35.200.238.249
2089
cPanel Licensing



clinicaltrials.hearthealthtech.com
35.200.238.249
2095
cPanel Webmail (http)



clinicaltrials.hearthealthtech.com
35.200.238.249
2095
cPanel Webmail (http)



clinicaltrials.hearthealthtech.com
35.200.238.249
2096
cPanel Webmail (https)



clinicaltrials.hearthealthtech.com
35.200.238.249
2096
cPanel Webmail (https)



clinicaltrials.hearthealthtech.com
35.200.238.249
2222
DirectAdmin (http)



clinicaltrials.hearthealthtech.com
35.200.238.249
2222
DirectAdmin (http)



clinicaltrials.hearthealthtech.com
35.200.238.249
2222
DirectAdmin (https)



clinicaltrials.hearthealthtech.com
35.200.238.249
2222
DirectAdmin (https)



clinicaltrials.hearthealthtech.com
35.200.238.249
3306
mySql



clinicaltrials.hearthealthtech.com
35.200.238.249
3306
mySql



clinicaltrials.hearthealthtech.com
35.200.238.249
5224
Plesk Licensing



clinicaltrials.hearthealthtech.com
35.200.238.249
5224
Plesk Licensing



clinicaltrials.hearthealthtech.com
35.200.238.249
5432
PostgreSQL



clinicaltrials.hearthealthtech.com
35.200.238.249
5432
PostgreSQL



clinicaltrials.hearthealthtech.com
35.200.238.249
8080
Ookla Speedtest (http)



clinicaltrials.hearthealthtech.com
35.200.238.249
8080
Ookla Speedtest (http)



clinicaltrials.hearthealthtech.com
35.200.238.249
8080
Ookla Speedtest (https)



clinicaltrials.hearthealthtech.com
35.200.238.249
8080
Ookla Speedtest (https)



clinicaltrials.hearthealthtech.com
35.200.238.249
8083
VestaCP http



clinicaltrials.hearthealthtech.com
35.200.238.249
8083
VestaCP http



clinicaltrials.hearthealthtech.com
35.200.238.249
8083
VestaCP https



clinicaltrials.hearthealthtech.com
35.200.238.249
8083
VestaCP https



clinicaltrials.hearthealthtech.com
35.200.238.249
8443
Plesk Administration (https)



clinicaltrials.hearthealthtech.com
35.200.238.249
8443
Plesk Administration (https)



clinicaltrials.hearthealthtech.com
35.200.238.249
8447
Plesk Installer + Updates



clinicaltrials.hearthealthtech.com
35.200.238.249
8447
Plesk Installer + Updates



clinicaltrials.hearthealthtech.com
35.200.238.249
8880
Plesk Administration (http)



clinicaltrials.hearthealthtech.com
35.200.238.249
8880
Plesk Administration (http)



clinicaltrials.hearthealthtech.com
35.200.238.249
10000
Webmin (http)



clinicaltrials.hearthealthtech.com
35.200.238.249
10000
Webmin (http)



clinicaltrials.hearthealthtech.com
35.200.238.249
10000
Webmin (https)



clinicaltrials.hearthealthtech.com
35.200.238.249
10000
Webmin (https)



 

 

Permalink: https://check-your-website.server-daten.de/?i=d39e3b0d-2e72-47fd-94fc-a1bad64cb681

 

Last Result: https://check-your-website.server-daten.de/?q=clinicaltrials.hearthealthtech.com - 2022-04-12 08:56:37

 

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

 

<a href="https://check-your-website.server-daten.de/?q=clinicaltrials.hearthealthtech.com" target="_blank">Check this Site: clinicaltrials.hearthealthtech.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=clinicaltrials.hearthealthtech.com