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



X

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

Checked:
16.09.2020 06:35:31


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
xx.dijizen.com

Name Error
yes
1
0
www.xx.dijizen.com

Name Error
yes
1
0
*.dijizen.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.xx.dijizen.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 46594, 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.2020, 00:00:00 +, Signature-Inception: 09.09.2020, 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



DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 28.09.2020, 21:00:00 +, Signature-Inception: 15.09.2020, 20:00:00 +, KeyTag 46594, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 24966, 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: 27.09.2020, 18:24:21 +, Signature-Inception: 12.09.2020, 18:19:21 +, KeyTag 30909, Signer-Name: com



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: dijizen.com
dijizen.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 "g6sv6rf4nh3m4qudmh8bidsaope34vj9" between the hashed NSEC3-owner "g6sv1arpkhckq7ko78kdsobgqpni406q" and the hashed NextOwner "g6t1r7gl617nlf2ud2haqomavlv7g3rf". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner g6sv1arpkhckq7ko78kdsobgqpni406q.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 21.09.2020, 04:50:10 +, Signature-Inception: 14.09.2020, 03:40:10 +, KeyTag 24966, Signer-Name: com



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q1gin43n1arrc9osm6qpqr81h5m9a". So that domain name is the Closest Encloser of "dijizen.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 22.09.2020, 04:41:59 +, Signature-Inception: 15.09.2020, 03:31:59 +, KeyTag 24966, Signer-Name: com



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 30765, Flags 256



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



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



3 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner dijizen.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 16.10.2020, 04:27:37 +, Signature-Inception: 16.09.2020, 03:27:37 +, KeyTag 30765, Signer-Name: dijizen.com



RRSIG-Owner dijizen.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 16.10.2020, 04:27:37 +, Signature-Inception: 16.09.2020, 03:27:37 +, KeyTag 41527, Signer-Name: dijizen.com



RRSIG-Owner dijizen.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 16.10.2020, 04:27:37 +, Signature-Inception: 16.09.2020, 03:27:37 +, KeyTag 47746, Signer-Name: dijizen.com



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



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



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



Error: DNSKEY 30765 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.



Error: DNSKEY 41527 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.



Error: DNSKEY 47746 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.

Zone: xx.dijizen.com
xx.dijizen.com
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 "dijizen.com" and the NextOwner "_dmarc.dijizen.com". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, NSEC, DNSKEY



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

Zone: www.xx.dijizen.com
www.xx.dijizen.com
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 "dijizen.com" and the NextOwner "_dmarc.dijizen.com". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, NSEC, DNSKEY



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


3. Name Servers

DomainNameserverNS-IP
www.xx.dijizen.com
  ns2.dijizen.com

xx.dijizen.com
  ns2.dijizen.com

dijizen.com
  ns1.dijizen.com
185.162.147.53
Bursa/Turkey (TR) - Bursabil Teknoloji A.S.


  ns2.dijizen.com
185.162.147.53
Bursa/Turkey (TR) - Bursabil Teknoloji A.S.

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


Domain:dijizen.com
Zone-Name:dijizen.com
Primary:ns2.dijizen.com
Mail:receptalhacolak.gmail.com
Serial:2020090206
Refresh:10800
Retry:3600
Expire:604800
TTL:10800
num Entries:2


Domain:xx.dijizen.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.xx.dijizen.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







7. Comments


1. General Results, most used to calculate the result

Aname "xx.dijizen.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 52208 (complete: 131120)
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.

2. DNS- and NameServer - Checks

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.dijizen.com (185.162.147.53), ns2.dijizen.com (185.162.147.53)
AGood (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns1.dijizen.com, ns2.dijizen.com, 2 Name Servers included in Delegation: ns1.dijizen.com, ns2.dijizen.com, 2 Name Servers included in 1 Zone definitions: ns1.dijizen.com, ns2.dijizen.com, 1 Name Servers listed in SOA.Primary: ns2.dijizen.com.
AGood: Only one SOA.Primary Name Server found.: ns2.dijizen.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns2.dijizen.com.
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 185., 1 different subnets (first two Bytes): 185.162., 1 different subnets (first three Bytes): 185.162.147.
XFatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.:
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 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

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: 17560 milliseconds, 17.560 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

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: ns1.dijizen.com, ns2.dijizen.com

QNr.DomainTypeNS used
1
com
NS
a.root-servers.net (2001:503:ba3e::2:30)

Answer: 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
2
ns1.dijizen.com: 185.162.147.53
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: ns2.dijizen.com
185.162.147.53


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
dijizen.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
dijizen.com
v=spf1 redirect=_spf.yandex.net
ok
1
0
_acme-challenge.xx.dijizen.com.dijizen.com

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=8e5557ef-1e8f-462f-8898-f81351eba2f9


Last Result: https://check-your-website.server-daten.de/?q=xx.dijizen.com - 2020-09-16 06:35:31


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

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