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




X

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

Checked:
07.11.2019 16:30:54


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
burhome.duckdns.org
A
176.105.38.121
Kyiv/Kyiv City/Ukraine (UA) - Bilink
No Hostname found
yes
1
0

AAAA

yes


www.burhome.duckdns.org
A
176.105.38.121
Kyiv/Kyiv City/Ukraine (UA) - Bilink
No Hostname found
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 22545, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.11.2019, 00:00:00 +, Signature-Inception: 31.10.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: org
org
2 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 20.11.2019, 05:00:00 +, Signature-Inception: 07.11.2019, 04:00:00 +, KeyTag 22545, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 22545 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 11324, Flags 256



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



Public Key with Algorithm 7, KeyTag 36752, Flags 256



3 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.11.2019, 15:23:40 +, Signature-Inception: 01.11.2019, 14:23:40 +, KeyTag 9795, Signer-Name: org



RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.11.2019, 15:23:40 +, Signature-Inception: 01.11.2019, 14:23:40 +, KeyTag 11324, Signer-Name: org



RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.11.2019, 15:23:40 +, Signature-Inception: 01.11.2019, 14:23:40 +, 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 11324 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

Zone: duckdns.org
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 query name "mnorhcks4b6fjob5ap1mrs7utmhf26bm" between the hashed NSEC3-owner "mnoq314vn5m775pq7osblqq7jdr6o56r" and the hashed NextOwner "mnpis27oa7d3n2t47lo6516sp4um1am4". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner mnoq314vn5m775pq7osblqq7jdr6o56r.org., Algorithm: 7, 2 Labels, original TTL: 86400 sec, Signature-expiration: 22.11.2019, 15:23:40 +, Signature-Inception: 01.11.2019, 14:23:40 +, KeyTag 11324, Signer-Name: org



0 DNSKEY RR found




Zone: burhome.duckdns.org
burhome.duckdns.org
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.burhome.duckdns.org
www.burhome.duckdns.org
0 DS RR in the parent zone found


3. Name Servers

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


U  ns2.duckdns.org


U  ns3.duckdns.org

burhome.duckdns.org
U  ns1.duckdns.org
54.187.92.222
Portland/Oregon/United States (US) - Amazon Technologies Inc.


U  ns2.duckdns.org
54.191.117.119
Portland/Oregon/United States (US) - Amazon Technologies Inc.


U  ns3.duckdns.org
52.26.169.94
Portland/Oregon/United States (US) - Amazon.com, Inc.

duckdns.org
U  ns1.duckdns.org


U  ns2.duckdns.org


U  ns3.duckdns.org

org
  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


4. SOA-Entries


Domain:org
Zone-Name:
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2013694931
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:1


Domain:org
Zone-Name:
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2013694932
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:5


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


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


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


Domain:burhome.duckdns.org
Zone-Name:
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:burhome.duckdns.org
Zone-Name:
Primary:ns2.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:burhome.duckdns.org
Zone-Name:
Primary:ns3.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:www.burhome.duckdns.org
Zone-Name:
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:www.burhome.duckdns.org
Zone-Name:
Primary:ns2.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:www.burhome.duckdns.org
Zone-Name:
Primary:ns3.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://burhome.duckdns.org/
176.105.38.121
-14

10.050
T
Timeout - The operation has timed out

• http://www.burhome.duckdns.org/
176.105.38.121
-14

10.043
T
Timeout - The operation has timed out

• https://burhome.duckdns.org/
176.105.38.121 No GZip used - 1577 / 3086 - 51.10 % possible
200

Html is minified: 176.54 %
3.687
A
Server: nginx/1.16.1
Date: Thu, 07 Nov 2019 15:33:15 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 3086
Connection: close
Strict-Transport-Security: max-age=31536000; includeSubDomains

• https://www.burhome.duckdns.org/
176.105.38.121
-8

0.373
W
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.

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

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

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

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

7. Comments


1. General Results, most used to calculate the result

Aname "burhome.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
Agood: destination is https
Agood - only one version with Http-Status 200
Agood: one preferred version: non-www is preferred
Agood: every https has a Strict Transport Security Header
Agood: HSTS max-age is long enough, 31536000 seconds = 365 days
Agood: HSTS has includeSubdomains - directive
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
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. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 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. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 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. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 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. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 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. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 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. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 52.26.169.94:53

2. DNS- and NameServer - Checks

AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns1.duckdns.org,ns2.duckdns.org,ns3.duckdns.org
AGood: Nameserver supports Echo Capitalization: 3 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 3 good Nameserver
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://burhome.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.105.38.121
-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.
http://www.burhome.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.105.38.121
-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.
https://burhome.duckdns.org/ 176.105.38.121
200

Warning: https result with status 200 and size greater then 1024 Bytes without GZip found. Add GZip support so the html content is compressed.
https://burhome.duckdns.org/ 176.105.38.121
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
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: 173897 milliseconds, 173.897 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
burhome.duckdns.org
176.105.38.121
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
burhome.duckdns.org
176.105.38.121
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
http/2 via ALPN supported 
no Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain (complete)
1CN=burhome.duckdns.org

2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


9. Certificates

1.
1.
CN=burhome.duckdns.org
22.10.2019
20.01.2020
173 days expired
burhome.duckdns.org - 1 entry
1.
1.
CN=burhome.duckdns.org
22.10.2019

20.01.2020
173 days expired
burhome.duckdns.org - 1 entry

KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:04F60A954C14D2D8200567BB95DC7C1D1A17
Thumbprint:FC1ADFDBD439B5E977191B3CFC8E8EDE577ABB78
SHA256 / Certificate:k2P1jsHzDmeiAsKqXscOoOeCSgh7ffuKAWv/FB0ypFo=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):97c11105fac14c51e82c52fc13fd320382201935cef16bb05717b76ff57ee5a6
SHA256 hex / Subject Public Key Information (SPKI):37a84f8a46ad54c82ae6f8e000a11a12b60a41e99ee82194ca4236fe11c29f00
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
expires in 249 days


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
expires in 249 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):cbb93d32de628874a3ecfb92affadc97f1b795f84cc6f24221a089dee1aa25ad
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
expires in 446 days


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
expires in 446 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):29cc40db5e2de462a311cbbafaa1dc466960002335ecdf3317f2cd05c1d0bedf
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:



10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

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

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1199686011
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-10-22 15:20:34
2020-01-20 15:20:34
burhome.duckdns.org - 1 entries



2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 are listed

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

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2026264941
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-10-22 13:20:34
2020-01-20 14:20:34
burhome.duckdns.org
1 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.burhome.duckdns.org



1
0
burhome.duckdns.org



1
0
duckdns.org
0

no CAA entry found
1
0
org
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
burhome.duckdns.org

ok
1
0
www.burhome.duckdns.org

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

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

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

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

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

perhaps wrong
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=0942370e-aeaf-44d0-9f9c-31f31bf44e99


Last Result: https://check-your-website.server-daten.de/?q=burhome.duckdns.org - 2019-11-07 16:46:18


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

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