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



T

Timeout

Checked:
21.11.2020 21:09:06


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
cloud.itcouldbeworse.de
CNAME
itcouldbeworse.de
yes
1
0

A
77.0.82.206
Hamburg/Germany (DE) - Telefonica Deutschland GmbH
Hostname: dynamic-077-000-082-206.77.0.pool.telefonica.de
yes


www.cloud.itcouldbeworse.de

Name Error
yes
1
0
*.itcouldbeworse.de
A

yes



AAAA

yes



CNAME

yes


*.cloud.itcouldbeworse.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 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 26116, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.12.2020, 00:00:00 +, Signature-Inception: 20.11.2020, 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 45580, DigestType 2 and Digest kYwy4vEiEXZr5iJmdPRHRY8iWbmg2HtE0p1Vr+ymsuE=



1 RRSIG RR to validate DS RR found



RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.12.2020, 17:00:00 +, Signature-Inception: 21.11.2020, 16:00:00 +, KeyTag 26116, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 60906, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 05.12.2020, 16:12:03 +, Signature-Inception: 21.11.2020, 14:42:03 +, KeyTag 45580, Signer-Name: de



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



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

Zone: itcouldbeworse.de
itcouldbeworse.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 "cs0u7i02hf4vtort747kqgv56bg32bm4" between the hashed NSEC3-owner "cs0qmh1glstgp80r1lfgd7skri78mj4g" and the hashed NextOwner "cs0um6jnej5009dicolfsct3ssa987pq". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner cs0qmh1glstgp80r1lfgd7skri78mj4g.de., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 01.12.2020, 04:11:35 +, Signature-Inception: 17.11.2020, 02:41:35 +, KeyTag 60906, 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 "tjldgsug88n1tlru13fbbv506ssgjgbm". So that domain name is the Closest Encloser of "itcouldbeworse.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: 01.12.2020, 04:11:35 +, Signature-Inception: 17.11.2020, 02:41:35 +, KeyTag 60906, Signer-Name: de



0 DNSKEY RR found




Zone: cloud.itcouldbeworse.de
cloud.itcouldbeworse.de
0 DS RR in the parent zone found

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


3. Name Servers

DomainNameserverNS-IP
www.cloud.itcouldbeworse.de
  docks20.rzone.de

itcouldbeworse.de
  docks20.rzone.de / dns-pub-de-fra-fr701.server.lan
217.160.80.147
Frankfurt am Main/Hesse/Germany (DE) - 1&1 IONOS SE


 
2001:8d8:fe:53:5747:2a74:d:20
Suedweststadt/Baden-Württemberg/Germany (DE) - AS8560 anycast


  shades18.rzone.de / dns-pub-de-fra-fr701.server.lan
217.160.82.145
Frankfurt am Main/Hesse/Germany (DE) - 1&1 IONOS SE


 
2001:8d8:fe:53:5747:2a74:5:18
Suedweststadt/Baden-Württemberg/Germany (DE) - AS8560 anycast

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.amx


  s.de.net / ns-3.de.de9


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


4. SOA-Entries


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


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


Domain:www.cloud.itcouldbeworse.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

DomainnameHttp-StatusredirectSec.G
• http://cloud.itcouldbeworse.de/
77.0.82.206
-14

10.026
T
Timeout - The operation has timed out

• https://cloud.itcouldbeworse.de/
77.0.82.206
-14

10.013
T
Timeout - The operation has timed out

• http://cloud.itcouldbeworse.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
77.0.82.206
-14

10.043
T
Timeout - The operation has timed out
Visible Content:

• https://77.0.82.206/
77.0.82.206
-14

10.017
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "cloud.itcouldbeworse.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: 6338 (complete: 131120)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: cloud.itcouldbeworse.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: cloud.itcouldbeworse.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
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 cloud.itcouldbeworse.de, 1 ip addresses.

2. 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, 46 with IPv6, 3 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
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, shades18.rzone.de, 2 Name Servers included in Delegation: docks20.rzone.de, shades18.rzone.de, 2 Name Servers included in 1 Zone definitions: docks20.rzone.de, shades18.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: 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.
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 217., 1 different subnets (first two Bytes): 217.160., 2 different subnets (first three Bytes): 217.160.80., 217.160.82.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:08d8:, 1 different subnets (first three blocks): 2001:08d8:00fe:, 1 different subnets (first four blocks): 2001:08d8:00fe:0053:
Fatal: All Name Server IPv6 addresses from the same subnet.
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 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.

3. Content- and Performance-critical Checks

http://cloud.itcouldbeworse.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.0.82.206
-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.
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
ADuration: 126826 milliseconds, 126.826 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" > 2019 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. Nameserver - IP-Adresses

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

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

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.4, 2a01:238:e100:192::4
3
shades18.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.4, 2a01:238:e100:192::4
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
2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.193
5
biz
NS
a.root-servers.net (2001:503:ba3e::2:30)

