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


 

 

T

 

Timeout

 

Checked:
27.08.2021 16:03:46

 

Older results

 

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
wygiz.app
A
151.80.149.141
Roubaix/Hauts-de-France/France (FR) - OVH SAS
Hostname: 141.ip-151-80-149.eu
yes
1
0

AAAA

yes


www.wygiz.app
A
151.80.149.141
Roubaix/Hauts-de-France/France (FR) - OVH SAS
Hostname: 141.ip-151-80-149.eu
yes
1
0

AAAA

yes


*.wygiz.app
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 26838, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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

app
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 23684, DigestType 2 and Digest OlzIox4CyUq6ZGGRL6u36fXjSVe7YRSlWoZNlq7DGDY=






1 RRSIG RR to validate DS RR found






RRSIG-Owner app., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 09.09.2021, 05:00:00 +, Signature-Inception: 27.08.2021, 04:00:00 +, KeyTag 26838, Signer-Name: (root)






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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 58030, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner app., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 16.09.2021, 07:30:28 +, Signature-Inception: 25.08.2021, 07:30:28 +, KeyTag 23684, Signer-Name: app






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






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



Zone: wygiz.app

wygiz.app
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 17779, DigestType 2 and Digest 8cWuBXU7nqPfLJCE4noowR/PnldMkt8vJdnLUkckw6U=






1 RRSIG RR to validate DS RR found






RRSIG-Owner wygiz.app., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 16.09.2021, 07:30:28 +, Signature-Inception: 25.08.2021, 07:30:28 +, KeyTag 58030, Signer-Name: app






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 15369, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner wygiz.app., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 17779, Signer-Name: wygiz.app






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






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






RRSIG Type 1 validates the A - Result: 151.80.149.141
Validated: RRSIG-Owner wygiz.app., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 15369, Signer-Name: wygiz.app






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "k2l5n8566hc75jd92h0i1f5cjv8s9pa8" equal the hashed NSEC3-owner "k2l5n8566hc75jd92h0i1f5cjv8s9pa8" and the hashed NextOwner "oaj9eq9f3ncoc8pslf5qqjtofbiiaiuj". 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, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner k2l5n8566hc75jd92h0i1f5cjv8s9pa8.wygiz.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 15369, Signer-Name: wygiz.app






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed query name "k2l5n8566hc75jd92h0i1f5cjv8s9pa8" equal the hashed NSEC3-owner "k2l5n8566hc75jd92h0i1f5cjv8s9pa8" and the hashed NextOwner "oaj9eq9f3ncoc8pslf5qqjtofbiiaiuj". 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, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner k2l5n8566hc75jd92h0i1f5cjv8s9pa8.wygiz.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 15369, Signer-Name: wygiz.app






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "k2l5n8566hc75jd92h0i1f5cjv8s9pa8" equal the hashed NSEC3-owner "k2l5n8566hc75jd92h0i1f5cjv8s9pa8" and the hashed NextOwner "oaj9eq9f3ncoc8pslf5qqjtofbiiaiuj". 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, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner k2l5n8566hc75jd92h0i1f5cjv8s9pa8.wygiz.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 15369, Signer-Name: wygiz.app






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.wygiz.app) sends a valid NSEC3 RR as result with the hashed owner name "k2l5n8566hc75jd92h0i1f5cjv8s9pa8" (unhashed: wygiz.app). So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "kn6qntt705pqksj6pvvv7hd6p0s1h2nu" (unhashed: *.wygiz.app) with the owner "k2l5n8566hc75jd92h0i1f5cjv8s9pa8" and the NextOwner "oaj9eq9f3ncoc8pslf5qqjtofbiiaiuj". So that NSEC3 confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.wygiz.app) sends a valid NSEC3 RR as result with the hashed query name "l9o8mshqb350hr8v8dsraov6a77nh1rr" between the hashed NSEC3-owner "k2l5n8566hc75jd92h0i1f5cjv8s9pa8" and the hashed NextOwner "oaj9eq9f3ncoc8pslf5qqjtofbiiaiuj". So the zone confirmes the not-existence of that TLSA RR.
Bitmap: A, NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner k2l5n8566hc75jd92h0i1f5cjv8s9pa8.wygiz.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 15369, Signer-Name: wygiz.app






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "fg52dk0f1mtdbsl7sb42iu0nu30d4cub" (unhashed: _tcp.wygiz.app) with the owner "akiogg6q63dlrr204p6lerg056tbgdkf" and the NextOwner "fru3307k5fq7cvuqon47n03708ffgqpv". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, RRSIG Validated: RRSIG-Owner akiogg6q63dlrr204p6lerg056tbgdkf.wygiz.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 15369, Signer-Name: wygiz.app






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "k2l5n8566hc75jd92h0i1f5cjv8s9pa8" equal the hashed NSEC3-owner "k2l5n8566hc75jd92h0i1f5cjv8s9pa8" and the hashed NextOwner "oaj9eq9f3ncoc8pslf5qqjtofbiiaiuj". 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, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner k2l5n8566hc75jd92h0i1f5cjv8s9pa8.wygiz.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 15369, Signer-Name: wygiz.app






