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



X

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

Checked:
14.09.2021 22:09:00


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
api.cravosity.io
CNAME
174.129.69.21
yes
1
0
www.api.cravosity.io

Name Error
yes
1
0
*.cravosity.io
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.api.cravosity.io
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 26838, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 30.09.2021, 00:00:00 +, Signature-Inception: 09.09.2021, 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: 27.09.2021, 17:00:00 +, Signature-Inception: 14.09.2021, 16:00:00 +, KeyTag 26838, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 17763, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner io., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.10.2021, 15:17:11 +, Signature-Inception: 13.09.2021, 14:17:11 +, 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: cravosity.io
cravosity.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 "370a1a78grc9e30r8vjfjpmemufh0gd9" between the hashed NSEC3-owner "36vb0b7kbdpsko8bnedrugvmait54645" and the hashed NextOwner "370ktag11p15t55r1bk212v18ttrqfhi". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 36vb0b7kbdpsko8bnedrugvmait54645.io., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 04.10.2021, 15:17:11 +, Signature-Inception: 13.09.2021, 14:17:11 +, KeyTag 17763, 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 "cravosity.io". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 0d790076pp5pfktg2hrthj5bj6ckckcb.io., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 05.10.2021, 20:08:13 +, Signature-Inception: 14.09.2021, 19:08:13 +, KeyTag 17763, Signer-Name: io



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 38799, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner cravosity.io., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 04.10.2021, 18:32:06 +, Signature-Inception: 12.09.2021, 18:32:06 +, KeyTag 29924, Signer-Name: cravosity.io



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



Error: DNSKEY 29924 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.

Zone: api.cravosity.io
api.cravosity.io
0 DS RR in the parent zone found



RRSIG Type 5 validates the CNAME - Result: 174.129.69.21
Validated: RRSIG-Owner api.cravosity.io., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 04.10.2021, 18:32:06 +, Signature-Inception: 12.09.2021, 18:32:06 +, KeyTag 38799, Signer-Name: cravosity.io

Zone: www.api.cravosity.io
www.api.cravosity.io
0 DS RR in the parent zone found



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "f6a6mcu6jk0dlej2arr41k5qfmgoo8m0" as Owner. That's the Hash of "api.cravosity.io" with the NextHashedOwnerName "grsin1ivofcic63475fnms1clj0b0ft5". So that domain name is the Closest Encloser of "www.api.cravosity.io". Opt-Out: False.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner f6a6mcu6jk0dlej2arr41k5qfmgoo8m0.cravosity.io., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 04.10.2021, 18:32:06 +, Signature-Inception: 12.09.2021, 18:32:06 +, KeyTag 38799, Signer-Name: cravosity.io



The ClosestEncloser says, that "*.api.cravosity.io" with the Hash "0qffid5lu9644epb6tod7uqvaspc2g69" 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 "s4que8jce2a3s7o5k9qm174sf8uir7or" and the Next Owner "73c04irdt14avjojkin49ngh4b7f3bn9", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: A, RRSIG Validated: RRSIG-Owner s4que8jce2a3s7o5k9qm174sf8uir7or.cravosity.io., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 04.10.2021, 18:32:06 +, Signature-Inception: 12.09.2021, 18:32:06 +, KeyTag 38799, Signer-Name: cravosity.io


3. Name Servers

DomainNameserverNS-IP
www.api.cravosity.io
  ns-cloud-d1.googledomains.com

cravosity.io
  ns-cloud-d1.googledomains.com
216.239.32.109
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:32::6d
Mountain View/California/United States (US) - Google LLC


  ns-cloud-d2.googledomains.com
216.239.34.109
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:34::6d
Mountain View/California/United States (US) - Google LLC


  ns-cloud-d3.googledomains.com
216.239.36.109
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:36::6d
Mountain View/California/United States (US) - Google LLC


  ns-cloud-d4.googledomains.com
216.239.38.109
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:38::6d
Mountain View/California/United States (US) - Google LLC

io
  a0.nic.io / ns087b.app22.nrt1.afilias-nst.info


  a2.nic.io / LHR5


T  b0.nic.io / ns087a.app32.ams2.afilias-nst.info


T  c0.nic.io / ns087a.app31.ams2.afilias-nst.info


4. SOA-Entries


