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


 

 

A

 

Top config

 

Checked:
25.04.2025 18:09:50

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
nextcloud.amyliv.de
A
91.41.7.140
Koblenz/Rheinland-Pfalz/Germany (DE) - Deutsche Telekom AG
Hostname: p5b29078c.dip0.t-ipconnect.de
yes
1
0

AAAA

yes


www.nextcloud.amyliv.de

Name Error
yes
1
0
*.amyliv.de
A

yes



AAAA

yes



CNAME

yes


*.nextcloud.amyliv.de
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=






Status: Valid because published






3 DNSKEY RR found






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






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






Public Key with Algorithm 8, KeyTag 53148, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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

de
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 26755, DigestType 2 and Digest 80E1eAmllUMRzLgq3hFMbB1ySnXAOVE3qjl4A1Ql540=






1 RRSIG RR to validate DS RR found






RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 08.05.2025, 14:00:00 +, Signature-Inception: 25.04.2025, 13:00:00 +, KeyTag 53148, Signer-Name: (root)






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






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 5808, Flags 256






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






Public Key with Algorithm 8, KeyTag 34356, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 07.05.2025, 18:12:56 +, Signature-Inception: 23.04.2025, 16:42:56 +, KeyTag 26755, Signer-Name: de






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






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



Zone: amyliv.de

amyliv.de
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 "6egcbbl282509hd5s2k845ban73hcc35" between the hashed NSEC3-owner "6egajeie32l7vepmgo4l9g40tje9rdd5" and the hashed NextOwner "6egen910a7uq0gjroinovgjhfeacicm6". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner 6egajeie32l7vepmgo4l9g40tje9rdd5.de., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 05.05.2025, 07:12:58 +, Signature-Inception: 21.04.2025, 05:42:58 +, KeyTag 5808, Signer-Name: de






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "tjlb7qbojvmlf1s6gdriru7vsms1lg16" as Owner. That's the Hash of "de" with the NextHashedOwnerName "tjlcsjat4ljtvo0tjncrrdf6kf6onefb". So that domain name is the Closest Encloser of "amyliv.de". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner tjlb7qbojvmlf1s6gdriru7vsms1lg16.de., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 05.05.2025, 07:12:58 +, Signature-Inception: 21.04.2025, 05:42:58 +, KeyTag 5808, Signer-Name: de






0 DNSKEY RR found









Zone: nextcloud.amyliv.de

nextcloud.amyliv.de
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: www.nextcloud.amyliv.de

www.nextcloud.amyliv.de
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.nextcloud.amyliv.de
  docks20.rzone.de

nextcloud.amyliv.de
  docks20.rzone.de / 8560_de-fra-fr7_strato-customer-docks
217.160.80.147
Frankfurt am Main/Hesse/Germany (DE) - IONOS SE


 
2001:8d8:fe:53:5747:2a74:d:20
Frankfurt am Main/Hesse/Germany (DE) - 1&1 IONOS SE

amyliv.de
  docks20.rzone.de / 8560_de-fra-fr7_strato-customer-docks
217.160.80.147
Frankfurt am Main/Hesse/Germany (DE) - IONOS SE


 
2001:8d8:fe:53:5747:2a74:d:20
Frankfurt am Main/Hesse/Germany (DE) - 1&1 IONOS SE


  shades09.rzone.de / 15418_de-ber-rs_strato-customer-shades
185.132.34.136
Berlin/State of Berlin/Germany (DE) - DNSAS (eBGP DNS)


 
2607:f1c0:fe:53:185:132:34:136
Frankfurt am Main/Hesse/Germany (DE) - Fasthosts Internet Limited

de
  a.nic.de / ns-1.de.de8.knot


  f.nic.de / ns-1.de.de1.knot


  l.de.net / ns-1.de.fr1.knot


  n.de.net / s3.amx


  s.de.net / ns-2.de.de9.knot


  z.nic.de / ns-2.de.de2.bind

 

4. SOA-Entries


Domain:de
Zone-Name:de
Primary:f.nic.de
Mail:dns-operations.denic.de
Serial:1745597317
Refresh:7200
Retry:7200
Expire:3600000
TTL:7200
num Entries:6


Domain:amyliv.de
Zone-Name:amyliv.de
Primary:docks20.rzone.de
Mail:hostmaster.strato-rz.de
Serial:2025041570
Refresh:86400
Retry:7200
Expire:604800
TTL:300
num Entries:4