Status: Good. NoData-Proof required and found.



Zone: www.wygiz.app

www.wygiz.app
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 "akiogg6q63dlrr204p6lerg056tbgdkf" between the hashed NSEC3-owner "akiogg6q63dlrr204p6lerg056tbgdkf" and the hashed NextOwner "fru3307k5fq7cvuqon47n03708ffgqpv". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner akiogg6q63dlrr204p6lerg056tbgdkf.wygiz.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 15369, Signer-Name: wygiz.app






RRSIG Type 1 validates the A - Result: 151.80.149.141
Validated: RRSIG-Owner www.wygiz.app., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 15369, Signer-Name: wygiz.app






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "akiogg6q63dlrr204p6lerg056tbgdkf" equal the hashed NSEC3-owner "akiogg6q63dlrr204p6lerg056tbgdkf" and the hashed NextOwner "fru3307k5fq7cvuqon47n03708ffgqpv". 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 akiogg6q63dlrr204p6lerg056tbgdkf.wygiz.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 15369, Signer-Name: wygiz.app






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed query name "akiogg6q63dlrr204p6lerg056tbgdkf" equal the hashed NSEC3-owner "akiogg6q63dlrr204p6lerg056tbgdkf" and the hashed NextOwner "fru3307k5fq7cvuqon47n03708ffgqpv". 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 akiogg6q63dlrr204p6lerg056tbgdkf.wygiz.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 15369, Signer-Name: wygiz.app






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "akiogg6q63dlrr204p6lerg056tbgdkf" equal the hashed NSEC3-owner "akiogg6q63dlrr204p6lerg056tbgdkf" and the hashed NextOwner "fru3307k5fq7cvuqon47n03708ffgqpv". 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 akiogg6q63dlrr204p6lerg056tbgdkf.wygiz.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 15369, Signer-Name: wygiz.app






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.www.wygiz.app) sends a valid NSEC3 RR as result with the hashed owner name "akiogg6q63dlrr204p6lerg056tbgdkf" (unhashed: www.wygiz.app). So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "bnbboqavhv70b3vqkm0j2crf1aake8j5" (unhashed: _tcp.www.wygiz.app) with the owner "akiogg6q63dlrr204p6lerg056tbgdkf" and the NextOwner "fru3307k5fq7cvuqon47n03708ffgqpv". 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 "d5pv3o99k4p49fmfd8ukva5j1oapljhq" (unhashed: *.www.wygiz.app) with the owner "akiogg6q63dlrr204p6lerg056tbgdkf" and the NextOwner "fru3307k5fq7cvuqon47n03708ffgqpv". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: A, RRSIG Validated: RRSIG-Owner akiogg6q63dlrr204p6lerg056tbgdkf.wygiz.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 15369, Signer-Name: wygiz.app






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "akiogg6q63dlrr204p6lerg056tbgdkf" equal the hashed NSEC3-owner "akiogg6q63dlrr204p6lerg056tbgdkf" and the hashed NextOwner "fru3307k5fq7cvuqon47n03708ffgqpv". 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 akiogg6q63dlrr204p6lerg056tbgdkf.wygiz.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 17.09.2021, 11:06:06 +, Signature-Inception: 26.08.2021, 11:06:06 +, KeyTag 15369, Signer-Name: wygiz.app






Status: Good. NoData-Proof required and found.

 

3. Name Servers

DomainNameserverNS-IP
www.wygiz.app
  ns-cloud-c1.googledomains.com

wygiz.app
  ns-cloud-c1.googledomains.com
216.239.32.108
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:32::6c
Mountain View/California/United States (US) - Google LLC


  ns-cloud-c2.googledomains.com
216.239.34.108
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:34::6c
Mountain View/California/United States (US) - Google LLC


  ns-cloud-c3.googledomains.com
216.239.36.108
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:36::6c
Mountain View/California/United States (US) - Google LLC


  ns-cloud-c4.googledomains.com
216.239.38.108
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:38::6c
Mountain View/California/United States (US) - Google LLC

