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

...

skip EDNS-Check

skip Content-Check

check links

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
18.09.2023 15:36:45

Older results

B - 01.02.2021 12:33:28

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
finecloud.srvdns.de	A	62.245.228.82 Hallbergmoos/Bavaria/Germany (DE) - MNET Hostname: host-62-245-228-82.customer.m-online.net	yes	1	0
	AAAA		yes
www.finecloud.srvdns.de		Name Error	yes	1	0
*.srvdns.de	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.finecloud.srvdns.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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 11019, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 30.09.2023, 00:00:00 +, Signature-Inception: 09.09.2023, 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: 01.10.2023, 05:00:00 +, Signature-Inception: 18.09.2023, 04:00:00 +, KeyTag 11019, Signer-Name: (root)


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 44886, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 29.09.2023, 23:42:55 +, Signature-Inception: 15.09.2023, 22:12:55 +, 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: srvdns.de
srvdns.de	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 13689, DigestType 2 and Digest cph0YPEIxhZPFAJV28bgF/24RFAmfovybje6BhQe7Cg=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner srvdns.de., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 01.10.2023, 06:56:29 +, Signature-Inception: 17.09.2023, 05:26:29 +, KeyTag 44886, Signer-Name: de


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


	1 DNSKEY RR found


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner srvdns.de., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 28.09.2023, 00:00:00 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 13689, Signer-Name: srvdns.de


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


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

Zone: finecloud.srvdns.de
finecloud.srvdns.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 "rs61rnbl09hsto2ahn2d6qo3t971rqus" between the hashed NSEC3-owner "rs61rnbl09hsto2ahn2d6qo3t971rqus" and the hashed NextOwner "rs61rnbl09hsto2ahn2d6qo3t971rqut". So the parent zone confirmes the not-existence of a DS RR. Bitmap: A, RRSIG Validated: RRSIG-Owner rs61rnbl09hsto2ahn2d6qo3t971rqus.srvdns.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 28.09.2023, 00:00:00 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 13689, Signer-Name: srvdns.de


	0 DNSKEY RR found





	RRSIG Type 1 validates the A - Result: 62.245.228.82 Validated: RRSIG-Owner finecloud.srvdns.de., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 28.09.2023, 00:00:00 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 13689, Signer-Name: srvdns.de


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "rs61rnbl09hsto2ahn2d6qo3t971rqus" equal the hashed NSEC3-owner "rs61rnbl09hsto2ahn2d6qo3t971rqus" and the hashed NextOwner "rs61rnbl09hsto2ahn2d6qo3t971rqut". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner rs61rnbl09hsto2ahn2d6qo3t971rqus.srvdns.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 28.09.2023, 00:00:00 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 13689, Signer-Name: srvdns.de


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed query name "rs61rnbl09hsto2ahn2d6qo3t971rqus" equal the hashed NSEC3-owner "rs61rnbl09hsto2ahn2d6qo3t971rqus" and the hashed NextOwner "rs61rnbl09hsto2ahn2d6qo3t971rqut". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner rs61rnbl09hsto2ahn2d6qo3t971rqus.srvdns.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 28.09.2023, 00:00:00 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 13689, Signer-Name: srvdns.de


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "rs61rnbl09hsto2ahn2d6qo3t971rqus" equal the hashed NSEC3-owner "rs61rnbl09hsto2ahn2d6qo3t971rqus" and the hashed NextOwner "rs61rnbl09hsto2ahn2d6qo3t971rqut". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner rs61rnbl09hsto2ahn2d6qo3t971rqus.srvdns.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 28.09.2023, 00:00:00 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 13689, Signer-Name: srvdns.de


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.finecloud.srvdns.de) sends a valid NSEC3 RR as result with the hashed owner name "rs61rnbl09hsto2ahn2d6qo3t971rqus" (unhashed: finecloud.srvdns.de). So that's the Closest Encloser of the query name. Bitmap: A, RRSIG Validated: RRSIG-Owner rs61rnbl09hsto2ahn2d6qo3t971rqus.srvdns.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 28.09.2023, 00:00:00 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 13689, Signer-Name: srvdns.de


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "97cmn7l174rnu7ootkmqrfirf60oqmmh" (unhashed: _tcp.finecloud.srvdns.de) with the owner "97cmn7l174rnu7ootkmqrfirf60oqmmg" and the NextOwner "97cmn7l174rnu7ootkmqrfirf60oqmmi". So that NSEC3 confirms the not-existence of the Next Closer Name. Bitmap: No Bitmap? Validated: RRSIG-Owner 97cmn7l174rnu7ootkmqrfirf60oqmmg.srvdns.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 28.09.2023, 00:00:00 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 13689, Signer-Name: srvdns.de


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "26gam9eemeisea40vbe41lo91a4t363m" (unhashed: *.finecloud.srvdns.de) with the owner "26gam9eemeisea40vbe41lo91a4t363l" and the NextOwner "26gam9eemeisea40vbe41lo91a4t363n". So that NSEC3 confirms the not-existence of the Wildcard expansion. Bitmap: No Bitmap? Validated: RRSIG-Owner 26gam9eemeisea40vbe41lo91a4t363l.srvdns.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 28.09.2023, 00:00:00 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 13689, Signer-Name: srvdns.de


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed query name "rs61rnbl09hsto2ahn2d6qo3t971rqus" equal the hashed NSEC3-owner "rs61rnbl09hsto2ahn2d6qo3t971rqus" and the hashed NextOwner "rs61rnbl09hsto2ahn2d6qo3t971rqut". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner rs61rnbl09hsto2ahn2d6qo3t971rqus.srvdns.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 28.09.2023, 00:00:00 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 13689, Signer-Name: srvdns.de


	Status: Good. NoData-Proof required and found.

