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



N

No trusted Certificate

Checked:
04.06.2019 10:21:31


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
thylbert.synology.me
A
109.135.7.244
/BE
Hostname: 244.7-135-109.adsl-fix.isp.belgacom.be
yes
1
0

AAAA

yes


www.thylbert.synology.me
A
109.135.7.244
/BE
Hostname: 244.7-135-109.adsl-fix.isp.belgacom.be
yes
1
0

AAAA

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



1 RRSIG RR to validate DNSKEY RR found



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



1 RRSIG RR to validate DS RR found



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



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 25266 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 27110, Flags 256



Public Key with Algorithm 7, KeyTag 49847, 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: 22.06.2019, 15:20:14 +, Signature-Inception: 01.06.2019, 14:20:14 +, KeyTag 2569, Signer-Name: me



RRSIG-Owner me., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.06.2019, 15:20:14 +, Signature-Inception: 01.06.2019, 14:20:14 +, KeyTag 27110, Signer-Name: me



RRSIG-Owner me., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.06.2019, 15:20:14 +, Signature-Inception: 01.06.2019, 14:20:14 +, 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 27110 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 "i7l5nt3mtoi274sf2bgtkt755t4ib6jt" and the hashed NextOwner "i7pqpvvh0900oa3pltq23h3ikki57qc3". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner i7l5nt3mtoi274sf2bgtkt755t4ib6jt.me., Algorithm: 7, 2 Labels, original TTL: 8400 sec, Signature-expiration: 22.06.2019, 15:20:14 +, Signature-Inception: 01.06.2019, 14:20:14 +, KeyTag 27110, Signer-Name: me



0 DNSKEY RR found




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



0 DNSKEY RR found




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


3. Name Servers

DomainNameserverNS-IP
www.thylbert.synology.me
  ddns-ns1.quickconnect.to / ip-10-0-40-80

thylbert.synology.me
  ddns-ns1.quickconnect.to / ip-10-0-40-80
18.194.15.61
Frankfurt/Hessen/DE

synology.me
  ddns-ns1.quickconnect.to / ip-10-0-40-80


  ddns-ns2.quickconnect.to / ip-10-0-45-9

me
  a0.nic.me / ns009b.app6.mia2.afilias-nst.info


  a2.nic.me / 2.ber.pch


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


  b2.nic.me / 4.fra.pch


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


4. SOA-Entries


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


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


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


Domain:www.thylbert.synology.me
Zone-Name:
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:10259881
Refresh:3600
Retry:300
Expire:604800
TTL:3600
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://thylbert.synology.me:51276/
109.135.7.244
400

0.093
M
Bad Request
Date: Tue, 04 Jun 2019 08:21:56 GMT
Content-Type: text/html
Content-Length: 248
Connection: close

• http://www.thylbert.synology.me:51276/
109.135.7.244
400

0.073
M
Bad Request
Date: Tue, 04 Jun 2019 08:21:56 GMT
Content-Type: text/html
Content-Length: 248
Connection: close

• https://thylbert.synology.me:51276/
109.135.7.244
200

1.437
I
Date: Tue, 04 Jun 2019 08:21:57 GMT
Content-Type: text/html; charset="UTF-8"
Transfer-Encoding: chunked
Connection: close
Cache-control: no-store
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Content-Security-Policy: base-uri 'self'; connect-src ws: wss: *; default-src 'self' 'unsafe-eval' data: blob: https://*.synology.com https://www.synology.cn/; font-src 'self' data: https://*.googleapis.com https://*.gstatic.com; form-action 'self'; frame-ancestors 'self' https://gofile.me http://gofile.me; frame-src 'self' data: blob: https://*.synology.com https://www.synology.cn/ http://*.synology.com http://*.synology.cn; img-src 'self' data: blob: https://*.google.com https://*.googleapis.com http://*.googlecode.com https://*.gstatic.com; media-src 'self' data: about:; report-uri webman/csp_report.cgi; script-src 'self' 'unsafe-eval' data: blob: https://*.synology.com https://www.synology.cn/ https://*.google.com https://*.googleapis.com; style-src 'self' 'unsafe-inline' https://*.googleapis.com;

• https://www.thylbert.synology.me:51276/
109.135.7.244
200

1.203
N
Certificate error: RemoteCertificateNameMismatch
Date: Tue, 04 Jun 2019 08:21:59 GMT
Content-Type: text/html; charset="UTF-8"
Transfer-Encoding: chunked
Connection: close
Cache-control: no-store
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Content-Security-Policy: base-uri 'self'; connect-src ws: wss: *; default-src 'self' 'unsafe-eval' data: blob: https://*.synology.com https://www.synology.cn/; font-src 'self' data: https://*.googleapis.com https://*.gstatic.com; form-action 'self'; frame-ancestors 'self' https://gofile.me http://gofile.me; frame-src 'self' data: blob: https://*.synology.com https://www.synology.cn/ http://*.synology.com http://*.synology.cn; img-src 'self' data: blob: https://*.google.com https://*.googleapis.com http://*.googlecode.com https://*.gstatic.com; media-src 'self' data: about:; report-uri webman/csp_report.cgi; script-src 'self' 'unsafe-eval' data: blob: https://*.synology.com https://www.synology.cn/ https://*.google.com https://*.googleapis.com; style-src 'self' 'unsafe-inline' https://*.googleapis.com;

