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



X

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

Checked:
11.09.2019 06:54:40


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
cloud-myweb.dynv6.net
A
77.183.185.201
Berlin/Land Berlin/Germany (DE) - Telefonica Germany GmbH & Co. OHG
Hostname: x4db7b9c9.dyn.telefonica.de
yes
1
0

AAAA

yes


www.cloud-myweb.dynv6.net
A

yes
1
0

AAAA

yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



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 59944, 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.2019, 00:00:00 +, Signature-Inception: 09.09.2019, 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: net
net
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.09.2019, 20:00:00 +, Signature-Inception: 10.09.2019, 19:00:00 +, KeyTag 59944, Signer-Name: (root)



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 2129, Flags 256



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



Public Key with Algorithm 8, KeyTag 59540, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.09.2019, 16:28:30 +, Signature-Inception: 07.09.2019, 16:23:30 +, KeyTag 35886, Signer-Name: net



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



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

Zone: dynv6.net
dynv6.net
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 "oi6dibn2el5qkpkjhc77dnl9s59ed5um" between the hashed NSEC3-owner "oi6bo5120e2uson550gbsf4thj5u4a6l" and the hashed NextOwner "oi6ehhnn7ujaieph1k2lt3vkji82jefo". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner oi6bo5120e2uson550gbsf4thj5u4a6l.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 15.09.2019, 05:52:16 +, Signature-Inception: 08.09.2019, 04:42:16 +, KeyTag 59540, Signer-Name: net



0 DNSKEY RR found




Zone: cloud-myweb.dynv6.net
cloud-myweb.dynv6.net
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.cloud-myweb.dynv6.net
www.cloud-myweb.dynv6.net
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.cloud-myweb.dynv6.net
 

cloud-myweb.dynv6.net
U  ns1.dynv6.com
95.216.144.82
Tuusula/Uusimaa/Finland (FI) - HETZNER-DC


U 
2a01:4f9:c010:95b::
Tuusula/Uusimaa/Finland (FI) - Hetzner Online GmbH


U  ns2.dynv6.com
185.55.116.153
Bremen/Germany (DE) - LWLcom GmbH


U 
2a00:c380:c0de::5353
Bremen/Germany (DE) - LWLcom GmbH


U  ns3.dynv6.com
159.69.43.243
Nuremberg/Bavaria/Germany (DE) - Hetzner


U 
2a01:4f8:1c1c:4c96::
Nuremberg/Bavaria/Germany (DE) - Hetzner

dynv6.net
U  ns1.dynv6.net


U  ns2.dynv6.net


U  ns3.dynv6.net

net
  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. SOA-Entries


Domain:net
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1568177663
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:13


Domain:dynv6.net
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:3


Domain:cloud-myweb.dynv6.net
Zone-Name:
Primary:ns1.dynv6.net
Mail:hostmaster.dyvn6.net
Serial:0
Refresh:1800
Retry:3600
Expire:86400
TTL:60
num Entries:6


Domain:www.cloud-myweb.dynv6.net
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-myweb.dynv6.net/
77.183.185.201
-14

10.027
T
Timeout - The operation has timed out

• https://cloud-myweb.dynv6.net/
77.183.185.201
-14

10.010
T
Timeout - The operation has timed out

• http://cloud-myweb.dynv6.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
77.183.185.201
-14

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

7. Comments


1. General Results, most used to calculate the result

Aname "cloud-myweb.dynv6.net" is domain, public suffix is "dynv6.net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
AGood: All ip addresses are public addresses
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 isn't defined or has timeout
XFatal error: Nameserver doesn't support TCP connection: ns1.dynv6.com / 95.216.144.82: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 95.216.144.82:53
XFatal error: Nameserver doesn't support TCP connection: ns1.dynv6.com / 2a01:4f9:c010:95b::: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it [2a01:4f9:c010:95b::]:53
XFatal error: Nameserver doesn't support TCP connection: ns1.dynv6.net: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 95.216.144.82:53
XFatal error: Nameserver doesn't support TCP connection: ns2.dynv6.com / 185.55.116.153: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 185.55.116.153:53
XFatal error: Nameserver doesn't support TCP connection: ns2.dynv6.com / 2a00:c380:c0de::5353: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it [2a00:c380:c0de::5353]:53
XFatal error: Nameserver doesn't support TCP connection: ns2.dynv6.net: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 185.55.116.153:53
XFatal error: Nameserver doesn't support TCP connection: ns3.dynv6.com / 159.69.43.243: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 159.69.43.243:53
XFatal error: Nameserver doesn't support TCP connection: ns3.dynv6.com / 2a01:4f8:1c1c:4c96::: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it [2a01:4f8:1c1c:4c96::]:53
XFatal error: Nameserver doesn't support TCP connection: ns3.dynv6.net: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 159.69.43.243:53