Domain:io
Zone-Name:io
Primary:a0.nic.io
Mail:noc.afilias-nst.info
Serial:1498168403
Refresh:10800
Retry:3600
Expire:2764800
TTL:900
num Entries:4


Domain:cravosity.io
Zone-Name:cravosity.io
Primary:ns-cloud-d1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:23
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


Domain:www.api.cravosity.io
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







7. Comments


1. General Results, most used to calculate the result

Aname "api.cravosity.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: 1744 (complete: 168171)
Agood: All ip addresses are public addresses
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.
XFatal: Wrong CNAME definition found.Domain name: api.cravosity.io, CNAME: 174.129.69.21: IPv4 address found, but not allowed. Only domain names are allowed.

2. DNS- and NameServer - Checks

AInfo:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 13 Queries complete, 13 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-d1.googledomains.com.
AGood: Only one SOA.Primary Name Server found.: ns-cloud-d1.googledomains.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-cloud-d1.googledomains.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: 4 Name Servers, 1 different subnets (first Byte): 216., 1 different subnets (first two Bytes): 216.239., 4 different subnets (first three Bytes): 216.239.32., 216.239.34., 216.239.36., 216.239.38.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:4860:, 1 different subnets (first three blocks): 2001:4860:4802:, 4 different subnets (first four blocks): 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2001:4860:4802:0036:, 2001:4860:4802:0038:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
XNameserver Timeout checking Echo Capitalization: b0.nic.io
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
XNameserver Timeout checking EDNS512: b0.nic.io
XNameserver Timeout checking EDNS512: c0.nic.io
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
Nameserver doesn't pass all EDNS-Checks: b0.nic.io: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (ns087a.app32.ams2.afilias-nst.info). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns-cloud-d1.googledomains.com: 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

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: 59786 milliseconds, 59.786 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

Issuerlast 7 daysactivenum Certs
CN=Amazon, OU=Server CA 1B, O=Amazon, C=US
0
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
5201169455
precert
CN=Amazon, OU=Server CA 1B, O=Amazon, C=US
2021-09-10 22:00:00
2022-10-10 21:59:59
*.cravosity.io, cravosity.io, www.cravosity.io
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: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com

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

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

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
3
ns-cloud-d2.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
4
ns-cloud-d3.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
5
ns-cloud-d4.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
6
ns-cloud-d1.googledomains.com: 216.239.32.109
A
ns5.googledomains.com (2001:4860:4802:32::a)
7
ns-cloud-d1.googledomains.com: 2001:4860:4802:32::6d
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
8
ns-cloud-d2.googledomains.com: 216.239.34.109
A
ns5.googledomains.com (2001:4860:4802:32::a)
9
ns-cloud-d2.googledomains.com: 2001:4860:4802:34::6d
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
10
ns-cloud-d3.googledomains.com: 216.239.36.109
A
ns5.googledomains.com (2001:4860:4802:32::a)
11
ns-cloud-d3.googledomains.com: 2001:4860:4802:36::6d
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
12
ns-cloud-d4.googledomains.com: 216.239.38.109
A
ns5.googledomains.com (2001:4860:4802:32::a)
13
ns-cloud-d4.googledomains.com: 2001:4860:4802:38::6d
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
api.cravosity.io



1
0
cravosity.io
0

no CAA entry found
1
0
io
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
cravosity.io
facebook-domain-verification=ckkv6qb1wbe46ab4wl1vjbvslv45rw
ok
1
0
cravosity.io
google-site-verification=rEr_M2PxACFLoW-GzccqllHAhLdOzHQW30cQwuG9cfA
ok
1
0
cravosity.io
google-site-verification=tIRRpPegoMsqvYk-sQ_jBbY0dgf_G0nzV5PLCpezbkU
ok
1
0
cravosity.io
MS=ms48754606
ok
1
0
cravosity.io
v=spf1 include:_spf.google.com ~all
ok
1
0
api.cravosity.io


1
0
_acme-challenge.api.cravosity.io

Name Error - The domain name does not exist
1
0
_acme-challenge.api.cravosity.io.cravosity.io

Name Error - The domain name does not exist
1
0
_acme-challenge.api.cravosity.io.api.cravosity.io

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=06ec49ba-8a2e-4099-971f-733261a3e7b9


Last Result: https://check-your-website.server-daten.de/?q=api.cravosity.io - 2021-09-14 22:09:00


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

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