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




X

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

Checked:
24.01.2023 23:11:04


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
files.nextcloud.io
A

yes
1
0

AAAA

yes


www.files.nextcloud.io
A

yes
1
0

AAAA

yes


*.nextcloud.io
A

yes



AAAA

yes



CNAME

yes


*.files.nextcloud.io
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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 951, 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: 11.02.2023, 00:00:00 +, Signature-Inception: 21.01.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: io
io
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 57355, DigestType 2 and Digest laV8O6t4SdvN33xyracaiBRrFBEQMYylvmcgV+hlw+I=



1 RRSIG RR to validate DS RR found



RRSIG-Owner io., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 06.02.2023, 17:00:00 +, Signature-Inception: 24.01.2023, 16:00:00 +, KeyTag 951, Signer-Name: (root)



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



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 59265, Flags 256



Public Key with Algorithm 8, KeyTag 63585, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner io., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 07.02.2023, 16:09:56 +, Signature-Inception: 17.01.2023, 15:09:56 +, KeyTag 57355, Signer-Name: io



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



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

Zone: nextcloud.io
nextcloud.io
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 "hh03hdg0oimk6i0i4qo3erhpam5ooc3t" between the hashed NSEC3-owner "hgvp6an3r990cfahcha2gud9j2gjslh1" and the hashed NextOwner "hh0l33p225ns1j03er9r3gmii1q38j8u". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner hgvp6an3r990cfahcha2gud9j2gjslh1.io., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 07.02.2023, 16:09:56 +, Signature-Inception: 17.01.2023, 15:09:56 +, KeyTag 63585, Signer-Name: io



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "0d790076pp5pfktg2hrthj5bj6ckckcb" as Owner. That's the Hash of "io" with the NextHashedOwnerName "0d7bd4g2j0sls1qj0ovhk6nsri6v9mik". So that domain name is the Closest Encloser of "nextcloud.io". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 0d790076pp5pfktg2hrthj5bj6ckckcb.io., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 14.02.2023, 22:10:24 +, Signature-Inception: 24.01.2023, 21:10:24 +, KeyTag 63585, Signer-Name: io



0 DNSKEY RR found




Zone: files.nextcloud.io
files.nextcloud.io
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.files.nextcloud.io
www.files.nextcloud.io
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
nextcloud.io
  ns1.dan.com
54.72.100.175
Dublin/Leinster/Ireland (IE) - Amazon.com, Inc.


  ns2.dan.com
52.28.84.253
Frankfurt am Main/Hesse/Germany (DE) - Amazon.com, Inc.

io
  a0.nic.io / app14.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861


  a2.nic.io / FRA4


  b0.nic.io / app24.ams2.hosts.meta.redstone.afilias-nst.info-1615580861


  c0.nic.io / app21.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861


4. SOA-Entries


Domain:io
Zone-Name:io
Primary:a0.nic.io
Mail:hostmaster.donuts.email
Serial:1674597289
Refresh:7200
Retry:900
Expire:1209600
TTL:3600
num Entries:1


Domain:io
Zone-Name:io
Primary:a0.nic.io
Mail:hostmaster.donuts.email
Serial:1674597921
Refresh:7200
Retry:900
Expire:1209600
TTL:3600
num Entries:3


Domain:nextcloud.io
Zone-Name:nextcloud.io
Primary:ns1.dan.com
Mail:root.dan.com
Serial:2015042809
Refresh:10000
Retry:7200
Expire:1209600
TTL:300
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

DomainnameHttp-StatusredirectSec.G







7. Comments


1. General Results, most used to calculate the result

Aname "files.nextcloud.io" is subdomain, public suffix is ".io", top-level-domain is ".io", top-level-domain-type is "country-code", Country is British Indian Ocean Territory (the), tld-manager is "IO Top Level Domain Registry", num .io-domains preloaded: 2163 (complete: 216710)
AGood: 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.
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.files.nextcloud.io

2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete)

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns1.dan.com, ns2.dan.com, 2 Name Servers included in Delegation: ns1.dan.com, ns2.dan.com, 2 Name Servers included in 1 Zone definitions: ns1.dan.com, ns2.dan.com, 1 Name Servers listed in SOA.Primary: ns1.dan.com.
AGood: Only one SOA.Primary Name Server found.: ns1.dan.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.dan.com.
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, 2 different subnets (first Byte): 52., 54., 2 different subnets (first two Bytes): 52.28., 54.72., 2 different subnets (first three Bytes): 52.28.84., 54.72.100.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.dan.com
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.dan.com
Nameserver doesn't pass all EDNS-Checks: ns1.dan.com / 54.72.100.175: 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.
Nameserver doesn't pass all EDNS-Checks: ns2.dan.com / 52.28.84.253: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

AGood: 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: 48740 milliseconds, 48.740 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

Issuerlast 7 daysactivenum Certs
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
0
0
2
CN=R3, O=Let's Encrypt, C=US
0 /0 new
0
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
6921619607
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-06-11 21:40:45
2022-09-09 21:40:44
*.nextcloud.io, nextcloud.io
2 entries


5987973330
precert
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
2022-01-15 23:00:00
2023-01-16 22:59:59
*.nextcloud.io, nextcloud.io, sni.cloudflaressl.com
3 entries


4473576609
precert
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
2021-05-03 22:00:00
2022-05-03 21:59:59
*.nextcloud.io, nextcloud.io, sni.cloudflaressl.com
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.dan.com, ns2.dan.com

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

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.dan.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: emma.ns.cloudflare.com, will.ns.cloudflare.com

Answer: emma.ns.cloudflare.com
108.162.192.112, 172.64.32.112, 173.245.58.112, 2606:4700:50::adf5:3a70, 2803:f800:50::6ca2:c070, 2a06:98c1:50::ac40:2070

Answer: will.ns.cloudflare.com
108.162.193.149, 172.64.33.149, 173.245.59.149, 2606:4700:58::adf5:3b95, 2803:f800:50::6ca2:c195, 2a06:98c1:50::ac40:2195
3
ns2.dan.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: emma.ns.cloudflare.com, will.ns.cloudflare.com

Answer: emma.ns.cloudflare.com
108.162.192.112, 172.64.32.112, 173.245.58.112, 2606:4700:50::adf5:3a70, 2803:f800:50::6ca2:c070, 2a06:98c1:50::ac40:2070

Answer: will.ns.cloudflare.com
108.162.193.149, 172.64.33.149, 173.245.59.149, 2606:4700:58::adf5:3b95, 2803:f800:50::6ca2:c195, 2a06:98c1:50::ac40:2195
4
ns1.dan.com: 54.72.100.175
A
emma.ns.cloudflare.com (2606:4700:50::adf5:3a70)
5
ns1.dan.com: No AAAA record found
AAAA
emma.ns.cloudflare.com (2606:4700:50::adf5:3a70)
6
ns2.dan.com: 52.28.84.253
A
emma.ns.cloudflare.com (2606:4700:50::adf5:3a70)
7
ns2.dan.com: No AAAA record found
AAAA
emma.ns.cloudflare.com (2606:4700:50::adf5:3a70)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.files.nextcloud.io
0

no CAA entry found
1
0
files.nextcloud.io
0

no CAA entry found
1
0
nextcloud.io
0

no CAA entry found
1
0
io
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
nextcloud.io
v=spf1 -all
ok
1
0
files.nextcloud.io

ok
1
0
www.files.nextcloud.io

ok
1
0
_acme-challenge.files.nextcloud.io

missing entry or wrong length
1
0
_acme-challenge.www.files.nextcloud.io

missing entry or wrong length
1
0
_acme-challenge.files.nextcloud.io.nextcloud.io

perhaps wrong
1
0
_acme-challenge.files.nextcloud.io.files.nextcloud.io

perhaps wrong
1
0
_acme-challenge.www.files.nextcloud.io.files.nextcloud.io

perhaps wrong
1
0
_acme-challenge.www.files.nextcloud.io.www.files.nextcloud.io

perhaps wrong
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks

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



Permalink: https://check-your-website.server-daten.de/?i=3dd73c74-8830-4f9a-8522-0cd569ce9a9e


Last Result: https://check-your-website.server-daten.de/?q=files.nextcloud.io - 2023-01-24 23:11:04


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

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

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro