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

...

skip EDNS-Check

skip Content-Check

check links

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

Checked:
15.05.2024 18:05:52

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
zlkrs.link	A		yes	1	0
	AAAA		yes
www.zlkrs.link		Name Error	yes	1	0
*.zlkrs.link	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 5613, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 13, KeyTag 16766, DigestType 2 and Digest QPEEUDXXukjSemZEKyxxyhWdIZdW061NNc8egEGSKLU=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner link., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 28.05.2024, 05:00:00 +, Signature-Inception: 15.05.2024, 04:00:00 +, KeyTag 5613, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 16766, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 13, KeyTag 59568, Flags 256


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner link., Algorithm: 13, 1 Labels, original TTL: 900 sec, Signature-expiration: 14.06.2024, 15:02:14 +, Signature-Inception: 15.05.2024, 15:02:14 +, KeyTag 16766, Signer-Name: link


	RRSIG-Owner link., Algorithm: 13, 1 Labels, original TTL: 900 sec, Signature-expiration: 14.06.2024, 15:02:14 +, Signature-Inception: 15.05.2024, 15:02:14 +, KeyTag 59568, Signer-Name: link


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 16766 used to validate the DNSKEY RRSet


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 59568 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 16766, DigestType 2 and Digest "QPEEUDXXukjSemZEKyxxyhWdIZdW061NNc8egEGSKLU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: zlkrs.link
zlkrs.link	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 "5agtr1tfc1pc8rek878bu3qlrhrjd3h2" between the hashed NSEC3-owner "5adqraj538fhvl2tv6qia9rlsrd68j12" and the hashed NextOwner "5ahu061jb1o2uu85a40i5r9shm3qtjd5". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 5adqraj538fhvl2tv6qia9rlsrd68j12.link., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 14.06.2024, 15:02:14 +, Signature-Inception: 15.05.2024, 15:02:14 +, KeyTag 59568, Signer-Name: link


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "9nos90sudpc503ec1bd8pem2ocmvhduk" as Owner. That's the Hash of "link" with the NextHashedOwnerName "9nu518hoc58uuh0tdvfskaqogbaukqi4". So that domain name is the Closest Encloser of "zlkrs.link". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 9nos90sudpc503ec1bd8pem2ocmvhduk.link., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 14.06.2024, 15:02:14 +, Signature-Inception: 15.05.2024, 15:02:14 +, KeyTag 59568, Signer-Name: link


	0 DNSKEY RR found




Zone: www.zlkrs.link
www.zlkrs.link	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.zlkrs.link	• carter.ns.cloudflare.com
zlkrs.link	• carter.ns.cloudflare.com / 67m58	108.162.193.80 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	172.64.33.80 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	173.245.59.80 San Francisco/California/United States (US) - Cloudflare, Inc.	•
	•	2606:4700:58::adf5:3b50 Montreal/Quebec/Canada (CA) - Cloudflare, Inc.	•
	•	2803:f800:50::6ca2:c150 San José/Provincia de San Jose/Costa Rica (CR) - Cloudflare, Inc.	•
	•	2a06:98c1:50::ac40:2150 London/England/United Kingdom (GB) - Cloudflare, Inc.	•
	• fay.ns.cloudflare.com / 67m62	108.162.192.115 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	172.64.32.115 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	173.245.58.115 San Francisco/California/United States (US) - Cloudflare, Inc.	•
	•	2606:4700:50::adf5:3a73 Montreal/Quebec/Canada (CA) - Cloudflare, Inc.	•
	•	2803:f800:50::6ca2:c073 San José/Provincia de San Jose/Costa Rica (CR) - Cloudflare, Inc.	•
	•	2a06:98c1:50::ac40:2073 London/England/United Kingdom (GB) - Cloudflare, Inc.	•
link	• ns.trs-dns.com
	• ns01.trs-dns.com / dns01.den1.tucowsregistry.net		•
	• ns01.trs-dns.info / FRA1		•
	• ns01.trs-dns.net / dns02.den1.tucowsregistry.net
	• ns01.trs-dns.org / CDG2		•

4. SOA-Entries

Domain:	link
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	link
Zone-Name:	link
Primary:	ns.trs-dns.com
Mail:	trs-ops.tucows.com
Serial:	1715788891
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	300
num Entries:	4

Domain:	zlkrs.link
Zone-Name:	zlkrs.link
Primary:	carter.ns.cloudflare.com
Mail:	dns.cloudflare.com
Serial:	2337188563
Refresh:	10000
Retry:	2400
Expire:	604800
TTL:	1800
num Entries:	12

Domain:	www.zlkrs.link
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

Domainname	Http-Status	redirect	Sec.	G
•

7. Comments

	1. General Results, most used to calculate the result
A	name "zlkrs.link" is domain, public suffix is ".link", top-level-domain is ".link", top-level-domain-type is "generic", tld-manager is "Uniregistry, Corp.", num .link-domains preloaded: 224 (complete: 244198)
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "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.
X	Fatal error: Nameserver doesn't support TCP connection: ns01.trs-dns.net: Timeout
B	No _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.zlkrs.link
	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	Info:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: carter.ns.cloudflare.com, fay.ns.cloudflare.com, 2 Name Servers included in Delegation: carter.ns.cloudflare.com, fay.ns.cloudflare.com, 2 Name Servers included in 1 Zone definitions: carter.ns.cloudflare.com, fay.ns.cloudflare.com, 1 Name Servers listed in SOA.Primary: carter.ns.cloudflare.com.