• http://thylbert.synology.me:51276/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
109.135.7.244
400

0.077
M
Bad Request
Visible Content:
Date: Tue, 04 Jun 2019 08:22:00 GMT
Content-Type: text/html
Content-Length: 248
Connection: close

• http://www.thylbert.synology.me:51276/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
109.135.7.244
400

0.074
M
Bad Request
Visible Content:
Date: Tue, 04 Jun 2019 08:22:00 GMT
Content-Type: text/html
Content-Length: 248
Connection: close

7. Comments


1. General Results, most used to calculate the result

Aname "thylbert.synology.me" is domain, public suffix is "synology.me", top-level-domain-type is "country-code", Country is Montenegro, tld-manager is "Government of Montenegro"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
Agood: destination is https
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Bhttps://thylbert.synology.me:51276/ 109.135.7.244
200

Missing HSTS-Header
Bhttps://www.thylbert.synology.me:51276/ 109.135.7.244
200

Missing HSTS-Header
CError - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
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.
Ihttps://thylbert.synology.me:51276/ 109.135.7.244
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
Ihttps://www.thylbert.synology.me:51276/ 109.135.7.244
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
Mhttp://thylbert.synology.me:51276/ 109.135.7.244
400

Misconfiguration - main pages should never send http status 400 - 499
Mhttp://www.thylbert.synology.me:51276/ 109.135.7.244
400

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://www.thylbert.synology.me:51276/ 109.135.7.244
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch

2. DNS- and NameServer - Checks

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
Nameserver doesn't pass all EDNS-Checks: ddns-ns1.quickconnect.to: 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 (ip-10-0-40-80). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ddns-ns1.quickconnect.to: 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 (ip-10-0-40-80). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ddns-ns1.quickconnect.to / 18.194.15.61: 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 (ip-10-0-40-80). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ddns-ns2.quickconnect.to: 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 (ip-10-0-45-9). 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.

3. Content- and Performance-critical Checks

http://thylbert.synology.me:51276/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 109.135.7.244
400

Fatal: Check of /.well-known/acme-challenge/random-filename has a http status between 400 and 499, but not 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.thylbert.synology.me:51276/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 109.135.7.244
400

Fatal: Check of /.well-known/acme-challenge/random-filename has a http status between 400 and 499, but not 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge may not work. 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
ADuration: 55113 milliseconds, 55.113 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
thylbert.synology.me
109.135.7.244
51276
ok
Tls12
DiffieHellman
2048
Aes128
128
Sha256
error checking OCSP stapling
ok
thylbert.synology.me
109.135.7.244
51276
ok
Tls12

DiffieHellman
2048
Aes128
128
Sha256
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
Chain - incomplete
1CN=thylbert.synology.me

2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


www.thylbert.synology.me
109.135.7.244
51276
name does not match
Tls12
DiffieHellman
2048
Aes128
128
Sha256
error checking OCSP stapling
ok

www.thylbert.synology.me
109.135.7.244
51276
name does not match
Tls12

DiffieHellman
2048
Aes128
128
Sha256
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
Chain - incomplete
1CN=thylbert.synology.me

2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


9. Certificates

1.
1.
CN=thylbert.synology.me
08.05.2019
06.08.2019
1149 days expired
thylbert.synology.me - 1 entry
1.
1.
CN=thylbert.synology.me
08.05.2019

06.08.2019
1149 days expired
thylbert.synology.me - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03AE34D123BA776C3463E39A988204362EC9
Thumbprint:CB6F0410671FB173DA467C7B8AFEC7498F66984C
SHA256 / Certificate:iHZvDLAo3mebxZINH7BdmxiZzgqrqEw/o2Bt4Uhy7Fc=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):5d59cf89bd4ed519288203ef3fb06fcedd7b671b07b911189ce642bdd93235db
SHA256 hex / Subject Public Key Information (SPKI):5d59cf89bd4ed519288203ef3fb06fcedd7b671b07b911189ce642bdd93235db
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Server Authentication (1.3.6.1.5.5.7.3.1), Client Authentication (1.3.6.1.5.5.7.3.2)


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
560 days expired


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
560 days expired


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
363 days expired


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
363 days expired


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
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:



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

Summary

No data found or small Code-update

Details

Small Code Update - wait one minute


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.thylbert.synology.me
0

no CAA entry found
1
0
thylbert.synology.me
0

no CAA entry found
1
0
synology.me
0

no CAA entry found
1
0
me
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
thylbert.synology.me

ok
1
0
www.thylbert.synology.me

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

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

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

perhaps wrong
1
0
_acme-challenge.www.thylbert.synology.me.thylbert.synology.me

perhaps wrong
1
0
_acme-challenge.www.thylbert.synology.me.www.thylbert.synology.me

perhaps wrong
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.



Permalink: https://check-your-website.server-daten.de/?i=e3e5c4ca-bdff-4b85-a385-6314e6e6f2f7


Last Result: https://check-your-website.server-daten.de/?q=thylbert.synology.me%3a51276 - 2019-06-04 10:21:31


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

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

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro