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

...

skip EDNS-Check

skip Content-Check

check links

Timeout

Checked:
06.07.2025 11:24:08

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
cloudwasmer.de	A	46.128.9.107 Munich/Bavaria/Germany (DE) - 16 originated by AS35244 Hostname: 46.128.9.107.dyn.pyur.net	yes	2	0
	AAAA		yes
www.cloudwasmer.de	CNAME	cloudwasmer.de	yes	1	0
	A	46.128.9.107 Munich/Bavaria/Germany (DE) - 16 originated by AS35244 Hostname: 46.128.9.107.dyn.pyur.net	yes
*.cloudwasmer.de	A		yes
	AAAA		yes
	CNAME		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


	4 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 46441, Flags 256


	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.07.2025, 00:00:00 +, Signature-Inception: 01.07.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: 19.07.2025, 05:00:00 +, Signature-Inception: 06.07.2025, 04:00:00 +, KeyTag 46441, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 11226, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 18.07.2025, 23:01:58 +, Signature-Inception: 04.07.2025, 21:31:58 +, 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: cloudwasmer.de
cloudwasmer.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 "517q0bu48gni9m4ssv99lat6gc2kcd48" between the hashed NSEC3-owner "517oppoqqgpo9hjo3m4h2jb9l2iubg09" and the hashed NextOwner "517q3aasbo5h312mp7a76tnpqluro1lr". So the parent zone confirmes the not-existence of a DS RR. Bitmap: A, RRSIG Validated: RRSIG-Owner 517oppoqqgpo9hjo3m4h2jb9l2iubg09.de., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 20.07.2025, 06:25:53 +, Signature-Inception: 06.07.2025, 04:55:53 +, KeyTag 11226, 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 "cloudwasmer.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: 20.07.2025, 05:14:45 +, Signature-Inception: 06.07.2025, 03:44:45 +, KeyTag 11226, Signer-Name: de


	0 DNSKEY RR found




Zone: www.cloudwasmer.de
www.cloudwasmer.de	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
cloudwasmer.de	• docks02.rzone.de / 8560_de-fra-fr7_strato-customer-docks	217.160.80.129 Frankfurt am Main/Hesse/Germany (DE) - IONOS SE	•
	•	2001:8d8:fe:53:5747:2a74:d:2 Frankfurt am Main/Hesse/Germany (DE) - 1&1 IONOS SE	•
	• shades01.rzone.de / 15418_de-ber-rs_strato-customer-shades	185.132.34.128 Frankfurt am Main/Hesse/Germany (DE) - DNSAS (eBGP DNS)	•
	•	2607:f1c0:fe:53:185:132:34:128 Kansas City/Missouri/United States (US) - Fasthosts Internet Limited	•
de	• a.nic.de / ns-1.de.de8.knot		•
	• f.nic.de / ns-2.de.de1.knot		•
	• l.de.net / ns-1.de.uk1.knot		•
	• n.de.net / s3.dex		•
	• s.de.net / ns-2.de.de9.knot		•
	• z.nic.de / ns-1.de.de2.bind		•

4. SOA-Entries

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

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

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://cloudwasmer.de/ 46.128.9.107	-14	10.033	T
Timeout - The operation has timed out.

• http://www.cloudwasmer.de/ 46.128.9.107	-14	10.016	T
Timeout - The operation has timed out.

• https://cloudwasmer.de/ 46.128.9.107	-14	10.020	T
Timeout - The operation has timed out.

• https://www.cloudwasmer.de/ 46.128.9.107	-14	10.027	T
Timeout - The operation has timed out.

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

• http://www.cloudwasmer.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.128.9.107	-14	10.034	T
Timeout - The operation has timed out.
Visible Content:

• https://46.128.9.107/ 46.128.9.107	-14	10.020	T
Timeout - The operation has timed out.

7. Comments

	1. General Results, most used to calculate the result
