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



N

No trusted Certificate

Checked:
01.08.2020 15:37:02


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
ownhost.synology.me
A
91.37.91.110
Mainz/Rheinland-Pfalz/Germany (DE) - Deutsche Telekom AG
Hostname: p5b255b6e.dip0.t-ipconnect.de
yes
1
0

AAAA

yes


www.ownhost.synology.me

Name Error
yes
1
0
www.ownhost.synology.me
A
91.37.91.110
Mainz/Rheinland-Pfalz/Germany (DE) - Deutsche Telekom AG
No Hostname found
no


*.ownhost.synology.me
A
91.37.91.110
yes



AAAA

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 46594, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 7, KeyTag 2569, DigestType 1 and Digest CboetNIEAmIIgf2YSJlEF4ANsmo=



DS with Algorithm 7, KeyTag 2569, DigestType 2 and Digest lOeYEG8DNQDmdWexl66RMsDpFnZNx0PFWp7KPHv1WeI=



1 RRSIG RR to validate DS RR found



RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.08.2020, 05:00:00 +, Signature-Inception: 01.08.2020, 04:00:00 +, KeyTag 46594, Signer-Name: (root)



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



4 DNSKEY RR found



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



Public Key with Algorithm 7, KeyTag 20555, Flags 256



Public Key with Algorithm 7, KeyTag 52877, Flags 256



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



3 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner me., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 15.08.2020, 15:17:35 +, Signature-Inception: 25.07.2020, 14:17:35 +, KeyTag 2569, Signer-Name: me



RRSIG-Owner me., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 15.08.2020, 15:17:35 +, Signature-Inception: 25.07.2020, 14:17:35 +, KeyTag 20555, Signer-Name: me



RRSIG-Owner me., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 15.08.2020, 15:17:35 +, Signature-Inception: 25.07.2020, 14:17:35 +, KeyTag 53233, Signer-Name: me



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



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



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



Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 2569, DigestType 1 and Digest "CboetNIEAmIIgf2YSJlEF4ANsmo=" 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 2569, DigestType 2 and Digest "lOeYEG8DNQDmdWexl66RMsDpFnZNx0PFWp7KPHv1WeI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: synology.me
synology.me
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 "i7p6ivvlm46fe4rml0dclpu3jjhb91jg" between the hashed NSEC3-owner "i7mhrttojfkmod70eida5t6ks6gqtsa2" and the hashed NextOwner "i7pdps0rdpm3nddgtcb6cgh0abh3npuc". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner i7mhrttojfkmod70eida5t6ks6gqtsa2.me., Algorithm: 7, 2 Labels, original TTL: 8400 sec, Signature-expiration: 15.08.2020, 15:17:35 +, Signature-Inception: 25.07.2020, 14:17:35 +, KeyTag 20555, Signer-Name: me



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "fsip6fkr2u8cf2kkg7scot4glihao6s1" as Owner. That's the Hash of "me" with the NextHashedOwnerName "fsj06ffj5gk2oparhlbv052e4ab9v77m". So that domain name is the Closest Encloser of "synology.me". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner fsip6fkr2u8cf2kkg7scot4glihao6s1.me., Algorithm: 7, 2 Labels, original TTL: 8400 sec, Signature-expiration: 22.08.2020, 13:36:18 +, Signature-Inception: 01.08.2020, 12:36:18 +, KeyTag 20555, Signer-Name: me



0 DNSKEY RR found




Zone: ownhost.synology.me
ownhost.synology.me
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.ownhost.synology.me
www.ownhost.synology.me
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.ownhost.synology.me
  ddns-ns1.quickconnect.to

ownhost.synology.me
  ddns-ns1.quickconnect.to
157.245.20.209
Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC

synology.me
  ddns-ns1.quickconnect.to
157.245.20.209
Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC


  ddns-ns2.quickconnect.to
68.183.254.129
London/England/United Kingdom (GB) - DigitalOcean, LLC

