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




X

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

Checked:
02.04.2024 22:20:09


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
zubi.cu

Refused
yes
1
0
www.zubi.cu

Refused
yes
1
0


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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 5613, Flags 256



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



Public Key with Algorithm 8, KeyTag 30903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "cu" and the NextOwner "cuisinella". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: NS, RRSIG, NSEC



0 DNSKEY RR found




Zone: zubi.cu
zubi.cu
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.zubi.cu
www.zubi.cu
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
zubi.cu
  ns3.etecsa.net
200.55.128.10
Havana/Cuba (CU) - Empresa de Telecomunicaciones de Cuba, S.A.


  ns4.etecsa.net
200.55.128.11
Havana/Cuba (CU) - Empresa de Telecomunicaciones de Cuba, S.A.


  ns5.etecsa.net
181.225.231.195
Alamar/Havana/Cuba (CU) - Empresa de Telecomunicaciones de Cuba, S.A.

cu
  cu.cctld.authdns.ripe.net / ns3.se-sto.authdns.ripe.net


  ns.ceniai.net.cu


  ns.dns.br / ns.dns.br


  ns2.ceniai.net.cu


  ns2.gip.net


  rip.psg.com / rip.psg.com


4. SOA-Entries


Domain:cu
Zone-Name:cu
Primary:ns.ceniai.net.cu
Mail:cu-tech.ceniai.inf.cu
Serial:2024040104
Refresh:3600
Retry:1800
Expire:1209600
TTL:3600
num Entries:2


Domain:cu
Zone-Name:cu
Primary:ns.ceniai.net.cu
Mail:cu-tech.ceniai.inf.cu
Serial:2024040200
Refresh:3600
Retry:1800
Expire:1209600
TTL:3600
num Entries:4


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


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 "zubi.cu" is domain, public suffix is ".cu", top-level-domain is ".cu", top-level-domain-type is "country-code", Country is Cuba, tld-manager is "CENIAInternet Industria y San Jose Capitolio Nacional", num .cu-domains preloaded: 2 (complete: 240622)
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: ns.ceniai.net.cu: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns2.ceniai.net.cu: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns3.etecsa.net / 200.55.128.10: Refused
XFatal error: Nameserver doesn't support TCP connection: ns4.etecsa.net / 200.55.128.11: Refused
XFatal error: Nameserver doesn't support TCP connection: ns5.etecsa.net / 181.225.231.195: Refused
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.zubi.cu

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

A
A
AInfo:: 6 different Name Servers found: cu.cctld.authdns.ripe.net, ns.ceniai.net.cu, ns.dns.br, ns2.ceniai.net.cu, ns2.gip.net, rip.psg.com, 6 Name Servers included in Delegation: cu.cctld.authdns.ripe.net, ns.ceniai.net.cu, ns.dns.br, ns2.ceniai.net.cu, ns2.gip.net, rip.psg.com, 6 Name Servers included in 1 Zone definitions: cu.cctld.authdns.ripe.net, ns.ceniai.net.cu, ns.dns.br, ns2.ceniai.net.cu, ns2.gip.net, rip.psg.com, 1 Name Servers listed in SOA.Primary: ns.ceniai.net.cu.
AGood: Only one SOA.Primary Name Server found.: ns.ceniai.net.cu.
AGood: SOA.Primary Name Server included in the delegation set.: ns.ceniai.net.cu.
AGood: All Name Server Domain Names have a Public Suffix.
A
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: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns3.etecsa.net / 200.55.128.10: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns4.etecsa.net / 200.55.128.11: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns5.etecsa.net / 181.225.231.195: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
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.

4. 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: 196956 milliseconds, 196.956 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" > of the last months 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:


No NameServer - IP address - Informations found


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
zubi.cu
-5

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

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
zubi.cu

Refused - The name server refuses to perform the specified operation for policy reasons
1
0
_acme-challenge.zubi.cu

Refused - The name server refuses to perform the specified operation for policy reasons
1
0
_acme-challenge.zubi.cu.zubi.cu

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


15. DomainService - Entries

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=6c619f90-b206-4e2c-a13c-831e0545bdd0


Last Result: https://check-your-website.server-daten.de/?q=zubi.cu - 2024-04-02 22:20:09


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

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

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