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




X

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

Checked:
14.01.2020 00:24:06


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
snelexample.site


yes
2
0
www.snelexample.site


yes
2
0


2. DNSSEC

Zone (*)DNSSEC - Informations (some minor bugs wildcard + nsec/nsec3)

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 33853, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



1 RRSIG RR to validate DS RR found



RRSIG-Owner site., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.01.2020, 17:00:00 +, Signature-Inception: 13.01.2020, 16:00:00 +, KeyTag 33853, Signer-Name: (root)



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



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 51718, Flags 256



Public Key with Algorithm 8, KeyTag 61735, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner site., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 04.02.2020, 18:30:40 +, Signature-Inception: 05.01.2020, 08:16:24 +, KeyTag 51676, Signer-Name: site



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 51676, DigestType 1 and Digest "kN2+7rlzsPhxntdj+27t6Xxzq/U=" 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 8, KeyTag 51676, DigestType 2 and Digest "iDF19vXGjqgVY7YtGyt5tqmX1g3G4gzHCv0M1rfoL2I=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: snelexample.site
snelexample.site
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 "s8uqkvh0flqhjs4h5mjkmer1pn5n4t0v" between the hashed NSEC3-owner "s8u0j9re27blrbci287f89odfs3bpvtn" and the hashed NextOwner "s92i8aonkdi2i152ht9c7umaqhcdt09g". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner s8u0j9re27blrbci287f89odfs3bpvtn.site., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 28.01.2020, 09:01:33 +, Signature-Inception: 29.12.2019, 13:03:26 +, KeyTag 51718, Signer-Name: site



0 DNSKEY RR found




Zone: www.snelexample.site
www.snelexample.site
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.snelexample.site
 

snelexample.site
  ns1.snelexample.site


  ns2.snelexample.site

site
  a.nic.site / NRDT-75SODK-AB8TIQ


  b.nic.site / FMCL-UEZCAO-YJSSPL


  c.nic.site / hivecast-23-cator.as15135.net Radix-C


  d.nic.site / hivecast-2-defra.as15135.net Radix-D


4. SOA-Entries


Domain:site
Zone-Name:
Primary:ns0.centralnic.net
Mail:hostmaster.centralnic.net
Serial:266580
Refresh:900
Retry:1800
Expire:6048000
TTL:3600
num Entries:4


Domain:snelexample.site
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:2


Domain:www.snelexample.site
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 "snelexample.site" is domain, public suffix is "site", top-level-domain-type is "generic", tld-manager is "DotSite Inc."
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.

2. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver

Nameserver doesn't pass all EDNS-Checks: ns1.snelexample.site: 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: ns2.snelexample.site: 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

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: 407786 milliseconds, 407.786 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:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
snelexample.site



2
0
site
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
snelexample.site


2
0
_acme-challenge.snelexample.site


2
0
_acme-challenge.snelexample.site.snelexample.site


2
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=6e9e2260-b39e-4adf-a862-081707f527f9


Last Result: https://check-your-website.server-daten.de/?q=snelexample.site - 2020-01-14 00:24:06


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

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