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

0 in Queue, 1 of max. 8 Checks (04:53:29)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

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

 

N

 

No trusted Certificate

 

Checked:
24.09.2019 20:10:51

 

Older results

 

O - 18.07.2019 20:22:09
V - 18.07.2019 16:56:06
V - 18.07.2019 16:47:10
W - 18.07.2019 11:30:12
V - 18.07.2019 10:51:16

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
domoticz.vanveldhuizen.org
CNAME
vanveldhuizen.duckdns.org
yes
1
0

A
77.248.139.109
Heerenveen/Friesland/Netherlands (NL) - UPC NL
Hostname: dhcp-077-248-139-109.chello.nl
yes


www.domoticz.vanveldhuizen.org

Name Error
yes
1
0

 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






• Status: Valid because published






3 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 22545, Flags 256






Public Key with Algorithm 8, KeyTag 59944, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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

org
2 DS RR in the parent zone found






2 RRSIG RR to validate DS RR found






RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 07.10.2019, 05:00:00 +, Signature-Inception: 24.09.2019, 04:00:00 +, KeyTag 59944, Signer-Name: (root)






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






4 DNSKEY RR found






Public Key with Algorithm 7, KeyTag 9795, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 7, KeyTag 17883, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 7, KeyTag 36752, Flags 256






Public Key with Algorithm 7, KeyTag 47612, Flags 256






3 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 10.10.2019, 15:23:48 +, Signature-Inception: 19.09.2019, 14:23:48 +, KeyTag 9795, Signer-Name: org






RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 10.10.2019, 15:23:48 +, Signature-Inception: 19.09.2019, 14:23:48 +, KeyTag 17883, Signer-Name: org






RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 10.10.2019, 15:23:48 +, Signature-Inception: 19.09.2019, 14:23:48 +, KeyTag 47612, Signer-Name: org






• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 9795 used to validate the DNSKEY RRSet






• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 17883 used to validate the DNSKEY RRSet






• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 47612 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 1 and Digest "Nk36s9ryVMq0d7VnWxB2bdqiSYI=" 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 7, KeyTag 9795, DigestType 2 and Digest "OSKzG286TqkrGet7UhIPAx/Y4F/wsDuvz5+JG/5/+OU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: vanveldhuizen.org

vanveldhuizen.org
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 "i7qrtn3q9dr7f8qpuul65m187bg17e4b" between the hashed NSEC3-owner "i7pp6an0rsopssgok3dr07p97jeupl8r" and the hashed NextOwner "i7reovbvve7gh84knpq8eretmfhm08cb". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner i7pp6an0rsopssgok3dr07p97jeupl8r.org., Algorithm: 7, 2 Labels, original TTL: 86400 sec, Signature-expiration: 14.10.2019, 11:37:03 +, Signature-Inception: 23.09.2019, 10:37:03 +, KeyTag 47612, Signer-Name: org






0 DNSKEY RR found









Zone: domoticz.vanveldhuizen.org

domoticz.vanveldhuizen.org
0 DS RR in the parent zone found



Zone: www.domoticz.vanveldhuizen.org

www.domoticz.vanveldhuizen.org
0 DS RR in the parent zone found



Zone: (root)

(root)
1 DS RR published






• Status: Valid because published






3 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 22545, Flags 256






Public Key with Algorithm 8, KeyTag 59944, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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

org
2 DS RR in the parent zone found






2 RRSIG RR to validate DS RR found






RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 07.10.2019, 05:00:00 +, Signature-Inception: 24.09.2019, 04:00:00 +, KeyTag 59944, Signer-Name: (root)






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






4 DNSKEY RR found






Public Key with Algorithm 7, KeyTag 9795, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 7, KeyTag 17883, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 7, KeyTag 36752, Flags 256






Public Key with Algorithm 7, KeyTag 47612, Flags 256






3 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 10.10.2019, 15:23:48 +, Signature-Inception: 19.09.2019, 14:23:48 +, KeyTag 9795, Signer-Name: org






RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 10.10.2019, 15:23:48 +, Signature-Inception: 19.09.2019, 14:23:48 +, KeyTag 17883, Signer-Name: org






RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 10.10.2019, 15:23:48 +, Signature-Inception: 19.09.2019, 14:23:48 +, KeyTag 47612, Signer-Name: org






• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 9795 used to validate the DNSKEY RRSet






• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 17883 used to validate the DNSKEY RRSet






• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 47612 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 1 and Digest "Nk36s9ryVMq0d7VnWxB2bdqiSYI=" 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 7, KeyTag 9795, DigestType 2 and Digest "OSKzG286TqkrGet7UhIPAx/Y4F/wsDuvz5+JG/5/+OU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: duckdns.org

