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



W

wrong Web-Response

Checked:
08.11.2019 09:55:16


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
eyeware.studio
A
223.16.122.101
Fanling/North/Hong Kong (HK) - HGC Global Communications Limited
Hostname: 101-122-16-223-on-nets.com
yes
2
0

AAAA

yes


www.eyeware.studio
CNAME
eyeware.studio
yes
1
0

A
223.16.122.101
Fanling/North/Hong Kong (HK) - HGC Global Communications Limited
Hostname: 101-122-16-223-on-nets.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 22545, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.11.2019, 00:00:00 +, Signature-Inception: 31.10.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: studio
studio
2 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner studio., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 21.11.2019, 05:00:00 +, Signature-Inception: 08.11.2019, 04:00:00 +, KeyTag 22545, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 44616, Flags 256



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



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner studio., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.12.2019, 17:23:02 +, Signature-Inception: 04.11.2019, 16:26:22 +, KeyTag 44616, Signer-Name: studio



RRSIG-Owner studio., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.12.2019, 17:23:02 +, Signature-Inception: 04.11.2019, 16:26:22 +, KeyTag 56335, Signer-Name: studio



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



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



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



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

Zone: eyeware.studio
eyeware.studio
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 "hd26fg5ghpiccf9dhjdj0hfqnfr9sihk" between the hashed NSEC3-owner "hbrpn49eoa134073vu8qs1lh5tmt1rse" and the hashed NextOwner "heq1bhicilfh2fv4v4alj3hbhrfgesmr". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner hbrpn49eoa134073vu8qs1lh5tmt1rse.studio., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 04.12.2019, 12:47:58 +, Signature-Inception: 04.11.2019, 11:55:19 +, KeyTag 44616, Signer-Name: studio



0 DNSKEY RR found




Zone: www.eyeware.studio
www.eyeware.studio
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
eyeware.studio
  dns1.registrar-servers.com
216.87.155.33
Amsterdam/North Holland/Netherlands (NL) - VeriSign Global Registry Services


 
2620:74:19::33
Reston/Virginia/United States (US) - VeriSign Global Registry Services


  dns2.registrar-servers.com
216.87.152.33
Dallas/Texas/United States (US) - VeriSign Global Registry Services


 
2001:502:cbe4::33
Reston/Virginia/United States (US) - VeriSign Global Registry Services

studio
  demand.alpha.aridns.net.au / dns1.tky


  demand.beta.aridns.net.au / dns5.ams


  demand.delta.aridns.net.au / dns2.mia


  demand.gamma.aridns.net.au / dns4.mia


4. SOA-Entries


Domain:studio
Zone-Name:
Primary:demand.alpha.aridns.net.au
Mail:hostmaster.donuts.co
Serial:1573202828
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:4


Domain:eyeware.studio
Zone-Name:
Primary:dns1.registrar-servers.com
Mail:hostmaster.registrar-servers.com
Serial:2019110812
Refresh:43200
Retry:3600
Expire:604800
TTL:3601
num Entries:4


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://eyeware.studio/
223.16.122.101 GZip used - 991 / 2769 - 64.21 %
200

Html is minified: 111.38 %
0.720
H
Date: Fri, 08 Nov 2019 08:55:41 GMT
Server: Apache
X-Frame-Options: SAMEORIGIN
Feature-Policy: geolocation 'none'
Retry-After: 86400
Vary: Accept-Encoding
Content-Encoding: gzip
X-XSS-Protection: 1; mode=block
Content-Security-Policy: script-src 'self' https://drive.google.com
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer-when-downgrade
Content-Length: 991
Connection: close
Content-Type: text/html; charset=UTF-8

• http://www.eyeware.studio/
223.16.122.101 GZip used - 991 / 2769 - 64.21 %
200

Html is minified: 111.38 %
0.716
H
Date: Fri, 08 Nov 2019 08:55:42 GMT
Server: Apache
X-Frame-Options: SAMEORIGIN
Feature-Policy: geolocation 'none'
Retry-After: 86400
Vary: Accept-Encoding
Content-Encoding: gzip
X-XSS-Protection: 1; mode=block
Content-Security-Policy: script-src 'self' https://drive.google.com
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer-when-downgrade
Content-Length: 991
Connection: close
Content-Type: text/html; charset=UTF-8

• https://eyeware.studio/
223.16.122.101
-4

1.157
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

• https://www.eyeware.studio/
223.16.122.101
-4

1.140
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

• http://eyeware.studio:443/
223.16.122.101
-8

1.530
A
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://www.eyeware.studio:443/
223.16.122.101
-8

1.107
A
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://eyeware.studio/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
223.16.122.101 GZip used - 991 / 2769 - 64.21 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 111.38 %
1.267

