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



X

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

Checked:
10.06.2021 14:21:55


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
bc.n0w.cc


yes
2
0
www.bc.n0w.cc


yes
2
0
*.n0w.cc
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.bc.n0w.cc
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 14631, 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: 01.07.2021, 00:00:00 +, Signature-Inception: 10.06.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: cc
cc
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 519, DigestType 2 and Digest 4exklavTRWLm9DPe4gHmxqUssQr2nATWddppLS1WaJc=



1 RRSIG RR to validate DS RR found



RRSIG-Owner cc., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.06.2021, 05:00:00 +, Signature-Inception: 10.06.2021, 04:00:00 +, KeyTag 14631, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 2625, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner cc., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.06.2021, 14:34:08 +, Signature-Inception: 08.06.2021, 14:29:08 +, KeyTag 519, Signer-Name: cc



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



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

Zone: n0w.cc
n0w.cc
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 "824hnl7shjur7q638jreoc5bkm1992td" between the hashed NSEC3-owner "81v6mb68812rt7dreeqnce701vnhivdl" and the hashed NextOwner "82bl4v9m38sl9fbj1lh7atgburric32n". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 81v6mb68812rt7dreeqnce701vnhivdl.cc., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 16.06.2021, 21:20:08 +, Signature-Inception: 09.06.2021, 21:20:08 +, KeyTag 2625, Signer-Name: cc



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "rqgap5uf6q1ngvckfno8ranvdn5ilrin" as Owner. That's the Hash of "cc" with the NextHashedOwnerName "rqnnbpncoob0lrgg43150tgrhalk01ov". So that domain name is the Closest Encloser of "n0w.cc". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner rqgap5uf6q1ngvckfno8ranvdn5ilrin.cc., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 16.06.2021, 18:20:08 +, Signature-Inception: 09.06.2021, 18:20:08 +, KeyTag 2625, Signer-Name: cc



0 DNSKEY RR found




Zone: bc.n0w.cc
bc.n0w.cc
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.bc.n0w.cc
www.bc.n0w.cc
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
bc.n0w.cc
T  ns1.bc.n0w.cc
143.198.133.45
Santa Clara/California/United States (US) - DigitalOcean, LLC


T  ns2.bc.n0w.cc
143.198.133.45
Santa Clara/California/United States (US) - DigitalOcean, LLC

n0w.cc
  ns-1061.awsdns-04.org / 3bc1110bbbbbfb19153f993895ce402d -
205.251.196.37
London/England/United Kingdom (GB) - Amazon.com


 
2600:9000:5304:2500::1
Seattle/Washington/United States (US) - Amazon.com


  ns-180.awsdns-22.com / b085e4b5e9f11bafe4c40a599f175633 -
205.251.192.180
Paris/Île-de-France/France (FR) - Amazon.com


 
2600:9000:5300:b400::1
Seattle/Washington/United States (US) - Amazon.com


  ns-1803.awsdns-33.co.uk / 815d1b947b77b3e5f0a8dba18afcb170 -
205.251.199.11
Seattle/Washington/United States (US) - Amazon.com


 
2600:9000:5307:b00::1
Seattle/Washington/United States (US) - Amazon.com


  ns-607.awsdns-11.net / 43de7e8b25e75a931ef5210d04a3ef9a -
205.251.194.95
Ashburn/Virginia/United States (US) - Amazon.com


 
2600:9000:5302:5f00::1
Seattle/Washington/United States (US) - Amazon.com

cc
  ac1.nstld.com / nnn1-was1


  ac2.nstld.com / nnn1-ein3


  ac3.nstld.com / nnn1-fra6


  ac4.nstld.com / nnn1-fra6


4. SOA-Entries


Domain:cc
Zone-Name:cc
Primary:ac1.nstld.com
Mail:info.verisign-grs.com
Serial:1623327691
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:4


Domain:n0w.cc
Zone-Name:n0w.cc
Primary:ns-607.awsdns-11.net
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:8


