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:
31.08.2026 23:35:18

Older results

X - 31.08.2026 23:34:14

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
lab1.site	A		yes	2	0
	AAAA		yes
www.lab1.site	CNAME	lab1.site	yes	1	0
*.lab1.site	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


	3 DNSKEY RR found


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


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


	Public Key with Algorithm 8, KeyTag 57780, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 13, KeyTag 31826, DigestType 2 and Digest 4FThCwA2oPRJzDp9U5qRnvnxjJ8layu1FSbPb9fTO2s=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner site., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 13.09.2026, 21:00:00 +, Signature-Inception: 31.08.2026, 20:00:00 +, KeyTag 57780, Signer-Name: (root)


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 13, KeyTag 40708, Flags 256


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner site., Algorithm: 13, 1 Labels, original TTL: 300 sec, Signature-expiration: 10.09.2026, 06:52:33 +, Signature-Inception: 11.08.2026, 11:34:16 +, KeyTag 31826, Signer-Name: site


	RRSIG-Owner site., Algorithm: 13, 1 Labels, original TTL: 300 sec, Signature-expiration: 08.09.2026, 17:14:23 +, Signature-Inception: 11.08.2026, 10:44:18 +, KeyTag 40708, Signer-Name: site


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


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


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

Zone: lab1.site
lab1.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 "17mjbtv4v3chnducu5tt6mm51c5cjmg4" between the hashed NSEC3-owner "17m576stj2cgqagfv65kmrbs6gpjjqlt" and the hashed NextOwner "17o5d362hr9pglg9mh95qde10l0g6ir2". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 17m576stj2cgqagfv65kmrbs6gpjjqlt.site., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 28.09.2026, 18:12:05 +, Signature-Inception: 30.08.2026, 23:24:21 +, KeyTag 40708, Signer-Name: site


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "kkkldpnn5k2662ei72hm1tvtee3uakea" as Owner. That's the Hash of "site" with the NextHashedOwnerName "kkknhb2f66ri3j98ko8fc72t7mfcpnv1". So that domain name is the Closest Encloser of "lab1.site". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner kkkldpnn5k2662ei72hm1tvtee3uakea.site., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 25.09.2026, 02:48:39 +, Signature-Inception: 27.08.2026, 10:34:19 +, KeyTag 40708, Signer-Name: site


	0 DNSKEY RR found




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

3. Name Servers

Domain	Nameserver	NS-IP
lab1.site	• dns1.registrar-servers.com / Auth_NC_Host2.Frankfurt_Node1	156.154.132.200 Lehi/Utah/United States (US) - Vercara, LLC	•
	•	2610:a1:1024::200 New York/United States (US) - Vercara, LLC	•
	• dns2.registrar-servers.com / Auth_NC_Host2.Frankfurt_Node1	156.154.133.200 Lehi/Utah/United States (US) - Vercara, LLC	•
	•	2610:a1:1025::200 Lehi/Utah/United States (US) - Vercara, LLC	•
site	• ns.trs-dns.com
	• ns01.trs-dns.com / fra02.dns1		•
	• ns01.trs-dns.net / fra01.dns2		•
	• ns10.trs-dns.info / 1.fra.pch		•
	• ns10.trs-dns.org / 2.fra.pch		•

4. SOA-Entries

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

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

Domain:	lab1.site
Zone-Name:	lab1.site
Primary:	dns1.registrar-servers.com
Mail:	hostmaster.registrar-servers.com
Serial:	1788209463
Refresh:	43200
Retry:	3600
Expire:	604800
TTL:	3601
num Entries:	4

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 "lab1.site" is domain, public suffix is ".site", top-level-domain is ".site", top-level-domain-type is "generic", tld-manager is "DotSite Inc.", num .site-domains preloaded: 353 (complete: 276475)
A	Good: All ip addresses are public addresses
A	Good: 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.
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.lab1.site
	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:: 24 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 24 Queries complete, 24 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Bad (greater 8):: An average of 12.0 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in Delegation: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in 1 Zone definitions: dns1.registrar-servers.com, dns2.registrar-servers.com, 1 Name Servers listed in SOA.Primary: dns1.registrar-servers.com.