Zone: www.finecloud.srvdns.de
www.finecloud.srvdns.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 "v8tjtmhol58a3eaqd1s1lgeimnok7ppb" between the hashed NSEC3-owner "v8tjtmhol58a3eaqd1s1lgeimnok7ppa" and the hashed NextOwner "v8tjtmhol58a3eaqd1s1lgeimnok7ppc". So the parent zone confirmes the not-existence of a DS RR. Bitmap: No Bitmap? Validated: RRSIG-Owner v8tjtmhol58a3eaqd1s1lgeimnok7ppa.srvdns.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 28.09.2023, 00:00:00 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 13689, Signer-Name: srvdns.de


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "rs61rnbl09hsto2ahn2d6qo3t971rqus" as Owner. That's the Hash of "finecloud.srvdns.de" with the NextHashedOwnerName "rs61rnbl09hsto2ahn2d6qo3t971rqut". So that domain name is the Closest Encloser of "www.finecloud.srvdns.de". Opt-Out: True. Bitmap: A, RRSIG Validated: RRSIG-Owner rs61rnbl09hsto2ahn2d6qo3t971rqus.srvdns.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 28.09.2023, 00:00:00 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 13689, Signer-Name: srvdns.de


	The ClosestEncloser says, that "*.finecloud.srvdns.de" with the Hash "26gam9eemeisea40vbe41lo91a4t363m" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "26gam9eemeisea40vbe41lo91a4t363l" and the Next Owner "26gam9eemeisea40vbe41lo91a4t363n", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: No Bitmap? Validated: RRSIG-Owner 26gam9eemeisea40vbe41lo91a4t363l.srvdns.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 28.09.2023, 00:00:00 +, Signature-Inception: 07.09.2023, 00:00:00 +, KeyTag 13689, Signer-Name: srvdns.de

3. Name Servers

Domain	Nameserver	NS-IP
www.finecloud.srvdns.de	• ns1.dnshome.de
finecloud.srvdns.de	• ns1.dnshome.de / cdns-01-eth.dnshome.org	45.86.125.58 Frankfurt am Main/Hesse/Germany (DE) - ETH-VOX	•
	•	2a0c:8901::53 Frankfurt am Main/Hesse/Germany (DE) - Lennart Seitz trading as "ETH-Services"	•
srvdns.de	• ns1.dnshome.de / cdns-01-eth.dnshome.org	45.86.125.58 Frankfurt am Main/Hesse/Germany (DE) - ETH-VOX	•
	•	2a0c:8901::53 Frankfurt am Main/Hesse/Germany (DE) - Lennart Seitz trading as "ETH-Services"	•
	• ns2.dnshome.de / cdns-01-eth.dnshome.org	45.86.125.59 Frankfurt am Main/Hesse/Germany (DE) - ETH-VOX	•
	•	2a0c:8902::53 Frankfurt am Main/Hesse/Germany (DE) - Lennart Seitz trading as "ETH-Services"	•
de	• a.nic.de / ns-2.de.de8.bind		•
	• f.nic.de / ns-1.de.de1		•
	• l.de.net / ns-1.de.fr1		•
	• n.de.net / s3.cph		•
	• s.de.net / ns-3.de.de9		•
	• 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:	1695044124
Refresh:	7200
Retry:	7200
Expire:	3600000
TTL:	7200
num Entries:	6

