X

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

Checked:
15.05.2019 14:18:29


Older results

No older results found


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
bearhugs.duckdns.org
A
212.149.178.154
Hostname: 212-149-178-154.bb.dnainternet.fi
yes
1
0

AAAA

yes


www.bearhugs.duckdns.org
A
212.149.178.154
Hostname: 212-149-178-154.bb.dnainternet.fi
yes
1
0

AAAA

yes



2. DNSSEC

Zone (*)DNSSEC - Informations (beta)
(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 25266, Flags 256

1 RRSIG RR to validate DNSKEY RR found

Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.06.2019, 00:00:00, Signature-Inception: 11.05.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
org
2 DS RR in the parent zone found

1 RRSIG RR to validate DS RR found

Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 28.05.2019, 05:00:00, Signature-Inception: 15.05.2019, 04:00:00, KeyTag 25266, Signer-Name: (root)

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

4 DNSKEY RR found

Public Key with Algorithm 7, KeyTag 9795, Flags 257 (SEP = Secure Entry Point)

Public Key with Algorithm 7, KeyTag 16454, Flags 256

Public Key with Algorithm 7, KeyTag 17883, Flags 257 (SEP = Secure Entry Point)

Public Key with Algorithm 7, KeyTag 50465, Flags 256

3 RRSIG RR to validate DNSKEY RR found

Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.05.2019, 15:23:32, Signature-Inception: 09.05.2019, 14:23:32, KeyTag 9795, Signer-Name: org

Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.05.2019, 15:23:32, Signature-Inception: 09.05.2019, 14:23:32, KeyTag 16454, Signer-Name: org

Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.05.2019, 15:23:32, Signature-Inception: 09.05.2019, 14:23:32, KeyTag 17883, Signer-Name: org

Status: Good - Algorithmus 7 and DNSKEY with KeyTag 9795 used to validate the DNSKEY RRSet

Status: Good - Algorithmus 7 and DNSKEY with KeyTag 16454 used to validate the DNSKEY RRSet

Status: Good - Algorithmus 7 and DNSKEY with KeyTag 17883 used to validate the DNSKEY RRSet

Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 1 and Digest "Nk36s9ryVMq0d7VnWxB2bdqiSYI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 2 and Digest "OSKzG286TqkrGet7UhIPAx/Y4F/wsDuvz5+JG/5/+OU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
duckdns.org
0 DS RR in the parent zone found

DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.

0 DNSKEY RR found


bearhugs.duckdns.org
0 DS RR in the parent zone found

0 DNSKEY RR found


www.bearhugs.duckdns.org
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.bearhugs.duckdns.org
U  ns1.duckdns.org


U  ns2.duckdns.org


U  ns3.duckdns.org

bearhugs.duckdns.org
U  ns1.duckdns.org
54.187.92.222

U  ns2.duckdns.org
54.191.117.119

U  ns3.duckdns.org
52.26.169.94
duckdns.org
U  ns1.duckdns.org


U  ns2.duckdns.org


U  ns3.duckdns.org

org
  a0.org.afilias-nst.info / ns000b.app14.mia2.afilias-nst.info


  a2.org.afilias-nst.info / 2.ber.pch


  b0.org.afilias-nst.org / ns000b.app3.ams2.afilias-nst.info


  b2.org.afilias-nst.org / 5.fra.pch


  c0.org.afilias-nst.info / ns000b.app27.ams2.afilias-nst.info


  d0.org.afilias-nst.org / app21.iad1.hosts.meta.redstone.afilias-nst.info-2


4. SOA-Entries


Domain:org
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2013470437
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:duckdns.org
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2018280802
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:duckdns.org
Primary:ns2.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2018280802
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:duckdns.org
Primary:ns3.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2018280802
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:bearhugs.duckdns.org
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2018280802
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:bearhugs.duckdns.org
Primary:ns2.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2018280802
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:bearhugs.duckdns.org
Primary:ns3.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2018280802
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:www.bearhugs.duckdns.org
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2018280802
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:www.bearhugs.duckdns.org
Primary:ns2.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2018280802
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:www.bearhugs.duckdns.org
Primary:ns3.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2018280802
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


5. Url-Checks

Domainname Http-StatusredirectSec.G
• http://bearhugs.duckdns.org/
212.149.178.154
-14

10.027
T
Timeout - The operation has timed out

• http://www.bearhugs.duckdns.org/
212.149.178.154
-14

10.030
T
Timeout - The operation has timed out

• https://bearhugs.duckdns.org/
212.149.178.154
-14

10.030
T
Timeout - The operation has timed out

• https://www.bearhugs.duckdns.org/
212.149.178.154
-14

10.026
T
Timeout - The operation has timed out

• http://bearhugs.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
212.149.178.154
-14

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

• http://www.bearhugs.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
212.149.178.154
-14

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

6. Comments

Aname "bearhugs.duckdns.org" is domain, public suffix is "duckdns.org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)"
Agood: All ip addresses are public addresses
XFatal error: Nameserver isn't defined or has timeout
XFatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org: 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 54.187.92.222:53
XFatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org / 54.187.92.222: 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 54.187.92.222:53
XFatal error: Nameserver doesn't support TCP connection: ns2.duckdns.org: 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 54.191.117.119:53
XFatal error: Nameserver doesn't support TCP connection: ns2.duckdns.org / 54.191.117.119: 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 54.191.117.119:53
XFatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org: 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 52.26.169.94:53
XFatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org / 52.26.169.94: 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 52.26.169.94:53
AGood: Nameserver supports Echo Capitalization: 3 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 3 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org / 54.187.92.222: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org / 54.191.117.119: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org / 52.26.169.94: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate
http://bearhugs.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 212.149.178.154
-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.
http://www.bearhugs.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 212.149.178.154
-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.
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: 206540 milliseconds, 206.540 seconds


7. Connections

No connection informations found. Perhaps only http - connections.


8. Certificates

No certificate informations found. Perhaps only http - connections.


9. Last Certificates - Certificate Transparency Log Check (BETA)

1. Source CertSpotter - active certificates

No CertSpotter - CT-Log entries found


2. Source crt.sh - old and new certificates, sometimes very slow.

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
0
3

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1200598771
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-02-13 16:41:20
2019-05-14 15:41:20
bearhugs.duckdns.org
1 entries


948041850
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-11-15 05:42:59
2019-02-13 05:42:59
bearhugs.duckdns.org
1 entries


946727443
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2018-11-14 19:07:50
2019-02-12 19:07:50
bearhugs.duckdns.org
1 entries



10. Html-Content - Entries (BETA - mixed content and other checks)

No Html-Content entries found. Only checked if https + status 200/401/403/404


11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.bearhugs.duckdns.org



1
0
bearhugs.duckdns.org



1
0
duckdns.org
0

no CAA entry found
1
0
org
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
bearhugs.duckdns.org

ok
1
0
www.bearhugs.duckdns.org

ok
1
0
_acme-challenge.bearhugs.duckdns.org

missing entry or wrong length
1
0
_acme-challenge.www.bearhugs.duckdns.org

missing entry or wrong length
1
0
_acme-challenge.bearhugs.duckdns.org.bearhugs.duckdns.org

perhaps wrong
1
0
_acme-challenge.www.bearhugs.duckdns.org.bearhugs.duckdns.org

perhaps wrong
1
0
_acme-challenge.www.bearhugs.duckdns.org.www.bearhugs.duckdns.org

perhaps wrong
1
0


13. Portchecks (BETA)

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.



Permalink: https://check-your-website.server-daten.de/?i=b6c0f5da-b9e8-4a58-9344-e82a99ca177e


Last Result: https://check-your-website.server-daten.de/?q=bearhugs.duckdns.org - 2019-05-15 14:18:29


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

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