A	Good: Only one SOA.Primary Name Server found.: dns1.registrar-servers.com.
A	Good: SOA.Primary Name Server included in the delegation set.: dns1.registrar-servers.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: dns1.registrar-servers.com, dns2.registrar-servers.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
A	Good: All name servers have ipv4- and ipv6-addresses.: 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: registrar-servers.com
	Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
A	Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 156., 1 different subnets (first two Bytes): 156.154., 2 different subnets (first three Bytes): 156.154.132., 156.154.133.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2610:, 1 different subnets (first two blocks): 2610:00a1:, 2 different subnets (first three blocks): 2610:00a1:1024:, 2610:00a1:1025:, 2 different subnets (first four blocks): 2610:00a1:1024:0000:, 2610:00a1:1025:0000:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 4 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 4 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
	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: 25950 milliseconds, 25.950 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. Html-Parsing via https://validator.w3.org/nu/

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: dns1.registrar-servers.com, dns2.registrar-servers.com

QNr.	Domain	Type	NS 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	dns1.registrar-servers.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: edns3.registrar-servers.com, edns4.registrar-servers.com, edns4.ultradns.biz, edns4.ultradns.com, edns4.ultradns.net, edns4.ultradns.org
	Answer: edns3.registrar-servers.com 193.108.91.149, 2.16.130.65, 2600:1401:2::95, 2600:1480:9800::41, 2a02:26f0:67::43, 95.100.175.67
	Answer: edns4.registrar-servers.com 2.22.230.67, 23.211.132.64, 2600:1406:1b::40, 2600:1408:1c::40, 2600:1480:800::43, 96.7.49.64
	Answer: edns4.ultradns.com 2001:502:f3ff::204, 204.74.66.4
3	dns2.registrar-servers.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: edns3.registrar-servers.com, edns4.registrar-servers.com, edns4.ultradns.biz, edns4.ultradns.com, edns4.ultradns.net, edns4.ultradns.org
	Answer: edns3.registrar-servers.com 193.108.91.149, 2.16.130.65, 2600:1401:2::95, 2600:1480:9800::41, 2a02:26f0:67::43, 95.100.175.67
	Answer: edns4.registrar-servers.com 2.22.230.67, 23.211.132.64, 2600:1406:1b::40, 2600:1408:1c::40, 2600:1480:800::43, 96.7.49.64
	Answer: edns4.ultradns.com 2001:502:f3ff::204, 204.74.66.4
4	biz	NS	k.root-servers.net (2001:7fd::1)
	Answer: a.gtld.biz, b.gtld.biz, c.gtld.biz, m.gtld.biz, n.gtld.biz, w.gtld.biz, x.gtld.biz, y.gtld.biz
5	edns4.ultradns.biz	NS	a.gtld.biz (2001:502:ad09::30)
	Answer: pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org
	Answer: pdns196.ultradns.biz 156.154.66.196, 2610:a1:1015::e8
6	net	NS	e.root-servers.net (2001:500:a8::e)
	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
7	edns4.ultradns.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns61.ultradns2.com, ns61.ultradns2.org, pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org
	Answer: pdns196.ultradns.net 156.154.65.196, 2610:a1:1014::e8
8	org	NS	k.root-servers.net (2001:7fd::1)
	Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
9	edns4.ultradns.org	NS	a0.org.afilias-nst.info (2001:500:e::1)
	Answer: ns61.ultradns2.com, ns61.ultradns2.org, pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org
	Answer: ns61.ultradns2.org 204.74.106.61, 2610:a1:323d::53
	Answer: pdns196.ultradns.org 156.154.67.196, 2001:502:4612::e8
10	uk	NS	b.root-servers.net (2001:500:200::b)
	Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
11	pdns196.ultradns.co.uk: 156.154.69.196, 2610:a1:1017::e8	NS	dns1.nic.uk (2a01:618:400::1)
12	pdns196.ultradns.com: 156.154.64.196, 2001:502:f3ff::e8	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns61.ultradns2.com 204.74.104.61, 2610:a1:313d::53
13	info	NS	k.root-servers.net (2001:7fd::1)
	Answer: a0.info.afilias-nst.info, a2.info.afilias-nst.info, b0.info.afilias-nst.org, b2.info.afilias-nst.org, c0.info.afilias-nst.info, d0.info.afilias-nst.org
