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

...

skip EDNS-Check

skip Content-Check

check links

Timeout

Checked:
09.05.2025 14:02:57

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
nextcloud.johanneslechner.com	CNAME	jochenrindt.ddns.net	yes	1	0
	A	89.105.180.240 Schwaz/Tyrol/Austria (AT) - Stadtwerke Schwaz GmbH No Hostname found	yes
www.nextcloud.johanneslechner.com	CNAME	jochenrindt.ddns.net	yes	1	0
	A	89.105.180.240 Schwaz/Tyrol/Austria (AT) - Stadtwerke Schwaz GmbH No Hostname found	yes
*.johanneslechner.com	A		yes
	AAAA		yes
	CNAME	jochenrindt.ddns.net	yes
*.nextcloud.johanneslechner.com	A		yes
	AAAA		yes
	CNAME	jochenrindt.ddns.net	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: 22.05.2025, 00:00:00 +, Signature-Inception: 01.05.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: com
com	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.05.2025, 05:00:00 +, Signature-Inception: 09.05.2025, 04: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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 19718, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 13, KeyTag 40097, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 17.05.2025, 14:02:35 +, Signature-Inception: 02.05.2025, 13:57:35 +, KeyTag 19718, Signer-Name: com


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 19718 used to validate the DNSKEY RRSet


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

Zone: johanneslechner.com
johanneslechner.com	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 "ikt6okcp4hjkg768711cmimitvqk008s" between the hashed NSEC3-owner "ikt6au556sg0ivhtt9vudqem9ab8jb1v" and the hashed NextOwner "ikt7631fm1s0vmkk3ik6impgm6i1pqba". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner ikt6au556sg0ivhtt9vudqem9ab8jb1v.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 16.05.2025, 01:52:55 +, Signature-Inception: 09.05.2025, 00:42:55 +, KeyTag 40097, Signer-Name: com


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q3udg8cekkae7rukpgct1dvssh8ll". So that domain name is the Closest Encloser of "johanneslechner.com". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 15.05.2025, 00:25:55 +, Signature-Inception: 07.05.2025, 23:15:55 +, KeyTag 40097, Signer-Name: com


	0 DNSKEY RR found




Zone: nextcloud.johanneslechner.com
nextcloud.johanneslechner.com	0 DS RR in the parent zone found

Zone: www.nextcloud.johanneslechner.com
www.nextcloud.johanneslechner.com	0 DS RR in the parent zone found

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: 22.05.2025, 00:00:00 +, Signature-Inception: 01.05.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: net
net	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.05.2025, 05:00:00 +, Signature-Inception: 09.05.2025, 04: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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 37331, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 13, KeyTag 45412, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner net., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 17.05.2025, 14:10:35 +, Signature-Inception: 02.05.2025, 14:05:35 +, KeyTag 37331, Signer-Name: net


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 37331 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest "LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: ddns.net
ddns.net	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 "e51o1pdujacqu01c7sqi76kt359m7agm" between the hashed NSEC3-owner "e51mnimmcme4gt51692ds6mmtqvsq7u5" and the hashed NextOwner "e51peeeeaj4k8hqim65ha9l4sei317p8". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner e51mnimmcme4gt51692ds6mmtqvsq7u5.net., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 13.05.2025, 02:57:28 +, Signature-Inception: 06.05.2025, 01:47:28 +, KeyTag 45412, Signer-Name: net


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "a1rt98bs5qgc9nfi51s9hci47uljg6jh" as Owner. That's the Hash of "net" with the NextHashedOwnerName "a1rtlnpgulogn7b9a62shje1u3ttp8dr". So that domain name is the Closest Encloser of "ddns.net". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 15.05.2025, 03:00:47 +, Signature-Inception: 08.05.2025, 01:50:47 +, KeyTag 45412, Signer-Name: net


	0 DNSKEY RR found




Zone: jochenrindt.ddns.net
jochenrindt.ddns.net	0 DS RR in the parent zone found


	0 DNSKEY RR found

3. Name Servers

Domain	Nameserver	NS-IP
johanneslechner.com	• ns1.mydomain.com / 67m112	172.64.52.99 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	• ns2.mydomain.com / 67m89	172.64.53.76 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
com	• a.gtld-servers.net / nnn1-par6		•
	• b.gtld-servers.net / nnn1-eltxl1		•
	• c.gtld-servers.net / nnn1-par6		•
	• d.gtld-servers.net / nnn1-par6		•
	• e.gtld-servers.net / nnn1-par6		•
	• f.gtld-servers.net / nnn1-defra-4		•
	• g.gtld-servers.net / nnn1-defra-4		•
	• h.gtld-servers.net / nnn1-defra-4		•
	• i.gtld-servers.net / nnn1-defra-4		•
	• j.gtld-servers.net / nnn1-frmrs-2		•
	• k.gtld-servers.net / nnn1-frmrs-2		•
	• l.gtld-servers.net / nnn1-frmrs-2		•
	• m.gtld-servers.net / nnn1-frmrs-2		•