me
  a0.nic.me / ns009b.app8.nrt1.afilias-nst.info


  a2.nic.me / LHR4


  b0.nic.me / ns009b.app3.ams2.afilias-nst.info


T  b2.nic.me / LHR4


  c0.nic.me / ns009b.app3.ams2.afilias-nst.info


  ns.nic.me


4. SOA-Entries


Domain:me
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:me
Zone-Name:me
Primary:ns.nic.me
Mail:noc.afilias-nst.info
Serial:2010959328
Refresh:3600
Retry:3600
Expire:3600000
TTL:8400
num Entries:5


Domain:synology.me
Zone-Name:synology.me
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:414056689
Refresh:3600
Retry:300
Expire:6040000
TTL:3600
num Entries:1


Domain:synology.me
Zone-Name:synology.me
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:414056694
Refresh:3600
Retry:300
Expire:6040000
TTL:3600
num Entries:1


Domain:ownhost.synology.me
Zone-Name:synology.me
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:414056774
Refresh:3600
Retry:300
Expire:6040000
TTL:3600
num Entries:1


Domain:www.ownhost.synology.me
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
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://www.ownhost.synology.me/
91.37.91.110
302
http://www.ownhost.synology.me:5000/
Html is minified: 111.29 %
0.040
D
Server: nginx
Date: Sat, 01 Aug 2020 13:37:39 GMT
Content-Type: text/html
Content-Length: 138
Connection: close
Location: http://www.ownhost.synology.me:5000/

• http://ownhost.synology.me/
91.37.91.110 GZip used - 9015 / 43788 - 79.41 %
200

Html is minified: 134.88 %
0.993
H
Server: nginx
Date: Sat, 01 Aug 2020 13:37:39 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 9015
Connection: close
X-Powered-By: PHP/5.5.9-1ubuntu4.22
Link: <http://ownhost.synology.me/wp-json/>; rel="https://api.w.org/"
Vary: Accept-Encoding
Content-Encoding: gzip

• http://www.ownhost.synology.me:5000/

-14

10.020
T
Timeout - The operation has timed out

• https://ownhost.synology.me/
91.37.91.110
302
https://ownhost.synology.me:5001/
Html is minified: 111.29 %
2.250
N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Server: nginx
Date: Sat, 01 Aug 2020 13:37:40 GMT
Content-Type: text/html
Content-Length: 138
Connection: close
Location: https://ownhost.synology.me:5001/

• https://www.ownhost.synology.me/
91.37.91.110
302
https://www.ownhost.synology.me:5001/
Html is minified: 111.29 %
2.247
N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Server: nginx
Date: Sat, 01 Aug 2020 13:37:42 GMT
Content-Type: text/html
Content-Length: 138
Connection: close
Location: https://www.ownhost.synology.me:5001/

• https://ownhost.synology.me:5001/

-14

10.010
T
Timeout - The operation has timed out

• https://www.ownhost.synology.me:5001/

-14

10.026
T
Timeout - The operation has timed out

• http://ownhost.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
91.37.91.110
Inline-JavaScript (∑/total): 1/2229 Inline-CSS (∑/total): 1/160
404

Html is minified: 125.83 %
0.080
A
Not Found
Visible Content: &copy; 2020 Synology Inc.
Info: Html-Content with meta and/or script, may be a problem creating a Letsencrypt certificate using http-01 validation
Server: nginx
Date: Sat, 01 Aug 2020 13:37:45 GMT
Content-Type: text/html
Content-Length: 11939
Connection: close
ETag: "5eb9cd6d-2ea3"

• http://www.ownhost.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
91.37.91.110 GZip used - 8447 / 11939 - 29.25 %
Inline-JavaScript (∑/total): 1/2229 Inline-CSS (∑/total): 1/160
404