14	pdns196.ultradns.info: 156.154.68.196, 2610:a1:1016::e8	NS	a0.info.afilias-nst.info (2001:500:19::1)
15	edns4.ultradns.biz: 204.74.67.4	A	pdns196.ultradns.biz (2610:a1:1015::e8)
16	edns4.ultradns.biz: 2610:a1:1015::204	AAAA	pdns196.ultradns.biz (2610:a1:1015::e8)
17	edns4.ultradns.net: 204.74.110.4	A	ns61.ultradns2.com (2610:a1:313d::53)
18	edns4.ultradns.net: 2610:a1:1014::204	AAAA	ns61.ultradns2.com (2610:a1:313d::53)
19	edns4.ultradns.org: 204.74.111.4	A	ns61.ultradns2.com (2610:a1:313d::53)
20	edns4.ultradns.org: 2001:502:4612::204	AAAA	ns61.ultradns2.com (2610:a1:313d::53)
21	dns1.registrar-servers.com: 156.154.132.200	A	edns3.registrar-servers.com (2600:1401:2::95)
22	dns1.registrar-servers.com: 2610:a1:1024::200	AAAA	edns3.registrar-servers.com (2600:1401:2::95)
23	dns2.registrar-servers.com: 156.154.133.200	A	edns3.registrar-servers.com (2600:1401:2::95)
24	dns2.registrar-servers.com: 2610:a1:1025::200	AAAA	edns3.registrar-servers.com (2600:1401:2::95)

14. CAA - Entries

Domainname	flag	Value	∑ Queries
www.lab1.site			1
lab1.site	0	no CAA entry found	1
site	0	no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
lab1.site	v=spf1 include:spf.efwd.registrar-servers.com ~all	ok	1
www.lab1.site	v=spf1 include:spf.efwd.registrar-servers.com ~all	ok	1
_acme-challenge.lab1.site		Name Error - The domain name does not exist	1
_acme-challenge.www.lab1.site		Name Error - The domain name does not exist	1
_acme-challenge.lab1.site.lab1.site			1
_acme-challenge.www.lab1.site.lab1.site		Name Error - The domain name does not exist	1
_acme-challenge.www.lab1.site.www.lab1.site		Name Error - The domain name does not exist	1

16. DomainService - Entries

Type		Domain	Pref	Value	DNS-error	num Answers	Status
MX		lab1.site	10	eforward1.registrar-servers.com	0	5	ok
	A			162.255.118.51	0	1	ok
	CNAME				0	0	ok
MX		lab1.site	10	eforward2.registrar-servers.com	0	5	ok
	A			162.255.118.52	0	1	ok
	CNAME				0	0	ok
MX		lab1.site	10	eforward3.registrar-servers.com	0	5	ok
	A			162.255.118.51	0	1	ok
	CNAME				0	0	ok
MX		lab1.site	15	eforward4.registrar-servers.com	0	5	ok
	A			162.255.118.52	0	1	ok
	CNAME				0	0	ok
MX		lab1.site	20	eforward5.registrar-servers.com	0	5	ok
	A			162.255.118.51	0	1	ok
	CNAME				0	0	ok
SPF	TXT	lab1.site		v=spf1 include:spf.efwd.registrar-servers.com ~all			ok
	TXT	spf.efwd.registrar-servers.com		v=spf1 ip4:209.105.246.192/28 ip4:198.54.122.192/26 ip4:162.255.118.0/26 ip4:198.54.122.0/28 ip4:162.255.118.240/29 ip4:63.250.43.96/27 ip4:198.177.126.16/28 ?all			ok

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=d6f87fb8-39f7-4d5c-bd52-36b459da683f

Last Result: https://check-your-website.server-daten.de/?q=lab1.site - 2026-08-31 23:35:18

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

<a href="https://check-your-website.server-daten.de/?q=lab1.site" target="_blank">Check this Site: lab1.site</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=lab1.site