Domain:nextcloud.amyliv.de
Zone-Name:amyliv.de
Primary:docks20.rzone.de
Mail:hostmaster.strato-rz.de
Serial:2025041570
Refresh:86400
Retry:7200
Expire:604800
TTL:300
num Entries:2


Domain:www.nextcloud.amyliv.de
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
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://nextcloud.amyliv.de/
91.41.7.140
301
https://nextcloud.amyliv.de/
Html is minified: 109.21 %
0.037
A
Server: openresty
Date: Fri, 25 Apr 2025 16:10:20 GMT
Connection: keep-alive
Location: https://nextcloud.amyliv.de/
Content-Type: text/html
Content-Length: 166

• https://nextcloud.amyliv.de/
91.41.7.140 No Compression used - 1464 / 3485 - 42.01 % possible
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 104.50 %
Other inline scripts (∑/total): 0/0
2.300
A
Server: openresty
Date: Fri, 25 Apr 2025 16:10:20 GMT
Connection: keep-alive
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Robots-Tag: noindex, nofollow
X-XSS-Protection: 1; mode=block
Referrer-Policy: no-referrer
ETag: "d9d-632f5b8cbbc40"
Accept-Ranges: bytes
Strict-Transport-Security: max-age=63072000; preload
X-Served-By: nextcloud.amyliv.de
Content-Length: 3485
Last-Modified: Thu, 17 Apr 2025 09:06:49 GMT

• http://nextcloud.amyliv.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
91.41.7.140
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
301
https://nextcloud.amyliv.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 109.21 %
Other inline scripts (∑/total): 0/0
0.023
A
Visible Content:
Server: openresty
Date: Fri, 25 Apr 2025 16:10:24 GMT
Connection: keep-alive
Location: https://nextcloud.amyliv.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Type: text/html
Content-Length: 166

• https://nextcloud.amyliv.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
gzip used - 111 / 150 - 26.00 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 110.29 %
Other inline scripts (∑/total): 0/0
2.040
A
Not Found
Visible Content:
Server: openresty
Date: Fri, 25 Apr 2025 16:10:24 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Strict-Transport-Security: max-age=63072000; preload
Content-Type: text/html
Content-Encoding: gzip
Content-Length: 111

• https://91.41.7.140/
91.41.7.140
-103


0.060
P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: '112' (FF: SSL_ERROR_UNRECOGNIZED_NAME_ALERT)

 

7. Comments


1. General Results, most used to calculate the result

Aname "nextcloud.amyliv.de" is subdomain, public suffix is ".de", top-level-domain is ".de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG", num .de-domains preloaded: 10860 (complete: 270180)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: nextcloud.amyliv.de 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: nextcloud.amyliv.de 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: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: No cookie sent via http.
AGood: HSTS has preload directive
Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
https://nextcloud.amyliv.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de


Url with incomplete Content-Type - header - missing charset
Ahttp://nextcloud.amyliv.de/ 91.41.7.140
301
https://nextcloud.amyliv.de/
Correct redirect http - https with the same domain name
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain nextcloud.amyliv.de, 1 ip addresses.
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.nextcloud.amyliv.de

2. Header-Checks

Anextcloud.amyliv.de 91.41.7.140
X-Content-Type-Options
Ok: Header without syntax errors found: nosniff
A
Referrer-Policy
Ok: Header without syntax errors found: no-referrer
A
X-Frame-Options
Ok: Header without syntax errors found: SAMEORIGIN
B

Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls.
A
X-Xss-Protection
Ok: Header without syntax errors found: 1; mode=block
B

Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block
Fnextcloud.amyliv.de 91.41.7.140
Content-Security-Policy
Critical: Missing Header:
Fnextcloud.amyliv.de 91.41.7.140
Permissions-Policy
Critical: Missing Header:
Bnextcloud.amyliv.de 91.41.7.140
Cross-Origin-Embedder-Policy
Info: Missing Header
Bnextcloud.amyliv.de 91.41.7.140
Cross-Origin-Opener-Policy
Info: Missing Header
Bnextcloud.amyliv.de 91.41.7.140
Cross-Origin-Resource-Policy
Info: Missing Header

3. DNS- and NameServer - Checks