duckdns.org
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 "mnorhcks4b6fjob5ap1mrs7utmhf26bm" between the hashed NSEC3-owner "mnoq314vn5m775pq7osblqq7jdr6o56r" and the hashed NextOwner "mnpis27oa7d3n2t47lo6516sp4um1am4". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner mnoq314vn5m775pq7osblqq7jdr6o56r.org., Algorithm: 7, 2 Labels, original TTL: 86400 sec, Signature-expiration: 15.10.2019, 03:02:38 +, Signature-Inception: 24.09.2019, 02:02:38 +, KeyTag 47612, Signer-Name: org






0 DNSKEY RR found









Zone: vanveldhuizen.duckdns.org

vanveldhuizen.duckdns.org
0 DS RR in the parent zone found






0 DNSKEY RR found







 

3. Name Servers

DomainNameserverNS-IP
www.domoticz.vanveldhuizen.org
•  ns1.mihosnet-38.nl

vanveldhuizen.org
•  ns1.mihosnet-38.nl
•

•  ns2.mihosnet-38.nl
•
org
•  a0.org.afilias-nst.info / ns000a.app32.mia2.afilias-nst.info
•

•  a2.org.afilias-nst.info / 2.ber.pch
•

•  b0.org.afilias-nst.org / ns000b.app23.ams2.afilias-nst.info
•

•  b2.org.afilias-nst.org / 5.fra.pch
•

•  c0.org.afilias-nst.info / ns000b.app28.ams2.afilias-nst.info
•

•  d0.org.afilias-nst.org / app19.iad1.hosts.meta.redstone.afilias-nst.info-2
•
vanveldhuizen.duckdns.org
U  ns1.duckdns.org
54.187.92.222
Portland/Oregon/United States (US) - Amazon Technologies Inc.

U  ns2.duckdns.org
54.191.117.119
Portland/Oregon/United States (US) - Amazon Technologies Inc.

U  ns3.duckdns.org
52.26.169.94
Portland/Oregon/United States (US) - Amazon.com, Inc.
duckdns.org
U  ns1.duckdns.org


U  ns2.duckdns.org


U  ns3.duckdns.org

org
•  a0.org.afilias-nst.info / ns000b.app30.mia2.afilias-nst.info
•

•  a2.org.afilias-nst.info / 2.ber.pch
•

•  b0.org.afilias-nst.org / ns000b.app13.ams2.afilias-nst.info
•

•  b2.org.afilias-nst.org / 4.fra.pch
•

•  c0.org.afilias-nst.info / ns000b.app10.ams2.afilias-nst.info
•

•  d0.org.afilias-nst.org / app1.iad1.hosts.meta.redstone.afilias-nst.info-2
•

 

4. SOA-Entries


Domain:org
Zone-Name:
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2013639784
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:vanveldhuizen.org
Zone-Name:
Primary:ns1.mihosnet-38.nl
Mail:arjenveldhuizen.gmail.com
Serial:2019071901
Refresh:10800
Retry:3600
Expire:604800
TTL:10800
num Entries:2


Domain:www.domoticz.vanveldhuizen.org
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:org
Zone-Name:
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2013639784
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:duckdns.org
Zone-Name:
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:duckdns.org
Zone-Name:
Primary:ns2.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:duckdns.org
Zone-Name:
Primary:ns3.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:vanveldhuizen.duckdns.org
Zone-Name:
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:vanveldhuizen.duckdns.org
Zone-Name:
Primary:ns2.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:vanveldhuizen.duckdns.org
Zone-Name:
Primary:ns3.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://domoticz.vanveldhuizen.org/
77.248.139.109
301
https://domoticz.vanveldhuizen.org/
Html is minified: 108.19 %
0.084
A
Server: nginx/1.14.2
Date: Tue, 24 Sep 2019 18:13:07 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://domoticz.vanveldhuizen.org/

• https://domoticz.vanveldhuizen.org/
77.248.139.109
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		401

Html is minified: 107.73 %
Other inline scripts (∑/total): 0/0		2.290
N
Unauthorized
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
small visible content (num chars: 39)
401 Authorization Required nginx/1.14.2
Server: nginx/1.14.2
Date: Tue, 24 Sep 2019 18:13:07 GMT
Content-Type: text/html
Content-Length: 195
Connection: close
WWW-Authenticate: Basic realm="Username and Password Required"

• http://domoticz.vanveldhuizen.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
77.248.139.109
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		301
https://domoticz.vanveldhuizen.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 108.19 %
Other inline scripts (∑/total): 0/0		0.120
A
Visible Content: 301 Moved Permanently nginx/1.14.2
Server: nginx/1.14.2
Date: Tue, 24 Sep 2019 18:13:10 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: https://domoticz.vanveldhuizen.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• https://domoticz.vanveldhuizen.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 109.03 %
Other inline scripts (∑/total): 0/0		2.184
N
Not Found
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Visible Content: 404 Not Found nginx/1.14.2
Server: nginx/1.14.2
Date: Tue, 24 Sep 2019 18:13:10 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

 

7. Comments


1. General Results, most used to calculate the result

Aname "domoticz.vanveldhuizen.org" is subdomain, public suffix is "org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)"
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
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://domoticz.vanveldhuizen.org/ 77.248.139.109