Html is minified: 125.83 %
0.050
A
Not Found
Visible Content: &copy; 2020 Synology Inc.
Info: Html-Content with meta and/or script, may be a problem creating a Letsencrypt certificate using http-01 validation
Server: nginx
Date: Sat, 01 Aug 2020 13:37:45 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
ETag: W/"5eb9cd6d-2ea3"
Content-Encoding: gzip

• https://91.37.91.110/
91.37.91.110
302
https://91.37.91.110:5001/
Html is minified: 111.29 %
2.243
N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Server: nginx
Date: Sat, 01 Aug 2020 13:37:45 GMT
Content-Type: text/html
Content-Length: 138
Connection: close
Location: https://91.37.91.110:5001/

• https://91.37.91.110:5001/

-14

10.044
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "ownhost.synology.me" is domain, public suffix is ".synology.me", top-level-domain is ".me", top-level-domain-type is "country-code", Country is Montenegro, tld-manager is "Government of Montenegro", num .me-domains preloaded: 1509 (complete: 128404)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: ownhost.synology.me 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: ownhost.synology.me 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 - only one version with Http-Status 200
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):1 complete Content-Type - header (3 urls)
http://ownhost.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.37.91.110


Url with incomplete Content-Type - header - missing charset
http://www.ownhost.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.37.91.110


Url with incomplete Content-Type - header - missing charset
Bhttps://ownhost.synology.me/ 91.37.91.110
302

Missing HSTS-Header
Bhttps://www.ownhost.synology.me/ 91.37.91.110
302

Missing HSTS-Header
Dhttp://www.ownhost.synology.me/ 91.37.91.110
302
http://www.ownhost.synology.me:5000/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Hfatal error: No https - result with http-status 200, no encryption
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.
Nhttps://ownhost.synology.me/ 91.37.91.110
302
https://ownhost.synology.me:5001/
Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://www.ownhost.synology.me/ 91.37.91.110
302
https://www.ownhost.synology.me:5001/
Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://91.37.91.110/ 91.37.91.110
302
https://91.37.91.110:5001/
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 the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain ownhost.synology.me, 1 ip addresses, 1 different http results.

2. DNS- and NameServer - Checks

AInfo:: 23 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 23 Queries complete, 21 with IPv6, 2 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Bad (greater 8):: An average of 11.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to, 2 Name Servers included in Delegation: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to, 2 Name Servers included in 1 Zone definitions: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to, 1 Name Servers listed in SOA.Primary: ddns-ns1.quickconnect.to.
AGood: Only one SOA.Primary Name Server found.: ddns-ns1.quickconnect.to.
AGood: SOA.Primary Name Server included in the delegation set.: ddns-ns1.quickconnect.to.
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: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to
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: 2 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 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.: 2 Name Servers, 1 Top Level Domain: to
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: quickconnect.to
AGood: Name servers with different Country locations found: 2 Name Servers, 2 Countries: DE, GB
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 157., 68., 2 different subnets (first two Bytes): 157.245., 68.183., 2 different subnets (first three Bytes): 157.245.20., 68.183.254.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
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
XNameserver Timeout checking EDNS512: b2.nic.me
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: b2.nic.me: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (LHR4). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ddns-ns1.quickconnect.to: 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: ns.nic.me: 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
Agood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates

3. Content- and Performance-critical Checks

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 2 complete.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 2 img-elements without alt-attribute, 0 img-elements with empty alt-attribute found.
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: 115320 milliseconds, 115.320 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
ownhost.synology.me
91.37.91.110
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
ownhost.synology.me
91.37.91.110
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
Tls.1.2
no Tls.1.1
no Tls.1.0
Self signed certificate
1CN=synology.com, O=Synology Inc., L=Taipei, C=TW


www.ownhost.synology.me
91.37.91.110
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok

www.ownhost.synology.me
91.37.91.110
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
Tls.1.2
no Tls.1.1
no Tls.1.0
Self signed certificate
1CN=synology.com, O=Synology Inc., L=Taipei, C=TW


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