A	name "cloudwasmer.de" is domain, 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: 10906 (complete: 271405)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: cloudwasmer.de has only one ip address.
	Warning: Only one ip address found: www.cloudwasmer.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: cloudwasmer.de 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.cloudwasmer.de 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 cloudwasmer.de, 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.cloudwasmer.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.cloudwasmer.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:: 49 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 49 Queries complete, 49 with IPv6, 0 with IPv4.
A	Good: 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.
A	Info:: 2 different Name Servers found: docks02.rzone.de, shades01.rzone.de, 2 Name Servers included in Delegation: docks02.rzone.de, shades01.rzone.de, 2 Name Servers included in 1 Zone definitions: docks02.rzone.de, shades01.rzone.de, 1 Name Servers listed in SOA.Primary: docks02.rzone.de.
A	Good: Only one SOA.Primary Name Server found.: docks02.rzone.de.
A	Good: SOA.Primary Name Server included in the delegation set.: docks02.rzone.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: docks02.rzone.de, shades01.rzone.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: 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
A	Good: Name servers with different Country locations found: 2 Name Servers, 2 Countries: DE, US
A	Info: 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.
A	Excellent: Every Name Server IPv4-address starts with an unique Byte.
A	Info: 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:
A	Excellent: Every Name Server IPv6-address starts with an unique Hex-block
A	Good: Nameserver supports TCP connections: 4 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 4 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
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://cloudwasmer.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.128.9.107	-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.cloudwasmer.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.128.9.107	-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: 117984 milliseconds, 117.984 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

No CRT - CT-Log entries found

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: docks02.rzone.de, shades01.rzone.de

QNr.	Domain	Type	NS used
1	de	NS	j.root-servers.net (2001:503:c27::2:30)
	Answer: a.nic.de, f.nic.de, l.de.net, n.de.net, s.de.net, z.nic.de
2	docks02.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	shades01.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	l.root-servers.net (2001:500:9f::42)
	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 (2001:8d8:fe:53:0:d9a0:51c2:100)
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 (2001:8d8:fe:53:0:d9a0:51c2:100)
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	docks02.rzone.de: 217.160.80.129	A	ns-anyslv.ui-dns.de (2001:8d8:fe:53:616e:7973:6c76:310a)
47	docks02.rzone.de: 2001:8d8:fe:53:5747:2a74:d:2	AAAA	ns-anyslv.ui-dns.de (2001:8d8:fe:53:616e:7973:6c76:310a)
48	shades01.rzone.de: 185.132.34.128	A	ns-anyslv.ui-dns.de (2001:8d8:fe:53:616e:7973:6c76:310a)
49	shades01.rzone.de: 2607:f1c0:fe:53:185:132:34:128	AAAA	ns-anyslv.ui-dns.de (2001:8d8:fe:53:616e:7973:6c76:310a)

14. CAA - Entries

Domainname	flag	Value	∑ Queries
www.cloudwasmer.de			1
cloudwasmer.de	0	no CAA entry found	1
de	0	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
cloudwasmer.de	ok	1
www.cloudwasmer.de		1
_acme-challenge.cloudwasmer.de	missing entry or wrong length	1
_acme-challenge.www.cloudwasmer.de	Name Error - The domain name does not exist	1
_acme-challenge.cloudwasmer.de.cloudwasmer.de	perhaps wrong	1
_acme-challenge.www.cloudwasmer.de.cloudwasmer.de	perhaps wrong	1
_acme-challenge.www.cloudwasmer.de.www.cloudwasmer.de	Name Error - The domain name does not exist	1

16. DomainService - Entries

Type		Domain	Pref	Value	DNS-error	num Answers	Status
MX		cloudwasmer.de	5	smtpin.rzone.de	0	1	ok
	A			81.169.145.97	0	1	ok
	AAAA			2a01:238:20a:202:50f0::1097	0	1	ok
	CNAME				0	0	ok
_dmarc	TXT	_dmarc.cloudwasmer.de		v=DMARC1;p=reject;			ok

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=dcbc1401-c5ba-4f28-9d4d-050ccac01c42

Last Result: https://check-your-website.server-daten.de/?q=cloudwasmer.de - 2025-07-06 11:24:08

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

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