app
  ns-tld1.charlestonroadregistry.com


  ns-tld2.charlestonroadregistry.com


  ns-tld3.charlestonroadregistry.com


  ns-tld4.charlestonroadregistry.com


  ns-tld5.charlestonroadregistry.com

 

4. SOA-Entries


Domain:app
Zone-Name:app
Primary:ns-tld1.charlestonroadregistry.com
Mail:cloud-dns-hostmaster.google.com
Serial:101427
Refresh:21600
Retry:3600
Expire:259200
TTL:900
num Entries:5


Domain:wygiz.app
Zone-Name:wygiz.app
Primary:ns-cloud-c1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:30
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


Domain:www.wygiz.app
Zone-Name:wygiz.app
Primary:ns-cloud-c1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:30
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:1


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://wygiz.app/
151.80.149.141
-14


10.027
T
Timeout - The operation has timed out

• http://www.wygiz.app/
151.80.149.141
-14


10.026
T
Timeout - The operation has timed out

• https://wygiz.app/
151.80.149.141
-14


10.030
T
Timeout - The operation has timed out

• https://www.wygiz.app/
151.80.149.141
-14


10.026
T
Timeout - The operation has timed out

• http://wygiz.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
151.80.149.141
-14


10.030
T
Timeout - The operation has timed out
Visible Content:

• http://www.wygiz.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
151.80.149.141
-14


10.027
T
Timeout - The operation has timed out
Visible Content:

• https://151.80.149.141/
151.80.149.141
-14


10.026
T
Timeout - The operation has timed out

 

7. Comments


1. General Results, most used to calculate the result

Aname "wygiz.app" is domain, public suffix is ".app", top-level-domain is ".app", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc.", num .app-domains preloaded: 42 (complete: 168171)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: www.wygiz.app has only one ip address.
Warning: Only one ip address found: wygiz.app 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: www.wygiz.app has no ipv6 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: wygiz.app has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
AExcellent: Domain is in the Google-Preload-List
AExcellent: Domain is in the Mozilla/Firefox-Preload-List
AHSTS-Preload-Status: Preloaded. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
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 www.wygiz.app, 1 ip addresses.
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 wygiz.app, 1 ip addresses.

2. Header-Checks


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-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-c1.googledomains.com.
AGood: Only one SOA.Primary Name Server found.: ns-cloud-c1.googledomains.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-cloud-c1.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-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.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

http://wygiz.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 151.80.149.141
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.wygiz.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 151.80.149.141
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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: 181350 milliseconds, 181.350 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)

No CertSpotter - CT-Log entries found

 

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

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

 

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

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-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com

 

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

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-c1.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-c2.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-c3.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-c4.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-c1.googledomains.com: 216.239.32.108
A
ns5.googledomains.com (2001:4860:4802:32::a)
7
ns-cloud-c1.googledomains.com: 2001:4860:4802:32::6c
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
8
ns-cloud-c2.googledomains.com: 216.239.34.108
A
ns5.googledomains.com (2001:4860:4802:32::a)
9
ns-cloud-c2.googledomains.com: 2001:4860:4802:34::6c
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
10
ns-cloud-c3.googledomains.com: 216.239.36.108
A
ns5.googledomains.com (2001:4860:4802:32::a)
11
ns-cloud-c3.googledomains.com: 2001:4860:4802:36::6c
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
12
ns-cloud-c4.googledomains.com: 216.239.38.108
A
ns5.googledomains.com (2001:4860:4802:32::a)
13
ns-cloud-c4.googledomains.com: 2001:4860:4802:38::6c
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.wygiz.app
0

no CAA entry found
1
0
wygiz.app
0

no CAA entry found
1
0
app
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
wygiz.app

ok
1
0
www.wygiz.app

ok
1
0
_acme-challenge.wygiz.app

Name Error - The domain name does not exist
1
0
_acme-challenge.www.wygiz.app

Name Error - The domain name does not exist
1
0
_acme-challenge.wygiz.app.wygiz.app

Name Error - The domain name does not exist
1
0
_acme-challenge.www.wygiz.app.wygiz.app

Name Error - The domain name does not exist
1
0
_acme-challenge.www.wygiz.app.www.wygiz.app

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

No open Ports <> 80 / 443 found, so no additional Ports checked.

 

 

Permalink: https://check-your-website.server-daten.de/?i=63a79fd6-b39c-4177-bc40-a36feb5a2635

 

Last Result: https://check-your-website.server-daten.de/?q=wygiz.app - 2021-08-27 16:03:46

 

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

 

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