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



X

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

Checked:
02.12.2019 21:05:22


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
tuftuf.asuscomm.com
A
86.86.205.67
Zuidland/South Holland/Netherlands (NL) - KPN N.V.
Hostname: ip5656cd43.adsl-surfen.hetnet.nl
yes
1
0

AAAA

yes


www.tuftuf.asuscomm.com

Refused
yes
1
0


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.12.2019, 00:00:00 +, Signature-Inception: 30.11.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: com
com
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.12.2019, 17:00:00 +, Signature-Inception: 02.12.2019, 16: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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 12163, Flags 256



Public Key with Algorithm 8, KeyTag 17708, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.12.2019, 19:24:21 +, Signature-Inception: 27.11.2019, 19:19:21 +, KeyTag 30909, Signer-Name: com



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.12.2019, 19:24:21 +, Signature-Inception: 27.11.2019, 19:19:21 +, KeyTag 30909, Signer-Name: com



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



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



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

Zone: asuscomm.com
asuscomm.com
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 "tn98g8kvdilk2bbue703nl9u8ihd3fui" between the hashed NSEC3-owner "tn989f816gkg771vad8pm3ckqhos4vct" and the hashed NextOwner "tn9909t8n02f0kg2ntti6okmhcfhsmvf". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner tn989f816gkg771vad8pm3ckqhos4vct.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 06.12.2019, 06:41:14 +, Signature-Inception: 29.11.2019, 05:31:14 +, KeyTag 12163, Signer-Name: com



0 DNSKEY RR found




Zone: tuftuf.asuscomm.com
tuftuf.asuscomm.com
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.tuftuf.asuscomm.com
www.tuftuf.asuscomm.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.tuftuf.asuscomm.com
 

tuftuf.asuscomm.com
  ns1.asuscomm.com
103.10.4.108
Fenjihu/Taiwan/Taiwan (TW) - ASUS

asuscomm.com
U  ns1.asuscomm.com

com
  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:com
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1575317103
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:7


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


Domain:asuscomm.com
Zone-Name:
Primary:ns1.asuscomm.com
Mail:chris1_wang.asuscomm.com
Serial:42
Refresh:28800
Retry:7200
Expire:604800
TTL:30
num Entries:1


Domain:tuftuf.asuscomm.com
Zone-Name:
Primary:ns1.asuscomm.com
Mail:chris1_wang.asuscomm.com
Serial:42
Refresh:28800
Retry:7200
Expire:604800
TTL:30
num Entries:1


Domain:www.tuftuf.asuscomm.com
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://tuftuf.asuscomm.com/
86.86.205.67
-14

10.033
T
Timeout - The operation has timed out

• https://tuftuf.asuscomm.com/
86.86.205.67
-14

10.043
T
Timeout - The operation has timed out

• http://tuftuf.asuscomm.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
86.86.205.67
-14

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

7. Comments


1. General Results, most used to calculate the result

Aname "tuftuf.asuscomm.com" is subdomain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
Agood: All ip addresses are public addresses
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.asuscomm.com: 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 103.10.4.108:53
XFatal error: Nameserver doesn't support TCP connection: ns1.asuscomm.com / 103.10.4.108: Timeout

2. DNS- and NameServer - Checks

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

Nameserver doesn't pass all EDNS-Checks: ns1.asuscomm.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.
Nameserver doesn't pass all EDNS-Checks: ns1.asuscomm.com / 103.10.4.108: 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://tuftuf.asuscomm.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 86.86.205.67
-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: 146180 milliseconds, 146.180 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
3

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
3104495396
leaf cert
CN=Amazon, OU=Server CA 1B, O=Amazon, C=US
2020-07-08 22:00:00
2021-08-08 10:00:00
*.asuscomm.com
1 entries


1862996283
leaf cert
CN=Amazon, OU=Server CA 1B, O=Amazon, C=US
2019-05-19 22:00:00
2020-06-20 10:00:00
*.asuscomm.com
1 entries


1573835390
leaf cert
CN=Amazon, OU=Server CA 1B, O=Amazon, C=US
2019-05-19 22:00:00
2020-06-20 10:00:00
*.asuscomm.com
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
tuftuf.asuscomm.com
0

no CAA entry found
1
0
asuscomm.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
asuscomm.com

ok
1
0
tuftuf.asuscomm.com

ok
1
0
_acme-challenge.tuftuf.asuscomm.com

Name Error - The domain name does not exist
1
0
_acme-challenge.tuftuf.asuscomm.com.asuscomm.com

Refused - The name server refuses to perform the specified operation for policy reasons
1
0
_acme-challenge.tuftuf.asuscomm.com.tuftuf.asuscomm.com

Refused - The name server refuses to perform the specified operation for policy reasons
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=b3175b63-e481-4f8a-9da5-d9444c240d93


Last Result: https://check-your-website.server-daten.de/?q=tuftuf.asuscomm.com - 2019-12-02 21:05:22


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

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