91.37.91.110
91.37.91.110
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
Self signed certificate
1CN=synology.com, O=Synology Inc., L=Taipei, C=TW


9. Certificates

1.
1.
CN=synology.com, O=Synology Inc., L=Taipei, C=TW
27.04.2017
12.01.2037
expires in 6002 days

1.
1.
CN=synology.com, O=Synology Inc., L=Taipei, C=TW
27.04.2017

12.01.2037
expires in 6002 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:009E6EB80D2DCBCBF7
Thumbprint:AA2DF8B61CB47A577A01C5B6F5BB8E70045D6035
SHA256 / Certificate:WuuBSr9f0sIQOOx+25ww0/NIJ2mjqxnF/k37HqkD1s4=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):2f78db5ae4a37ef85a951d2ce1e89f764dd48a27c50b2bb3eac4fdb0ca9ea2e1
SHA256 hex / Subject Public Key Information (SPKI):086e6202b1a1b2e70ce199bdcca8b2c04572970ac20cd3bd132881f8886c7e5e
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:

RevocationStatusUnknown: The revocation function was unable to check revocation for the certificate.
OfflineRevocation: The revocation function was unable to check revocation because the revocation server was offline.


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
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1753892487
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-07-09 12:23:52
2020-10-07 12:23:52
ownhost.synology.me - 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
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
3063446455
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-07-09 10:23:52
2020-10-07 10:23:52
ownhost.synology.me
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: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to

QNr.DomainTypeNS used
1
to
NS
g.root-servers.net (2001:500:12::d0d)

Answer: colo.tonic.to, frankfurt.tonic.to, helsinki.tonic.to, newyork.tonic.to, singapore.tonic.to, sydney.tonic.to, tonic.to
2
ddns-ns1.quickconnect.to
NS
colo.tonic.to (216.74.32.101)

Answer: ns-1412.awsdns-48.org, ns-1987.awsdns-56.co.uk, ns-55.awsdns-06.com, ns-597.awsdns-10.net
3
ddns-ns2.quickconnect.to
NS
colo.tonic.to (216.74.32.101)

Answer: ns-1412.awsdns-48.org, ns-1987.awsdns-56.co.uk, ns-55.awsdns-06.com, ns-597.awsdns-10.net
4
org
NS
h.root-servers.net (2001:500:1::53)

Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
5
ns-1412.awsdns-48.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: g-ns-1075.awsdns-48.org, g-ns-1648.awsdns-48.org, g-ns-176.awsdns-48.org, g-ns-754.awsdns-48.org

Answer: g-ns-1075.awsdns-48.org
205.251.196.51, 2600:9000:5304:3300::1

Answer: g-ns-1648.awsdns-48.org
205.251.198.112, 2600:9000:5306:7000::1

Answer: g-ns-176.awsdns-48.org
205.251.192.176, 2600:9000:5300:b000::1

Answer: g-ns-754.awsdns-48.org
205.251.194.242, 2600:9000:5302:f200::1
6
uk
NS
j.root-servers.net (2001:503:c27::2:30)

Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
7
ns-1987.awsdns-56.co.uk
NS
dns1.nic.uk (2a01:618:400::1)

Answer: g-ns-1531.awsdns-56.co.uk, g-ns-1852.awsdns-56.co.uk, g-ns-376.awsdns-56.co.uk, g-ns-952.awsdns-56.co.uk

Answer: g-ns-1531.awsdns-56.co.uk
205.251.197.251, 2600:9000:5305:fb00::1

Answer: g-ns-1852.awsdns-56.co.uk
205.251.199.60, 2600:9000:5307:3c00::1

Answer: g-ns-376.awsdns-56.co.uk
205.251.193.120, 2600:9000:5301:7800::1