Domain:bc.n0w.cc
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
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 "bc.n0w.cc" is subdomain, public suffix is ".cc", top-level-domain is ".cc", top-level-domain-type is "country-code", Country is Cocos (Keeling) Islands (the), tld-manager is "eNIC Cocos (Keeling) Islands Pty. Ltd. d/b/a Island Internet Services", num .cc-domains preloaded: 557 (complete: 151507)
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.
XFatal error: Nameserver doesn't support TCP connection: ns1.bc.n0w.cc / 143.198.133.45: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns2.bc.n0w.cc / 143.198.133.45: Timeout

2. DNS- and NameServer - Checks

AInfo:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 16 Queries complete, 16 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns-1061.awsdns-04.org, ns-180.awsdns-22.com, ns-1803.awsdns-33.co.uk, ns-607.awsdns-11.net, 4 Name Servers included in Delegation: ns-1061.awsdns-04.org, ns-180.awsdns-22.com, ns-1803.awsdns-33.co.uk, ns-607.awsdns-11.net, 4 Name Servers included in 1 Zone definitions: ns-1061.awsdns-04.org, ns-180.awsdns-22.com, ns-1803.awsdns-33.co.uk, ns-607.awsdns-11.net, 1 Name Servers listed in SOA.Primary: ns-607.awsdns-11.net.
AGood: Only one SOA.Primary Name Server found.: ns-607.awsdns-11.net.
AGood: SOA.Primary Name Server included in the delegation set.: ns-607.awsdns-11.net.
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): 205., 1 different subnets (first two Bytes): 205.251., 4 different subnets (first three Bytes): 205.251.192., 205.251.194., 205.251.196., 205.251.199.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2600:, 1 different subnets (first two blocks): 2600:9000:, 4 different subnets (first three blocks): 2600:9000:5300:, 2600:9000:5302:, 2600:9000:5304:, 2600:9000:5307:, 4 different subnets (first four blocks): 2600:9000:5300:b400:, 2600:9000:5302:5f00:, 2600:9000:5304:2500:, 2600:9000:5307:0b00:
AGood: Name Server IPv6 addresses from different subnets found.
XNameserver Timeout checking Echo Capitalization: ns1.bc.n0w.cc / 143.198.133.45
XNameserver Timeout checking Echo Capitalization: ns2.bc.n0w.cc / 143.198.133.45
XNameserver Timeout checking EDNS512: ns1.bc.n0w.cc / 143.198.133.45
XNameserver Timeout checking EDNS512: ns2.bc.n0w.cc / 143.198.133.45
Nameserver doesn't pass all EDNS-Checks: ns1.bc.n0w.cc / 143.198.133.45: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns2.bc.n0w.cc / 143.198.133.45: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
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: 356344 milliseconds, 356.344 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: ns-1061.awsdns-04.org, ns-180.awsdns-22.com, ns-1803.awsdns-33.co.uk, ns-607.awsdns-11.net

QNr.DomainTypeNS used
1
org
NS
k.root-servers.net (2001:7fd::1)

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
2
ns-1061.awsdns-04.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: g-ns-1031.awsdns-04.org, g-ns-132.awsdns-04.org, g-ns-1604.awsdns-04.org, g-ns-710.awsdns-04.org

Answer: g-ns-1031.awsdns-04.org
205.251.196.7, 2600:9000:5304:700::1

Answer: g-ns-132.awsdns-04.org
205.251.192.132, 2600:9000:5300:8400::1

Answer: g-ns-1604.awsdns-04.org
205.251.198.68, 2600:9000:5306:4400::1

Answer: g-ns-710.awsdns-04.org
205.251.194.198, 2600:9000:5302:c600::1
3
com
NS
d.root-servers.net (2001:500:2d::d)

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
4
ns-180.awsdns-22.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1174.awsdns-22.com, g-ns-1750.awsdns-22.com, g-ns-23.awsdns-22.com, g-ns-598.awsdns-22.com