AInfo:: 49 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 49 Queries complete, 49 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 24.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: docks20.rzone.de, shades09.rzone.de, 2 Name Servers included in Delegation: docks20.rzone.de, shades09.rzone.de, 2 Name Servers included in 1 Zone definitions: docks20.rzone.de, shades09.rzone.de, 1 Name Servers listed in SOA.Primary: docks20.rzone.de.
AGood: Only one SOA.Primary Name Server found.: docks20.rzone.de.
AGood: SOA.Primary Name Server included in the delegation set.: docks20.rzone.de.
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: docks20.rzone.de, shades09.rzone.de
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
AGood: All name servers have ipv4- and ipv6-addresses.: 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: de
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: rzone.de
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: DE
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 185., 217., 2 different subnets (first two Bytes): 185.132., 217.160., 2 different subnets (first three Bytes): 185.132.34., 217.160.80.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 2 different subnets (first block): 2001:, 2607:, 2 different subnets (first two blocks): 2001:08d8:, 2607:f1c0:, 2 different subnets (first three blocks): 2001:08d8:00fe:, 2607:f1c0:00fe:, 2 different subnets (first four blocks): 2001:08d8:00fe:0053:, 2607:f1c0:00fe:0053:
AExcellent: Every Name Server IPv6-address starts with an unique Hex-block
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: docks20.rzone.de: 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
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.
https://nextcloud.amyliv.de/ 91.41.7.140
200

Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
AGood: No https + http status 200 with inline CSS / JavaScript found
AGood: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
AInfo: No img element found, no alt attribute checked
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
https://nextcloud.amyliv.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
2.040 seconds
Warning: 404 needs more then one second
ADuration: 145973 milliseconds, 145.973 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
nextcloud.amyliv.de
91.41.7.140
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
nextcloud.amyliv.de
91.41.7.140
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=nextcloud.amyliv.de


2CN=E5, O=Let's Encrypt, C=US


nextcloud.amyliv.de
nextcloud.amyliv.de
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

nextcloud.amyliv.de
nextcloud.amyliv.de
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=nextcloud.amyliv.de


2CN=E5, O=Let's Encrypt, C=US

 

9. Certificates

1.
1.
CN=nextcloud.amyliv.de
17.04.2025
16.07.2025
371 days expired
nextcloud.amyliv.de - 1 entry
1.
1.
CN=nextcloud.amyliv.de
17.04.2025

16.07.2025
371 days expired


nextcloud.amyliv.de - 1 entry

KeyalgorithmEC Public Key (384 bit, secp384r1)
Signatur:ECDSA SHA384
Serial Number:06A722AB16338955273E627C5E584F4A2F4D
Thumbprint:53E168D8ACD2991460866DE153C63ABDD6585F3D
SHA256 / Certificate:Tnn/gHzqMNSescPf9YBXtG33Uj2enaO9Nq1lyrgz180=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):afc05febb5f390229f9a7c3d85b89e9fba9cb2111bd795be5f6b040f66ca2517
SHA256 hex / Subject Public Key Information (SPKI):afc05febb5f390229f9a7c3d85b89e9fba9cb2111bd795be5f6b040f66ca2517 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://e5.o.lencr.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




2.
CN=E5, O=Let's Encrypt, C=US
13.03.2024
13.03.2027
expires in 234 days


2.
CN=E5, O=Let's Encrypt, C=US
13.03.2024

13.03.2027
expires in 234 days




KeyalgorithmEC Public Key (384 bit, secp384r1)
Signatur:SHA256 With RSA-Encryption
Serial Number:00838F6C63CEB1398C6206628315C9FDDE
Thumbprint:5F28D9C589EE4BF31A11B78C72B8D13F079DDC45
SHA256 / Certificate:Xf2zzzGybyPYfAnzoM72QvZAaan7fP4pJwu13A8eFrs=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):3586d4ecf070578cbd27aedce20b964e48bc149faeb9dad72f46b857869172b8
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Clientauthentifizierung (1.3.6.1.5.5.7.3.2), Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015
04.06.2035
expires in 3239 days


3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015

04.06.2035
expires in 3239 days




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008210CFB0D240E3594463E0BB63828B00
Thumbprint:CABD2A79A1076A31F21D253635CB039D4329A5E8
SHA256 / Certificate:lrzsBiZJdvN0YHeazyjFp8/oo8Cq4RqP/O4FwL3fCMY=
SHA256 hex / Cert (DANE * 0 1):96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SHA256 hex / PublicKey (DANE * 1 1):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SHA256 hex / Subject Public Key Information (SPKI):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
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)