A	Good: Only one SOA.Primary Name Server found.: carter.ns.cloudflare.com.
A	Good: SOA.Primary Name Server included in the delegation set.: carter.ns.cloudflare.com.
A	Good: 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: carter.ns.cloudflare.com, fay.ns.cloudflare.com
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
	Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: com
	Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: cloudflare.com
A	Good: Name servers with different Country locations found: 2 Name Servers, 4 Countries: CA, CR, GB, US
A	Info: Ipv4-Subnet-list: 6 Name Servers, 3 different subnets (first Byte): 108., 172., 173., 3 different subnets (first two Bytes): 108.162., 172.64., 173.245., 6 different subnets (first three Bytes): 108.162.192., 108.162.193., 172.64.32., 172.64.33., 173.245.58., 173.245.59.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 6 Name Servers with IPv6, 3 different subnets (first block): 2606:, 2803:, 2a06:, 3 different subnets (first two blocks): 2606:4700:, 2803:f800:, 2a06:98c1:, 4 different subnets (first three blocks): 2606:4700:0050:, 2606:4700:0058:, 2803:f800:0050:, 2a06:98c1:0050:, 4 different subnets (first four blocks): 2606:4700:0050:0000:, 2606:4700:0058:0000:, 2803:f800:0050:0000:, 2a06:98c1:0050:0000:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 12 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 12 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 12 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: carter.ns.cloudflare.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: ns.trs-dns.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.
A	Good: 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
A	Good: 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
A	Duration: 53563 milliseconds, 53.563 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)

Issuer				last 7 days	active	num Certs
CN=E1, O=Let's Encrypt, C=US				0	0	1
CN=GTS CA 1P5, O=Google Trust Services LLC, C=US				0	0	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
7025586072 leaf cert	CN=E1, O=Let's Encrypt, C=US	2024-03-29 08:00:42	2024-06-27 08:00:41	*.zlkrs.link, zlkrs.link - 2 entries
6958372068 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2024-03-18 16:58:52	2024-06-16 16:58:51	*.zlkrs.link, zlkrs.link - 2 entries

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

Issuer				last 7 days	active	num Certs
CN=GTS CA 1P5, O=Google Trust Services LLC, C=US				0	0	4
CN=E1, O=Let's Encrypt, C=US				0	0	3

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
12585010746 leaf cert	CN=E1, O=Let's Encrypt, C=US	2024-03-29 07:00:42	2024-06-27 06:00:41	*.zlkrs.link, zlkrs.link 2 entries
12427100578 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2024-03-18 15:58:52	2024-06-16 14:58:51	*.zlkrs.link, zlkrs.link 2 entries
11914863163 leaf cert	CN=E1, O=Let's Encrypt, C=US	2024-01-30 05:39:01	2024-04-29 04:39:00	*.zlkrs.link, zlkrs.link 2 entries
11801263603 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2024-01-19 16:22:13	2024-04-18 15:22:12	*.zlkrs.link, zlkrs.link 2 entries
11314416311 leaf cert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2023-11-21 16:38:29	2024-02-19 16:38:28	*.zlkrs.link, zlkrs.link 2 entries
11176800506 leaf cert	CN=E1, O=Let's Encrypt, C=US	2023-11-21 16:37:11	2024-02-19 16:37:10	*.zlkrs.link, zlkrs.link 2 entries
11171565161 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2023-11-21 16:36:09	2024-02-19 16:36:08	*.zlkrs.link, zlkrs.link 2 entries

11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404

12. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: carter.ns.cloudflare.com, fay.ns.cloudflare.com

QNr.	Domain	Type	NS used
1	com	NS	b.root-servers.net (2001:500:200::b)
	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	carter.ns.cloudflare.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
	Answer: ns7.cloudflare.com 162.159.4.8
	Answer: ns6.cloudflare.com 162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506
	Answer: ns5.cloudflare.com 162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937
	Answer: ns4.cloudflare.com 162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837
	Answer: ns3.cloudflare.com 162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2
3	fay.ns.cloudflare.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
	Answer: ns7.cloudflare.com 162.159.4.8
	Answer: ns6.cloudflare.com 162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506
	Answer: ns5.cloudflare.com 162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937
	Answer: ns4.cloudflare.com 162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837
	Answer: ns3.cloudflare.com 162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2
4	carter.ns.cloudflare.com: 108.162.193.80, 172.64.33.80, 173.245.59.80	A	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
5	carter.ns.cloudflare.com: 2606:4700:58::adf5:3b50, 2803:f800:50::6ca2:c150, 2a06:98c1:50::ac40:2150	AAAA	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
6	fay.ns.cloudflare.com: 108.162.192.115, 172.64.32.115, 173.245.58.115	A	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
7	fay.ns.cloudflare.com: 2606:4700:50::adf5:3a73, 2803:f800:50::6ca2:c073, 2a06:98c1:50::ac40:2073	AAAA	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)

14. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
zlkrs.link	0		no CAA entry found	1	0
link	0		no CAA entry found	1	0

15. TXT - Entries

Domainname	Status	∑ Queries
zlkrs.link	ok	1
_acme-challenge.zlkrs.link	Name Error - The domain name does not exist	1
_acme-challenge.zlkrs.link.zlkrs.link	Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No Ciphers found

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

Permalink: https://check-your-website.server-daten.de/?i=fab1e97e-508f-48d4-a0a0-9120213d980b

Last Result: https://check-your-website.server-daten.de/?q=zlkrs.link - 2024-05-15 18:05:52

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

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

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

QR-Code of this page - https://check-your-website.server-daten.de/?d=zlkrs.link