Answer: a.gtld.biz, b.gtld.biz, c.gtld.biz, e.gtld.biz, f.gtld.biz, k.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
2001:8d8:fe:53:0:d9a0:51c3:100, 217.160.81.195
7
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
8
ns-de.ui-dns.com
NS
b.gtld-servers.net (192.33.14.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
2001:8d8:fe:53:0:d9a0:52c2:100, 217.160.82.194
9
org
NS
f.root-servers.net (2001:500:2f::f)

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
2001:8d8:fe:53:0:d9a0:53c4:100, 217.160.83.196
11
ns-biz.ui-dns.com
NS
b.gtld-servers.net (192.33.14.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
2001:8d8:fe:53:0:d9a0:52c2:100, 217.160.82.194
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
2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.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
2001:8d8:fe:53:0:d9a0:53c4:100, 217.160.83.196
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
2001:8d8:fe:53:0:d9a0:51c3:100, 217.160.81.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
2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.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
2001:8d8:fe:53:0:d9a0:53c4:100, 217.160.83.196
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
2001:8d8:fe:53:0:d9a0:51c3:100, 217.160.81.195
18
ns-org.ui-dns.com
NS
b.gtld-servers.net (192.33.14.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
2001:8d8:fe:53:0:d9a0:52c2:100, 217.160.82.194
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
2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.193
20
ns-anyslv.ui-dns.de: 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
AAAA
ns-de.ui-dns.de (2001:8d8:fe:53:0:d9a0:50c1:100)
22
ns-de.ui-dns.biz: 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
AAAA
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
24
ns-de.ui-dns.com: 217.160.82.193
A
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52c2:100)
25
ns-de.ui-dns.com: 2001:8d8:fe:53:0:d9a0:52c1:100
AAAA
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52c2:100)
26
ns-de.ui-dns.org: 217.160.83.193
A
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
27
ns-de.ui-dns.org: 2001:8d8:fe:53:0:d9a0:53c1:100
AAAA
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
28
ns-biz.ui-dns.com: 217.160.82.195
A
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52c2:100)
29
ns-biz.ui-dns.com: 2001:8d8:fe:53:0:d9a0:52c3:100
AAAA
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52c2:100)
30
ns-biz.ui-dns.de: 217.160.80.195
A
ns-de.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c1:100)
31
ns-biz.ui-dns.de: 2001:8d8:fe:53:0:d9a0:50c3:100
AAAA
ns-de.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c1:100)
32
ns-biz.ui-dns.org: 217.160.83.195
A
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
33
ns-biz.ui-dns.org: 2001:8d8:fe:53:0:d9a0:53c3:100
AAAA
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
34
ns-com.ui-dns.biz: 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
AAAA
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
36
ns-com.ui-dns.de: 217.160.80.194
A
ns-de.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c1:100)
37
ns-com.ui-dns.de: 2001:8d8:fe:53:0:d9a0:50c2:100
AAAA
ns-de.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c1:100)
38
ns-com.ui-dns.org: 217.160.83.194
A
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
39
ns-com.ui-dns.org: 2001:8d8:fe:53:0:d9a0:53c2:100
AAAA
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
40
ns-org.ui-dns.biz: 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
AAAA
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
42
ns-org.ui-dns.com: 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
AAAA
ns-com.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c2:100)
44
ns-org.ui-dns.de: 217.160.80.196
A
ns-de.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c1:100)
45
ns-org.ui-dns.de: 2001:8d8:fe:53:0:d9a0:50c4:100
AAAA
ns-de.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c1:100)
46
docks20.rzone.de: 217.160.80.147
A
ns-anyslv.ui-dns.de (2001:8d8:fe:53:616e:7973:6c76:310a)
47
docks20.rzone.de: 2001:8d8:fe:53:5747:2a74:d:20
AAAA
ns-anyslv.ui-dns.de (2001:8d8:fe:53:616e:7973:6c76:310a)
48
shades18.rzone.de: 217.160.82.145
A
ns-anyslv.ui-dns.de (2001:8d8:fe:53:616e:7973:6c76:310a)
49
shades18.rzone.de: 2001:8d8:fe:53:5747:2a74:5:18
AAAA
ns-anyslv.ui-dns.de (2001:8d8:fe:53:616e:7973:6c76:310a)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
cloud.itcouldbeworse.de



1
0
itcouldbeworse.de
0

no CAA entry found
1
0
de
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
itcouldbeworse.de

ok
1
0
cloud.itcouldbeworse.de


1
0
_acme-challenge.cloud.itcouldbeworse.de

Name Error - The domain name does not exist
1
0
_acme-challenge.cloud.itcouldbeworse.de.itcouldbeworse.de

perhaps wrong
1
0
_acme-challenge.cloud.itcouldbeworse.de.cloud.itcouldbeworse.de

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=87d05bca-801c-41e0-b418-1acfc8d74bd1


Last Result: https://check-your-website.server-daten.de/?q=cloud.itcouldbeworse.de - 2020-11-21 21:09:06


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

<a href="https://check-your-website.server-daten.de/?q=cloud.itcouldbeworse.de" target="_blank">Check this Site: cloud.itcouldbeworse.de</a>