Issuerlast 7 daysactivenum Certs
CN=E5, O=Let's Encrypt, C=US
0
0
6
CN=E6, O=Let's Encrypt, C=US
0
0
4

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
10222988598
leaf cert
CN=E5, O=Let's Encrypt, C=US
2025-04-25 09:34:29
2025-07-24 09:34:28
nextcloud.amyliv.de - 1 entries


10214074949
leaf cert
CN=E6, O=Let's Encrypt, C=US
2025-04-24 14:25:20
2025-07-23 14:25:19
nextcloud.amyliv.de - 1 entries


10214058418
leaf cert
CN=E6, O=Let's Encrypt, C=US
2025-04-24 14:23:39
2025-07-23 14:23:38
nextcloud.amyliv.de - 1 entries


10214043386
leaf cert
CN=E5, O=Let's Encrypt, C=US
2025-04-24 14:21:52
2025-07-23 14:21:51
nextcloud.amyliv.de - 1 entries


10166074239
leaf cert
CN=E5, O=Let's Encrypt, C=US
2025-04-20 10:55:32
2025-07-19 10:55:31
nextcloud.amyliv.de - 1 entries


10136961227
leaf cert
CN=E5, O=Let's Encrypt, C=US
2025-04-17 14:02:05
2025-07-16 14:02:04
nextcloud.amyliv.de - 1 entries


10136937937
leaf cert
CN=E5, O=Let's Encrypt, C=US
2025-04-17 13:59:13
2025-07-16 13:59:12
nextcloud.amyliv.de - 1 entries


10137493034
leaf cert
CN=E6, O=Let's Encrypt, C=US
2025-04-17 13:45:26
2025-07-16 13:45:25
nextcloud.amyliv.de - 1 entries


10137201416
leaf cert
CN=E5, O=Let's Encrypt, C=US
2025-04-17 13:42:45
2025-07-16 13:42:44
nextcloud.amyliv.de - 1 entries


10136609231
leaf cert
CN=E6, O=Let's Encrypt, C=US
2025-04-17 13:13:27
2025-07-16 13:13:26
nextcloud.amyliv.de - 1 entries


 

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

Issuerlast 7 daysactivenum Certs
CN=E5, O=Let's Encrypt, C=US
0
0
6
CN=E6, O=Let's Encrypt, C=US
0
0
4

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
18054370992
precert
CN=E5, O=Let's Encrypt, C=US
2025-04-25 07:34:29
2025-07-24 07:34:28
nextcloud.amyliv.de
1 entries


18040700095
precert
CN=E6, O=Let's Encrypt, C=US
2025-04-24 12:25:20
2025-07-23 12:25:19
nextcloud.amyliv.de
1 entries


18039437297
precert
CN=E6, O=Let's Encrypt, C=US
2025-04-24 12:23:39
2025-07-23 12:23:38
nextcloud.amyliv.de
1 entries


18039416799
leaf cert
CN=E5, O=Let's Encrypt, C=US
2025-04-24 12:21:52
2025-07-23 12:21:51
nextcloud.amyliv.de
1 entries


17957670881
precert
CN=E5, O=Let's Encrypt, C=US
2025-04-20 08:55:32
2025-07-19 08:55:31
nextcloud.amyliv.de
1 entries


17905730410
leaf cert
CN=E5, O=Let's Encrypt, C=US
2025-04-17 12:02:05
2025-07-16 12:02:04
nextcloud.amyliv.de
1 entries


17905695590
leaf cert
CN=E5, O=Let's Encrypt, C=US
2025-04-17 11:59:13
2025-07-16 11:59:12
nextcloud.amyliv.de
1 entries


17905523307
precert
CN=E6, O=Let's Encrypt, C=US
2025-04-17 11:45:26
2025-07-16 11:45:25
nextcloud.amyliv.de
1 entries


17905489967
precert
CN=E5, O=Let's Encrypt, C=US
2025-04-17 11:42:45
2025-07-16 11:42:44
nextcloud.amyliv.de
1 entries


17905143316
leaf cert
CN=E6, O=Let's Encrypt, C=US
2025-04-17 11:13:27
2025-07-16 11:13:26
nextcloud.amyliv.de
1 entries


 

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/


No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: docks20.rzone.de, shades09.rzone.de

 

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

Answer: a.nic.de, f.nic.de, l.de.net, n.de.net, s.de.net, z.nic.de
2
docks20.rzone.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-anyslv.ui-dns.de, ns1.rzone.de, ns2.rzone.de, ns4.rzone.de