Answer: g-ns-952.awsdns-56.co.uk
205.251.195.184, 2600:9000:5303:b800::1
8
com
NS
d.root-servers.net (2001:500:2d::d)

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
9
ns-55.awsdns-06.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1158.awsdns-06.com, g-ns-1734.awsdns-06.com, g-ns-582.awsdns-06.com, g-ns-7.awsdns-06.com

Answer: g-ns-1158.awsdns-06.com
205.251.196.134, 2600:9000:5304:8600::1

Answer: g-ns-1734.awsdns-06.com
205.251.198.198, 2600:9000:5306:c600::1

Answer: g-ns-582.awsdns-06.com
205.251.194.70, 2600:9000:5302:4600::1

Answer: g-ns-7.awsdns-06.com
205.251.192.7, 2600:9000:5300:700::1
10
net
NS
d.root-servers.net (2001:500:2d::d)

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
11
ns-597.awsdns-10.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1354.awsdns-10.net, g-ns-1930.awsdns-10.net, g-ns-459.awsdns-10.net, g-ns-780.awsdns-10.net

Answer: g-ns-1354.awsdns-10.net
205.251.197.74, 2600:9000:5305:4a00::1

Answer: g-ns-1930.awsdns-10.net
205.251.199.138, 2600:9000:5307:8a00::1

Answer: g-ns-459.awsdns-10.net
205.251.193.203, 2600:9000:5301:cb00::1

Answer: g-ns-780.awsdns-10.net
205.251.195.12, 2600:9000:5303:c00::1
12
ns-1412.awsdns-48.org: 205.251.197.132
A
g-ns-1075.awsdns-48.org (2600:9000:5304:3300::1)
13
ns-1412.awsdns-48.org: 2600:9000:5305:8400::1
AAAA
g-ns-1075.awsdns-48.org (2600:9000:5304:3300::1)
14
ns-1987.awsdns-56.co.uk: 205.251.199.195
A
g-ns-1531.awsdns-56.co.uk (2600:9000:5305:fb00::1)
15
ns-1987.awsdns-56.co.uk: 2600:9000:5307:c300::1
AAAA
g-ns-1531.awsdns-56.co.uk (2600:9000:5305:fb00::1)
16
ns-55.awsdns-06.com: 205.251.192.55
A
g-ns-1158.awsdns-06.com (2600:9000:5304:8600::1)
17
ns-55.awsdns-06.com: 2600:9000:5300:3700::1
AAAA
g-ns-1158.awsdns-06.com (2600:9000:5304:8600::1)
18
ns-597.awsdns-10.net: 205.251.194.85
A
g-ns-1354.awsdns-10.net (2600:9000:5305:4a00::1)
19
ns-597.awsdns-10.net: 2600:9000:5302:5500::1
AAAA
g-ns-1354.awsdns-10.net (2600:9000:5305:4a00::1)
20
ddns-ns1.quickconnect.to: 157.245.20.209
A
ns-1412.awsdns-48.org (2600:9000:5305:8400::1)
21
ddns-ns1.quickconnect.to: No AAAA record found
AAAA
ns-1412.awsdns-48.org (2600:9000:5305:8400::1)
22
ddns-ns2.quickconnect.to: 68.183.254.129
A
ns-1412.awsdns-48.org (2600:9000:5305:8400::1)
23
ddns-ns2.quickconnect.to: No AAAA record found
AAAA
ns-1412.awsdns-48.org (2600:9000:5305:8400::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
ownhost.synology.me
0

no CAA entry found
1
0
synology.me
5
issue
letsencrypt.org
1
0
me
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
ownhost.synology.me

ok
1
0
_acme-challenge.ownhost.synology.me

missing entry or wrong length
1
0
_acme-challenge.ownhost.synology.me.ownhost.synology.me

perhaps wrong
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=6694d80a-bbd1-45ba-8a60-1e7f175fb0d5


Last Result: https://check-your-website.server-daten.de/?q=ownhost.synology.me - 2020-08-01 15:37:02


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

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