Domain:	srvdns.de
Zone-Name:	srvdns.de
Primary:	ns1.dnshome.de
Mail:	hostmaster.dnshome.de
Serial:	1695044216
Refresh:	14400
Retry:	3600
Expire:	604800
TTL:	3600
num Entries:	4

Domain:	finecloud.srvdns.de
Zone-Name:	srvdns.de
Primary:	ns1.dnshome.de
Mail:	hostmaster.dnshome.de
Serial:	1695044221
Refresh:	14400
Retry:	3600
Expire:	604800
TTL:	3600
num Entries:	2

Domain:	www.finecloud.srvdns.de
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

Domainname	Http-Status	Sec.	G
• http://finecloud.srvdns.de/ 62.245.228.82	-14	10.047	T
Timeout - The operation has timed out

• https://finecloud.srvdns.de/ 62.245.228.82	-14	10.027	T
Timeout - The operation has timed out

• http://finecloud.srvdns.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 62.245.228.82	-14	10.030	T
Timeout - The operation has timed out
Visible Content:

• https://62.245.228.82/ 62.245.228.82	-14	10.030	T
Timeout - The operation has timed out

7. Comments

	1. General Results, most used to calculate the result
A	name "finecloud.srvdns.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: 9157 (complete: 231048)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: finecloud.srvdns.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: finecloud.srvdns.de has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
	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 finecloud.srvdns.de, 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.finecloud.srvdns.de
	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.dnshome.de (2a0c:8901::53, 45.86.125.58), ns2.dnshome.de (2a0c:8902::53, 45.86.125.59)
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.dnshome.de, ns2.dnshome.de, 2 Name Servers included in Delegation: ns1.dnshome.de, ns2.dnshome.de, 2 Name Servers included in 1 Zone definitions: ns1.dnshome.de, ns2.dnshome.de, 1 Name Servers listed in SOA.Primary: ns1.dnshome.de.
A	Good: Only one SOA.Primary Name Server found.: ns1.dnshome.de.
A	Good: SOA.Primary Name Server included in the delegation set.: ns1.dnshome.de.
A	Good: 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: ns1.dnshome.de, ns2.dnshome.de
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	Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
A	Good: 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: dnshome.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:
	Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: DE
A	Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 45., 1 different subnets (first two Bytes): 45.86., 1 different subnets (first three Bytes): 45.86.125.
X	Fatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.:
A	Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2a0c:, 2 different subnets (first two blocks): 2a0c:8901:, 2a0c:8902:, 2 different subnets (first three blocks): 2a0c:8901:0000:, 2a0c:8902:0000:, 2 different subnets (first four blocks): 2a0c:8901:0000:0000:, 2a0c:8902:0000:0000:
A	Good: Name Server IPv6 addresses from different subnets 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
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns1.dnshome.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.
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://finecloud.srvdns.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 62.245.228.82	-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: 91900 milliseconds, 91.900 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=R3, O=Let's Encrypt, C=US				0 /0 new	0	2

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
9375921678 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-05-11 18:26:29	2023-08-09 18:26:28	finecloud.finepower.com, finecloud.finepower.de, finecloud.srvdns.de 3 entries
8906194954 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-03-12 14:46:58	2023-06-10 13:46:57	finecloud.finepower.com, finecloud.finepower.de, finecloud.srvdns.de 3 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: ns1.dnshome.de, ns2.dnshome.de

QNr.	Domain	Type	NS used
1	de	NS	h.root-servers.net (2001:500:1::53)
	Answer: a.nic.de, f.nic.de, l.de.net, n.de.net, s.de.net, z.nic.de
2	ns1.dnshome.de: 2a0c:8901::53, 45.86.125.58	NS	a.nic.de (2001:678:2::53)
	Answer: ns2.dnshome.de 2a0c:8902::53, 45.86.125.59

13. CAA - Entries

Domainname	Value	∑ Queries
finecloud.srvdns.de	no CAA entry found	1
srvdns.de	no CAA entry found	1
de	no CAA entry found	1

14. TXT - Entries

Domainname	Status	∑ Queries
srvdns.de	ok	1
finecloud.srvdns.de	ok	1
_acme-challenge.finecloud.srvdns.de	Name Error - The domain name does not exist	1
_acme-challenge.finecloud.srvdns.de.srvdns.de	Name Error - The domain name does not exist	1
_acme-challenge.finecloud.srvdns.de.finecloud.srvdns.de	Name Error - The domain name does not exist	1

15. DomainService - Entries

No DomainServiceEntries entries found

16. Cipher Suites

No results

17. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=6e1f71bc-a755-4c21-b765-e878f300f344

Last Result: https://check-your-website.server-daten.de/?q=finecloud.srvdns.de - 2023-09-18 15:36:45

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

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