Answer: ns1.rzone.de
193.141.3.6

Answer: ns2.rzone.de
81.169.144.234

Answer: ns4.rzone.de
192.166.192.224, 2a01:238:e100:f003::110
3
shades09.rzone.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-anyslv.ui-dns.de, ns1.rzone.de, ns2.rzone.de, ns4.rzone.de

Answer: ns1.rzone.de
193.141.3.6

Answer: ns2.rzone.de
81.169.144.234

Answer: ns4.rzone.de
192.166.192.224, 2a01:238:e100:f003::110
4
ns-anyslv.ui-dns.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-de.ui-dns.biz, ns-de.ui-dns.com, ns-de.ui-dns.de, ns-de.ui-dns.org

Answer: ns-de.ui-dns.de
185.132.32.193, 2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.193, 2607:f1c0:fe:53:185:132:32:193
5
biz
NS
d.root-servers.net (2001:500:2d::d)

Answer: a.gtld.biz, b.gtld.biz, c.gtld.biz, m.gtld.biz, n.gtld.biz, w.gtld.biz, x.gtld.biz, y.gtld.biz
6
ns-de.ui-dns.biz
NS
a.gtld.biz (2001:502:ad09::30)

Answer: ns-biz.ui-dns.biz, ns-biz.ui-dns.com, ns-biz.ui-dns.de, ns-biz.ui-dns.org

Answer: ns-biz.ui-dns.biz
185.132.33.195, 2001:8d8:fe:53:0:d9a0:51c3:100, 217.160.81.195, 2607:f1c0:fe:53:185:132:33:195
7
com
NS
e.root-servers.net (2001:500:a8::e)

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
8
ns-de.ui-dns.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns-com.ui-dns.biz, ns-com.ui-dns.com, ns-com.ui-dns.de, ns-com.ui-dns.org

Answer: ns-com.ui-dns.com
185.132.34.214, 2001:8d8:fe:53:0:d9a0:52d6:100, 217.160.82.214, 2607:f1c0:fe:53:185:132:34:214
9
org
NS
d.root-servers.net (2001:500:2d::d)

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
10
ns-de.ui-dns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns-org.ui-dns.biz, ns-org.ui-dns.com, ns-org.ui-dns.de, ns-org.ui-dns.org

Answer: ns-org.ui-dns.org
185.132.34.194, 2001:8d8:fe:53:0:d9a0:52c2:100, 217.160.82.194, 2607:f1c0:fe:53:185:132:34:194
11
ns-biz.ui-dns.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns-com.ui-dns.biz, ns-com.ui-dns.com, ns-com.ui-dns.de, ns-com.ui-dns.org

Answer: ns-com.ui-dns.com
185.132.34.214, 2001:8d8:fe:53:0:d9a0:52d6:100, 217.160.82.214, 2607:f1c0:fe:53:185:132:34:214
12
ns-biz.ui-dns.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-de.ui-dns.biz, ns-de.ui-dns.com, ns-de.ui-dns.de, ns-de.ui-dns.org

Answer: ns-de.ui-dns.de
185.132.32.193, 2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.193, 2607:f1c0:fe:53:185:132:32:193
13
ns-biz.ui-dns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns-org.ui-dns.biz, ns-org.ui-dns.com, ns-org.ui-dns.de, ns-org.ui-dns.org

Answer: ns-org.ui-dns.org
185.132.34.194, 2001:8d8:fe:53:0:d9a0:52c2:100, 217.160.82.194, 2607:f1c0:fe:53:185:132:34:194
14
ns-com.ui-dns.biz
NS
a.gtld.biz (2001:502:ad09::30)

Answer: ns-biz.ui-dns.biz, ns-biz.ui-dns.com, ns-biz.ui-dns.de, ns-biz.ui-dns.org

Answer: ns-biz.ui-dns.biz
185.132.33.195, 2001:8d8:fe:53:0:d9a0:51c3:100, 217.160.81.195, 2607:f1c0:fe:53:185:132:33:195
15
ns-com.ui-dns.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-de.ui-dns.biz, ns-de.ui-dns.com, ns-de.ui-dns.de, ns-de.ui-dns.org