jochenrindt.ddns.net	• nf1.no-ip.com / frana1	194.62.182.53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2a07:dc00:1820::53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
ddns.net	• nf1.no-ip.com / frana1	194.62.182.53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2a07:dc00:1820::53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	• nf2.no-ip.com / frana2	45.54.64.53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2607:f740:e626::53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
	• nf3.no-ip.com / frana1	204.16.253.53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2620:0:2e61::53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
	• nf4.no-ip.com / frana2	194.62.183.53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2a07:dc00:1830::53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	• nf5.no-ip.com / frana1	204.16.253.53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2620:0:2e61::53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
net	• a.gtld-servers.net / nnn1-par6		•
	• b.gtld-servers.net / nnn1-eltxl1		•
	• c.gtld-servers.net / nnn1-par6		•
	• d.gtld-servers.net / nnn1-par6		•
	• e.gtld-servers.net / nnn1-par6		•
	• f.gtld-servers.net / nnn1-defra-4		•
	• g.gtld-servers.net / nnn1-defra-4		•
	• h.gtld-servers.net / nnn1-defra-4		•
	• i.gtld-servers.net / nnn1-defra-4		•
	• j.gtld-servers.net / nnn1-frmrs-2		•
	• k.gtld-servers.net / nnn1-frmrs-2		•
	• l.gtld-servers.net / nnn1-frmrs-2		•
	• m.gtld-servers.net / nnn1-frmrs-2		•

4. SOA-Entries

Domain:	com
Zone-Name:	com
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1746792160
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	900
num Entries:	11

Domain:	com
Zone-Name:	com
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1746792175
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	900
num Entries:	2

Domain:	johanneslechner.com
Zone-Name:	johanneslechner.com
Primary:	ns1.mydomain.com
Mail:	namehost@WORLDNIC.com
Serial:	124112505
Refresh:	10800
Retry:	3600
Expire:	604800
TTL:	3600
num Entries:	2


Domain:	net
Zone-Name:	net
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1746792175
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	900
num Entries:	10

Domain:	net
Zone-Name:	net
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1746792190
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	900
num Entries:	3

Domain:	ddns.net
Zone-Name:	ddns.net
Primary:	nf1.no-ip.com
Mail:	hostmaster.no-ip.com
Serial:	2631935610
Refresh:	10800
Retry:	1800
Expire:	604800
TTL:	1800
num Entries:	2

Domain:	ddns.net
Zone-Name:	ddns.net
Primary:	nf1.no-ip.com
Mail:	hostmaster.no-ip.com
Serial:	2631935610
Refresh:	10800
Retry:	1800
Expire:	604800
TTL:	1800
num Entries:	2

Domain:	ddns.net
Zone-Name:	ddns.net
Primary:	nf1.no-ip.com
Mail:	hostmaster.no-ip.com
Serial:	2631935622
Refresh:	10800
Retry:	1800
Expire:	604800
TTL:	1800
num Entries:	6

Domain:	ddns.net
Zone-Name:	ddns.net
Primary:	nf1.no-ip.com
Mail:	hostmaster.no-ip.com
Serial:	2631935622
Refresh:	10800
Retry:	1800
Expire:	604800
TTL:	1800
num Entries:	6

Domain:	ddns.net
Zone-Name:	ddns.net
Primary:	nf1.no-ip.com
Mail:	hostmaster.no-ip.com
Serial:	2631935631
Refresh:	10800
Retry:	1800
Expire:	604800
TTL:	1800
num Entries:	2

Domain:	ddns.net
Zone-Name:	ddns.net
Primary:	nf1.no-ip.com
Mail:	hostmaster.no-ip.com
Serial:	2631935631
Refresh:	10800
Retry:	1800
Expire:	604800
TTL:	1800
num Entries:	2

Domain:	jochenrindt.ddns.net
Zone-Name:	ddns.net
Primary:	nf1.no-ip.com
Mail:	hostmaster.no-ip.com
Serial:	2631935631
Refresh:	10800
Retry:	1800
Expire:	604800
TTL:	1800
num Entries:	2

5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

Domainname	Http-Status	Sec.	G
• http://nextcloud.johanneslechner.com/ 89.105.180.240	-14	10.024	T
Timeout - The operation has timed out.

• http://www.nextcloud.johanneslechner.com/ 89.105.180.240	-14	10.030	T
Timeout - The operation has timed out.

• https://nextcloud.johanneslechner.com/ 89.105.180.240	-14	10.026	T
Timeout - The operation has timed out.

• https://www.nextcloud.johanneslechner.com/ 89.105.180.240	-14	10.020	T
Timeout - The operation has timed out.

• http://nextcloud.johanneslechner.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 89.105.180.240	-14	10.024	T
Timeout - The operation has timed out.
Visible Content:

• http://www.nextcloud.johanneslechner.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 89.105.180.240	-14	10.026	T
Timeout - The operation has timed out.
Visible Content:

• https://89.105.180.240/ 89.105.180.240	-14	10.013	T
Timeout - The operation has timed out.

7. Comments

	1. General Results, most used to calculate the result