Visible Content:
Date: Fri, 08 Nov 2019 08:55:45 GMT
Server: Apache
X-Frame-Options: SAMEORIGIN
Feature-Policy: geolocation 'none'
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Retry-After: 86400
Vary: Accept-Encoding
Content-Encoding: gzip
X-XSS-Protection: 1; mode=block
Content-Security-Policy: script-src 'self' https://drive.google.com
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer-when-downgrade
Content-Length: 991
Connection: close
Content-Type: text/html; charset=UTF-8

• http://www.eyeware.studio/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
223.16.122.101 GZip used - 991 / 2769 - 64.21 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 111.38 %
0.860

Visible Content:
Date: Fri, 08 Nov 2019 08:55:46 GMT
Server: Apache
X-Frame-Options: SAMEORIGIN
Feature-Policy: geolocation 'none'
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Retry-After: 86400
Vary: Accept-Encoding
Content-Encoding: gzip
X-XSS-Protection: 1; mode=block
Content-Security-Policy: script-src 'self' https://drive.google.com
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer-when-downgrade
Content-Length: 991
Connection: close
Content-Type: text/html; charset=UTF-8

7. Comments


1. General Results, most used to calculate the result

Aname "eyeware.studio" is domain, public suffix is "studio", top-level-domain-type is "generic", tld-manager is "United TLD Holdco Ltd."
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
Hfatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Ihttp://eyeware.studio/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 223.16.122.101
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
Ihttp://www.eyeware.studio/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 223.16.122.101
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.

2. DNS- and NameServer - Checks

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: dns1.registrar-servers.com,dns2.registrar-servers.com
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: demand.beta.aridns.net.au: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (dns5.ams). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
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

http://eyeware.studio/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 223.16.122.101
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.eyeware.studio/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 223.16.122.101
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: All CSS / JavaScript files are sent with GZip. That reduces the content of the files. 2 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. 8 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 2 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 10 complete.
Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 2 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 2 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 4 complete.
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: 50757 milliseconds, 50.757 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

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

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
0
7

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1231469002
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-08 07:34:50
2020-02-06 07:34:50
eyeware.studio, www.eyeware.studio - 2 entries


1231445414
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-08 07:23:27
2020-02-06 07:23:27
eyeware.studio, www.eyeware.studio - 2 entries


1231274552
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-08 05:42:21
2020-02-06 05:42:21
www.eyeware.studio - 1 entries


1231271810
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-08 05:40:26
2020-02-06 05:40:26
www.eyeware.studio - 1 entries


1231268651
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-08 05:38:21
2020-02-06 05:38:21
www.eyeware.studio - 1 entries


1231267106
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-08 05:37:01
2020-02-06 05:37:01
www.eyeware.studio - 1 entries


1231266677
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-08 05:36:32
2020-02-06 05:36:32
www.eyeware.studio - 1 entries



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

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
0
7

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2085826828
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-08 06:34:50
2020-02-06 06:34:50
eyeware.studio, www.eyeware.studio
2 entries


2085770986
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-08 06:23:27
2020-02-06 06:23:27
eyeware.studio, www.eyeware.studio
2 entries


2085548291
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-08 04:42:21
2020-02-06 04:42:21
www.eyeware.studio
1 entries


2085543925
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-08 04:40:26
2020-02-06 04:40:26
www.eyeware.studio
1 entries


2085539825
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-08 04:38:21
2020-02-06 04:38:21
www.eyeware.studio
1 entries


2085536984
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-08 04:37:01
2020-02-06 04:37:01
www.eyeware.studio
1 entries


2085537577
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-08 04:36:32
2020-02-06 04:36:32
www.eyeware.studio
1 entries



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.eyeware.studio



1
0
eyeware.studio
0

no CAA entry found
1
0
studio
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
eyeware.studio
v=spf1 include:spf.privateemail.com ~all
ok
1
0
www.eyeware.studio
v=spf1 include:spf.privateemail.com ~all
ok
1
0
_acme-challenge.eyeware.studio

Name Error - The domain name does not exist
1
0
_acme-challenge.www.eyeware.studio

Name Error - The domain name does not exist
1
0
_acme-challenge.eyeware.studio.eyeware.studio

Name Error - The domain name does not exist
1
0
_acme-challenge.www.eyeware.studio.eyeware.studio

Name Error - The domain name does not exist
1
0
_acme-challenge.www.eyeware.studio.www.eyeware.studio

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=140cd101-7a9d-4fdc-b387-ecc1597fbe61


Last Result: https://check-your-website.server-daten.de/?q=eyeware.studio - 2019-11-08 09:57:10


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

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