Answer: ns-de.ui-dns.de
185.132.32.193, 2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.193, 2607:f1c0:fe:53:185:132:32:193
16
ns-com.ui-dns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns-org.ui-dns.biz, ns-org.ui-dns.com, ns-org.ui-dns.de, ns-org.ui-dns.org

Answer: ns-org.ui-dns.org
185.132.34.194, 2001:8d8:fe:53:0:d9a0:52c2:100, 217.160.82.194, 2607:f1c0:fe:53:185:132:34:194
17
ns-org.ui-dns.biz
NS
a.gtld.biz (2001:502:ad09::30)

Answer: ns-biz.ui-dns.biz, ns-biz.ui-dns.com, ns-biz.ui-dns.de, ns-biz.ui-dns.org

Answer: ns-biz.ui-dns.biz
185.132.33.195, 2001:8d8:fe:53:0:d9a0:51c3:100, 217.160.81.195, 2607:f1c0:fe:53:185:132:33:195
18
ns-org.ui-dns.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns-com.ui-dns.biz, ns-com.ui-dns.com, ns-com.ui-dns.de, ns-com.ui-dns.org

Answer: ns-com.ui-dns.com
185.132.34.214, 2001:8d8:fe:53:0:d9a0:52d6:100, 217.160.82.214, 2607:f1c0:fe:53:185:132:34:214
19
ns-org.ui-dns.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-de.ui-dns.biz, ns-de.ui-dns.com, ns-de.ui-dns.de, ns-de.ui-dns.org

Answer: ns-de.ui-dns.de
185.132.32.193, 2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.193, 2607:f1c0:fe:53:185:132:32:193
20
ns-anyslv.ui-dns.de: 185.132.32.247, 217.160.80.247
A
ns-de.ui-dns.de (2001:8d8:fe:53:0:d9a0:50c1:100)
21
ns-anyslv.ui-dns.de: 2001:8d8:fe:53:616e:7973:6c76:310a, 2607:f1c0:fe:53:185:132:32:247
AAAA
ns-de.ui-dns.de (2001:8d8:fe:53:0:d9a0:50c1:100)
22
ns-de.ui-dns.biz: 185.132.33.193, 217.160.81.193
A
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
23
ns-de.ui-dns.biz: 2001:8d8:fe:53:0:d9a0:51c1:100, 2607:f1c0:fe:53:185:132:33:193
AAAA
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
24
ns-de.ui-dns.com: 185.132.34.193, 217.160.82.193
A
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52d6:100)
25
ns-de.ui-dns.com: 2001:8d8:fe:53:0:d9a0:52c1:100, 2607:f1c0:fe:53:185:132:34:193
AAAA
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52d6:100)
26
ns-de.ui-dns.org: 185.132.35.193, 217.160.83.193
A
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:52c2:100)
27
ns-de.ui-dns.org: 2001:8d8:fe:53:0:d9a0:53c1:100, 2607:f1c0:fe:53:185:132:35:193
AAAA
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:52c2:100)
28
ns-biz.ui-dns.com: 185.132.34.195, 217.160.82.195
A
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52d6:100)
29
ns-biz.ui-dns.com: 2001:8d8:fe:53:0:d9a0:52c3:100, 2607:f1c0:fe:53:185:132:34:195
AAAA
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52d6:100)
30
ns-biz.ui-dns.de: 185.132.32.195, 217.160.80.195
A
ns-de.ui-dns.biz (2607:f1c0:fe:53:185:132:33:193)
31
ns-biz.ui-dns.de: 2001:8d8:fe:53:0:d9a0:50c3:100, 2607:f1c0:fe:53:185:132:32:195
AAAA
ns-de.ui-dns.biz (2607:f1c0:fe:53:185:132:33:193)
32
ns-biz.ui-dns.org: 185.132.35.195, 217.160.83.195
A
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:52c2:100)
33
ns-biz.ui-dns.org: 2001:8d8:fe:53:0:d9a0:53c3:100, 2607:f1c0:fe:53:185:132:35:195
AAAA
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:52c2:100)
34
ns-com.ui-dns.biz: 185.132.33.194, 217.160.81.194
A
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
35
ns-com.ui-dns.biz: 2001:8d8:fe:53:0:d9a0:51c2:100, 2607:f1c0:fe:53:185:132:33:194
AAAA
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
36
ns-com.ui-dns.de: 185.132.32.194, 217.160.80.194
A
ns-de.ui-dns.biz (2607:f1c0:fe:53:185:132:33:193)
37
ns-com.ui-dns.de: 2001:8d8:fe:53:0:d9a0:50c2:100, 2607:f1c0:fe:53:185:132:32:194
AAAA
ns-de.ui-dns.biz (2607:f1c0:fe:53:185:132:33:193)
38
ns-com.ui-dns.org: 185.132.35.194, 217.160.83.194
A
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:52c2:100)
39
ns-com.ui-dns.org: 2001:8d8:fe:53:0:d9a0:53c2:100, 2607:f1c0:fe:53:185:132:35:194
AAAA
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:52c2:100)
40
ns-org.ui-dns.biz: 185.132.33.196, 217.160.81.196
A
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
41
ns-org.ui-dns.biz: 2001:8d8:fe:53:0:d9a0:51c4:100, 2607:f1c0:fe:53:185:132:33:196
AAAA
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
42
ns-org.ui-dns.com: 185.132.34.196, 217.160.82.196
A
ns-com.ui-dns.biz (2607:f1c0:fe:53:185:132:33:194)
43
ns-org.ui-dns.com: 2001:8d8:fe:53:0:d9a0:52c4:100, 2607:f1c0:fe:53:185:132:34:196
AAAA
ns-com.ui-dns.biz (2607:f1c0:fe:53:185:132:33:194)
44
ns-org.ui-dns.de: 185.132.32.196, 217.160.80.196
A
ns-de.ui-dns.biz (2607:f1c0:fe:53:185:132:33:193)
45
ns-org.ui-dns.de: 2001:8d8:fe:53:0:d9a0:50c4:100, 2607:f1c0:fe:53:185:132:32:196
AAAA
ns-de.ui-dns.biz (2607:f1c0:fe:53:185:132:33:193)
46
docks20.rzone.de: 217.160.80.147
A
ns-anyslv.ui-dns.de (2607:f1c0:fe:53:185:132:32:247)
47
docks20.rzone.de: 2001:8d8:fe:53:5747:2a74:d:20
AAAA
ns-anyslv.ui-dns.de (2607:f1c0:fe:53:185:132:32:247)
48
shades09.rzone.de: 185.132.34.136
A
ns-anyslv.ui-dns.de (2607:f1c0:fe:53:185:132:32:247)
49
shades09.rzone.de: 2607:f1c0:fe:53:185:132:34:136
AAAA
ns-anyslv.ui-dns.de (2607:f1c0:fe:53:185:132:32:247)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
nextcloud.amyliv.de
0