2. DNS- and NameServer - Checks

AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.dynv6.com
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.dynv6.net
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.dynv6.com
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.dynv6.net
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns3.dynv6.com
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns3.dynv6.net

Nameserver doesn't pass all EDNS-Checks: ns1.dynv6.com / 95.216.144.82: 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: ns1.dynv6.com / 2a01:4f9:c010:95b::: 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: ns1.dynv6.net: 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.dynv6.com / 185.55.116.153: 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.dynv6.com / 2a00:c380:c0de::5353: 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.dynv6.net: 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: ns3.dynv6.com / 159.69.43.243: 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: ns3.dynv6.com / 2a01:4f8:1c1c:4c96::: 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: ns3.dynv6.net: 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-myweb.dynv6.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.183.185.201
-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.
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: 144393 milliseconds, 144.393 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)

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0
1
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
3970446185
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-07-21 05:15:04
2022-10-19 05:15:03
cloud-myweb.dynv6.net, fritzco.myweb.dynv6.net, myweb.dynv6.net, schlicker.dynv6.net, wake.myweb.dynv6.net - 5 entries


3868965572
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-06-21 22:12:49
2022-09-19 22:12:48
cloud-myweb.dynv6.net, fritzco.myweb.dynv6.net, myweb.dynv6.net, schlicker.dynv6.net - 4 entries



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=R3, O=Let's Encrypt, C=US
0 /0 new
1
6

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
7170446932
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-07-21 03:15:04
2022-10-19 03:15:03
cloud-myweb.dynv6.net, fritzco.myweb.dynv6.net, myweb.dynv6.net, schlicker.dynv6.net, wake.myweb.dynv6.net
5 entries


6984251011
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-06-21 20:12:49
2022-09-19 20:12:48
cloud-myweb.dynv6.net, fritzco.myweb.dynv6.net, myweb.dynv6.net, schlicker.dynv6.net
4 entries


6593955107
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-04-22 16:49:57
2022-07-21 16:49:56
cloud-myweb.dynv6.net, fritzco.myweb.dynv6.net, myweb.dynv6.net, schlicker.dynv6.net
4 entries


6437887237
precert
CN=R3, O=Let's Encrypt, C=US
2022-03-29 20:08:35
2022-06-27 20:08:34
cloud-myweb.dynv6.net, myweb.dynv6.net, schlicker.dynv6.net
3 entries


6079788261
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-01-28 21:37:25
2022-04-28 20:37:24
cloud-myweb.dynv6.net, myweb.dynv6.net, schlicker.dynv6.net
3 entries


5703354378
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-11-29 21:56:03
2022-02-27 21:56:02
cloud-myweb.dynv6.net, myweb.dynv6.net, schlicker.dynv6.net
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:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.cloud-myweb.dynv6.net
0

no CAA entry found
1
0
cloud-myweb.dynv6.net
0

no CAA entry found
1
0
dynv6.net
-3

Name Error - The domain name does not exist
1
0
net
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
cloud-myweb.dynv6.net

ok
1
0
www.cloud-myweb.dynv6.net

ok
1
0
_acme-challenge.cloud-myweb.dynv6.net

missing entry or wrong length
1
0
_acme-challenge.www.cloud-myweb.dynv6.net

missing entry or wrong length
1
0
_acme-challenge.cloud-myweb.dynv6.net.cloud-myweb.dynv6.net

perhaps wrong
1
0
_acme-challenge.www.cloud-myweb.dynv6.net.cloud-myweb.dynv6.net

perhaps wrong
1
0
_acme-challenge.www.cloud-myweb.dynv6.net.www.cloud-myweb.dynv6.net

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=a70da123-62d9-4dbe-909b-fb42527b6328


Last Result: https://check-your-website.server-daten.de/?q=cloud-myweb.dynv6.net - 2022-07-29 21:06:40


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-myweb.dynv6.net" target="_blank">Check this Site: cloud-myweb.dynv6.net</a>

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