A	name "nextcloud.johanneslechner.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 105479 (complete: 270180)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: nextcloud.johanneslechner.com has only one ip address.
	Warning: Only one ip address found: www.nextcloud.johanneslechner.com 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.johanneslechner.com has no ipv6 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: www.nextcloud.johanneslechner.com has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
	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.johanneslechner.com, 1 ip addresses.
	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 www.nextcloud.johanneslechner.com, 1 ip addresses.
B	No _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.johanneslechner.com
	2. Header-Checks
U			No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
A	Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.mydomain.com (172.64.52.99), ns2.mydomain.com (172.64.53.76)
A	Good (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: ns1.mydomain.com, ns2.mydomain.com, 2 Name Servers included in Delegation: ns1.mydomain.com, ns2.mydomain.com, 2 Name Servers included in 1 Zone definitions: ns1.mydomain.com, ns2.mydomain.com, 1 Name Servers listed in SOA.Primary: ns1.mydomain.com.
A	Good: Only one SOA.Primary Name Server found.: ns1.mydomain.com.
A	Good: SOA.Primary Name Server included in the delegation set.: ns1.mydomain.com.
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 172., 1 different subnets (first two Bytes): 172.64., 2 different subnets (first three Bytes): 172.64.52., 172.64.53.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Good: Nameserver supports TCP connections: 2 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 2 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns1.mydomain.com / 172.64.52.99: OP100: ok. FLAGS: ok. V1: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (67m112). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns2.mydomain.com / 172.64.53.76: OP100: ok. FLAGS: ok. V1: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (67m89). COOKIE: ok. CLIENTSUBNET: ok.
A	Good: 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
	http://nextcloud.johanneslechner.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 89.105.180.240	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.nextcloud.johanneslechner.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 89.105.180.240	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
A	Info: No img element found, no alt attribute checked
A	Good: 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
A	Duration: 195794 milliseconds, 195.794 seconds

8. Connections

No connection informations found. Perhaps only http - connections.

9. Certificates

No certificate informations found. Perhaps only http - connections.

10. Last Certificates - Certificate Transparency Log Check

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

No CertSpotter - CT-Log entries found

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

Issuer				last 7 days	active	num Certs
CN=E5, O=Let's Encrypt, C=US				0	1	2

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
17404317422 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-02-28 10:55:43	2025-05-29 09:55:42	jf.johanneslechner.com, nextcloud.johanneslechner.com 2 entries
15938558093 precert	CN=E5, O=Let's Encrypt, C=US	2024-12-30 08:25:11	2025-03-30 07:25:10	jf.johanneslechner.com, nextcloud.johanneslechner.com 2 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: ns1.mydomain.com, ns2.mydomain.com

QNr.	Domain	Type	NS used
1	com	NS	a.root-servers.net (2001:503:ba3e::2:30)
	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
2	ns1.mydomain.com: 172.64.52.99	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns2.mydomain.com 172.64.53.76
	Answer: ns3.mydomain.com 172.64.52.99
	Answer: ns4.mydomain.com 172.64.53.76

14. CAA - Entries

Domainname	flag	Value	∑ Queries
www.nextcloud.johanneslechner.com			1
nextcloud.johanneslechner.com			1
jochenrindt.ddns.net	0	no CAA entry found	1
johanneslechner.com	0	no CAA entry found	1
ddns.net	0	no CAA entry found	1
com	0	no CAA entry found	1
net	0	no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
johanneslechner.com	protonmail-verification=41a10ba766ec7aafc8dcbedd0bc4abe9e271ba48	ok	1
johanneslechner.com	v=spf1 include:_spf.protonmail.ch ~all	ok	1
nextcloud.johanneslechner.com			1
www.nextcloud.johanneslechner.com			1
_acme-challenge.jochenrindt.ddns.net		Name Error - The domain name does not exist	1
_acme-challenge.nextcloud.johanneslechner.com			1
_acme-challenge.www.nextcloud.johanneslechner.com			1
_acme-challenge.jochenrindt.ddns.net.jochenrindt.ddns.net		Name Error - The domain name does not exist	1
_acme-challenge.nextcloud.johanneslechner.com.johanneslechner.com			1
_acme-challenge.nextcloud.johanneslechner.com.nextcloud.johanneslechner.com			1
_acme-challenge.www.nextcloud.johanneslechner.com.nextcloud.johanneslechner.com			1
_acme-challenge.www.nextcloud.johanneslechner.com.www.nextcloud.johanneslechner.com			1

16. DomainService - Entries

Type		Domain	Pref	Value	DNS-error	num Answers	Status	Description
SPF	TXT	nextcloud.johanneslechner.com					32768	TXT expected, but CNAME found. CNAME not allowed, only TXT queries are allowed. See RFC 7208, 4.4.

17. Cipher Suites

No results

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=0f34db3e-8d50-4c93-bdda-7bd3a94fb6d8

Last Result: https://check-your-website.server-daten.de/?q=nextcloud.johanneslechner.com - 2025-05-09 14:02:57

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.johanneslechner.com" target="_blank">Check this Site: nextcloud.johanneslechner.com</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.johanneslechner.com