no CAA entry found
1
0
amyliv.de
0

no CAA entry found
1
0
de
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
amyliv.de

ok
1
0
nextcloud.amyliv.de

ok
1
0
_acme-challenge.nextcloud.amyliv.de

Name Error - The domain name does not exist
1
0
_acme-challenge.nextcloud.amyliv.de.amyliv.de

perhaps wrong
1
0
_acme-challenge.nextcloud.amyliv.de.nextcloud.amyliv.de

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

nextcloud.amyliv.de
5
smtpin.rzone.de
01ok

A


81.169.145.97
01ok

AAAA


2a01:238:20a:202:50f0::1097
01ok

CNAME


00ok

 

 

17. Cipher Suites

Summary
DomainIPPortnum CipherstimeStd.ProtocolForward Secrecy
nextcloud.amyliv.de
91.41.7.140
443
2 Ciphers94.13 sec
0 without, 2 FS
100.00 %
Complete

1
2 Ciphers
2.00 Ciphers/Check
94.13 sec94.13 sec/Check
0 without, 2 FS
100.00 %

Details
DomainIPPortCipher (OpenSsl / IANA)
nextcloud.amyliv.de
91.41.7.140
443
ECDHE-ECDSA-CHACHA20-POLY1305
(Recommended)
TLSv1.2
0xCC,0xA9
FS
2 Ciphers, 94.13 sec
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256

ECDH
ECDSA
CHACHA20/POLY1305(256)
AEAD




ECDHE-ECDSA-AES128-GCM-SHA256
(Recommended)
TLSv1.2
0xC0,0x2B
FS

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

ECDH
ECDSA
AESGCM(128)
AEAD

 

18. Portchecks

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

 

 

Permalink: https://check-your-website.server-daten.de/?i=0f6b3953-5208-43f3-a4e4-b36493abd364

 

Last Result: https://check-your-website.server-daten.de/?q=nextcloud.amyliv.de - 2025-04-25 18:09:50

 

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

 

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