Url with incomplete Content-Type - header - missing charset
https://domoticz.vanveldhuizen.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de


Url with incomplete Content-Type - header - missing charset
Ahttp://domoticz.vanveldhuizen.org/ 77.248.139.109
301
https://domoticz.vanveldhuizen.org/
Correct redirect http - https with the same domain name
CError - no version with Http-Status 200
HFatal error: No https - result with http-status 200, no encryption
Mhttps://domoticz.vanveldhuizen.org/ 77.248.139.109
401

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://domoticz.vanveldhuizen.org/ 77.248.139.109
401

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://domoticz.vanveldhuizen.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
XFatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 54.187.92.222:53
XFatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org / 54.187.92.222: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 54.187.92.222:53
XFatal error: Nameserver doesn't support TCP connection: ns2.duckdns.org: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 54.191.117.119:53
XFatal error: Nameserver doesn't support TCP connection: ns2.duckdns.org / 54.191.117.119: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 54.191.117.119:53
XFatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 52.26.169.94:53
XFatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org / 52.26.169.94: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 52.26.169.94:53

2. Header-Checks


3. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org / 54.187.92.222: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.mihosnet-38.nl: 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.
Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org / 54.191.117.119: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org / 52.26.169.94: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. 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.

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.
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
https://domoticz.vanveldhuizen.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
2.184 seconds
Warning: 404 needs more then one second
ADuration: 149776 milliseconds, 149.776 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
domoticz.vanveldhuizen.org
77.248.139.109
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
domoticz.vanveldhuizen.org
77.248.139.109
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

 no Tls.1.2
no Tls.1.1
no Tls.1.0
Self signed certificate

1CN=Arjen v. Veldhuizen, OU=None, O=None, L=Heerenveen, C=NL, emailAddress=arjen@vanveldhuizen.org


domoticz.vanveldhuizen.org
domoticz.vanveldhuizen.org
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok

domoticz.vanveldhuizen.org
domoticz.vanveldhuizen.org
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

 no Tls.1.2
no Tls.1.1
no Tls.1.0
Self signed certificate

1CN=Arjen v. Veldhuizen, OU=None, O=None, L=Heerenveen, C=NL, emailAddress=arjen@vanveldhuizen.org

 

9. Certificates

1.
1.
E=arjen@vanveldhuizen.org, CN=Arjen v. Veldhuizen, OU=None, O=None, L=Heerenveen, S=Friesland, C=NL
24.09.2019
21.09.2029
expires in 1607 days
1.
1.
E=arjen@vanveldhuizen.org, CN=Arjen v. Veldhuizen, OU=None, O=None, L=Heerenveen, S=Friesland, C=NL
24.09.2019

21.09.2029
expires in 1607 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:53FEC94B4D47A4BC2EA6C035C9568D7AABA7A0BF
Thumbprint:689ABCAC610E9703DF8A60BC14AE79A64EBD4C2D
SHA256 / Certificate:LRXxPxv7W+RQYqtnF5h6OuVKZL8aqO4CCy8Jk3mALoA=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):0fbea97e6ebd533e453fdbc8f642b885664c19a861c04818bceb84133f963fca
SHA256 hex / Subject Public Key Information (SPKI):0fbea97e6ebd533e453fdbc8f642b885664c19a861c04818bceb84133f963fca
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:


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

No CRT - CT-Log entries found

 

11. Html-Content - Entries

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

 

12. 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:

 

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

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
domoticz.vanveldhuizen.org



1
0
vanveldhuizen.duckdns.org



1
0
vanveldhuizen.org
0

no CAA entry found
1
0
duckdns.org
0

no CAA entry found
1
0
org
0

no CAA entry found
1
0

0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
duckdns.org
atlassian-domain-verification=ASAtJylfgPvFbteMew2nBgJCxkJo6U3zmyJact0e3jBlJ0DYhft99GgH/Qe8hZes
ok
1
0
vanveldhuizen.org

ok
1
0
vanveldhuizen.duckdns.org

ok
1
0
domoticz.vanveldhuizen.org


1
0
_acme-challenge.vanveldhuizen.duckdns.org

missing entry or wrong length
1
0
_acme-challenge.domoticz.vanveldhuizen.org

Name Error - The domain name does not exist
1
0
_acme-challenge.vanveldhuizen.duckdns.org.duckdns.org

 perhaps wrong
1
0
_acme-challenge.domoticz.vanveldhuizen.org.vanveldhuizen.org

Name Error - The domain name does not exist
1
0
_acme-challenge.vanveldhuizen.duckdns.org.vanveldhuizen.duckdns.org

 perhaps wrong
1
0
_acme-challenge.domoticz.vanveldhuizen.org.domoticz.vanveldhuizen.org

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=8551629e-dac1-4614-b041-bcd5bff686df

 

Last Result: https://check-your-website.server-daten.de/?q=domoticz.vanveldhuizen.org - 2019-09-24 20:10:51

 

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

 

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

 

 

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

 

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