Answer: g-ns-1174.awsdns-22.com
205.251.196.150, 2600:9000:5304:9600::1

Answer: g-ns-1750.awsdns-22.com
205.251.198.214, 2600:9000:5306:d600::1

Answer: g-ns-23.awsdns-22.com
205.251.192.23, 2600:9000:5300:1700::1

Answer: g-ns-598.awsdns-22.com
205.251.194.86, 2600:9000:5302:5600::1
5
uk
NS
k.root-servers.net (2001:7fd::1)

Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
6
ns-1803.awsdns-33.co.uk
NS
dns1.nic.uk (2a01:618:400::1)

Answer: g-ns-1508.awsdns-33.co.uk, g-ns-1829.awsdns-33.co.uk, g-ns-353.awsdns-33.co.uk, g-ns-929.awsdns-33.co.uk

Answer: g-ns-1508.awsdns-33.co.uk
205.251.197.228, 2600:9000:5305:e400::1

Answer: g-ns-1829.awsdns-33.co.uk
205.251.199.37, 2600:9000:5307:2500::1

Answer: g-ns-353.awsdns-33.co.uk
205.251.193.97, 2600:9000:5301:6100::1

Answer: g-ns-929.awsdns-33.co.uk
205.251.195.161, 2600:9000:5303:a100::1
7
net
NS
d.root-servers.net (2001:500:2d::d)

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

Answer: g-ns-1355.awsdns-11.net, g-ns-1931.awsdns-11.net, g-ns-460.awsdns-11.net, g-ns-781.awsdns-11.net

Answer: g-ns-1355.awsdns-11.net
205.251.197.75, 2600:9000:5305:4b00::1

Answer: g-ns-1931.awsdns-11.net
205.251.199.139, 2600:9000:5307:8b00::1

Answer: g-ns-460.awsdns-11.net
205.251.193.204, 2600:9000:5301:cc00::1

Answer: g-ns-781.awsdns-11.net
205.251.195.13, 2600:9000:5303:d00::1
9
ns-1061.awsdns-04.org: 205.251.196.37
A
g-ns-1031.awsdns-04.org (2600:9000:5304:700::1)
10
ns-1061.awsdns-04.org: 2600:9000:5304:2500::1
AAAA
g-ns-1031.awsdns-04.org (2600:9000:5304:700::1)
11
ns-180.awsdns-22.com: 205.251.192.180
A
g-ns-1174.awsdns-22.com (2600:9000:5304:9600::1)
12
ns-180.awsdns-22.com: 2600:9000:5300:b400::1
AAAA
g-ns-1174.awsdns-22.com (2600:9000:5304:9600::1)
13
ns-1803.awsdns-33.co.uk: 205.251.199.11
A
g-ns-1508.awsdns-33.co.uk (2600:9000:5305:e400::1)
14
ns-1803.awsdns-33.co.uk: 2600:9000:5307:b00::1
AAAA
g-ns-1508.awsdns-33.co.uk (2600:9000:5305:e400::1)
15
ns-607.awsdns-11.net: 205.251.194.95
A
g-ns-1355.awsdns-11.net (2600:9000:5305:4b00::1)
16
ns-607.awsdns-11.net: 2600:9000:5302:5f00::1
AAAA
g-ns-1355.awsdns-11.net (2600:9000:5305:4b00::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
bc.n0w.cc



2
0
n0w.cc
0

no CAA entry found
1
0
cc
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
n0w.cc

ok
1
0
bc.n0w.cc


2
0
_acme-challenge.bc.n0w.cc


2
0
_acme-challenge.bc.n0w.cc.n0w.cc

Name Error - The domain name does not exist
1
0
_acme-challenge.bc.n0w.cc.bc.n0w.cc


2
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=b6d67a12-da2f-432b-a074-a581aa9f2edf


Last Result: https://check-your-website.server-daten.de/?q=bc.n0w.cc - 2021-06-10 14:21:55


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

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