Domain report: licht.de

Registration

info

.de country-code

Found

TLD: .de (country-code)
ICANN policies apply: no

Checks

i

.de is a country-code TLD (ccTLD)

Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.

#1
✓ TLD delegated and signed #2

.de is delegated in the root zone and DNSSEC-signed.
i

Registration data not available

No registration data via RDAP: the registry of .de offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.

#3

Delegation

info

ns1.zvei.org, ns2.zvei.org

Found

Parent zone: de
Delegation from: a.nic.de (194.0.0.53)
NS at the parent: ns1.zvei.org, ns2.zvei.org
NS in the zone: ns1.zvei.org, ns2.zvei.org

Nameserver	Addresses	Network (AS)	Glue
ns1.zvei.org	185.17.146.85 2a00:c98:2200:af0f:13::85	AS28753 LEASEWEB-DE-FRA-10 - Leaseweb Deutschland GmbH, DE AS28753 LEASEWEB-DE-FRA-10 - Leaseweb Deutschland GmbH, DE	-
ns2.zvei.org	23.88.19.185 2a01:4f8:242:4d83::185	AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE	-

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.zvei.org, ns2.zvei.org.

#6
✓ Parent and zone agree #7

The parent delegation and the zone's NS records list the same nameservers.
✓ No glue needed #8

All nameservers are outside the zone, so no glue records are needed.
✓ All names resolve #9

Every nameserver name has an address and is not an alias.
✓ Nameservers in different networks #10

The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses; AS28753 (LEASEWEB-DE-FRA-10 - Leaseweb Deutschland GmbH, DE): 2 addresses.
i

All nameserver names under .org

All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.

#12
✓ All reachable over IPv6 #13

Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.zvei.org 185.17.146.85	NOERROR, 3 ms, authoritative	no	yes / yes	refused	ZVEI - ns1
ns1.zvei.org 2a00:c98:2200:af0f:13::85	NOERROR, 4 ms, authoritative	no	yes / yes	refused	ZVEI - ns1
ns2.zvei.org 23.88.19.185	NOERROR, 3 ms, authoritative	no	yes / yes	refused	ZVEI - ns2
ns2.zvei.org 2a01:4f8:242:4d83::185	NOERROR, 3 ms, authoritative	no	yes / yes	refused	ZVEI - ns2

Checks

✓ All respond #14

All 4 nameserver addresses answered.
✓ All authoritative #15

Every responding nameserver answers authoritatively for the zone.
✓ No recursion #16

The nameservers do not answer recursive queries for other domains.
i

Identifying string disclosed

These nameservers answer version queries with a string that is not a version number: ns1.zvei.org: "ZVEI - ns1"; ns2.zvei.org: "ZVEI - ns2".

#17
✓ Zone transfers refused #18

No nameserver allows a zone transfer to the public.
✓ TCP supported #19

All nameservers answer over TCP.
✓ EDNS supported #20

All nameservers support EDNS(0).
✓ Public addresses #21

All nameserver addresses are publicly routable.

SOA

pass

serial 2023042261 · primary ns1.zvei.org

Found

Primary (MNAME): ns1.zvei.org
Contact (RNAME): hostmaster.ns1.zvei.org
Serial: 2023042261
Refresh / retry: 86400 s / 7200 s
Expire: 604800 s
Negative TTL: 86400 s

Serial per nameserver

Nameserver	Serial
ns1.zvei.org (185.17.146.85)	2023042261
ns1.zvei.org (2a00:c98:2200:af0f:13::85)	2023042261
ns2.zvei.org (23.88.19.185)	2023042261
ns2.zvei.org (2a01:4f8:242:4d83::185)	2023042261

Checks

✓ Serial 2023042261 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 1d, retry 2h, expire 7d, negative TTL 1d.
✓ Primary is a public nameserver #24

The primary nameserver ns1.zvei.org is one of the listed nameservers.
✓ Contact hostmaster@ns1.zvei.org #25

The SOA RNAME hostmaster.ns1.zvei.org means hostmaster@ns1.zvei.org.
✓ Date-based serial #26

The serial 2023042261 follows the YYYYMMDDnn convention (2023-04-22).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC
Signatures valid until: 18 November 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
24041	RSASHA256 (8)	SHA256 7B1A180B2E867F69…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
45786	ZSK (256)	RSASHA256 (8)
24041	KSK (257)	RSASHA256 (8)

Checks

✓ Signed and validated #27

The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
✓ DS matches a key #28

The DS record at the parent matches a key in the zone: key tag 24041 (SHA256).
✓ Modern algorithms #29

Key algorithms: RSASHA256 (8).
✓ Signatures valid until 2026-11-18 #30

The earliest DNSKEY/SOA signature expires at 2026-11-18 19:07 UTC.
i

NSEC

The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.

#31

Records

info

6 records at the apex

Found

Read from: 185.17.146.85:53

Type	Value	TTL
SOA	ns1.zvei.org. hostmaster.ns1.zvei.org. 2023042261 86400 7200 604800 86400	3600
NS	ns2.zvei.org.	3600
NS	ns1.zvei.org.	3600
A	168.119.84.244	3600
MX	10 manwe.zvei.org.	3600
TXT	"v=spf1 ip4:168.119.84.244 include:zvei.org -all"	3600

Checks

✓ TTLs within range #32

TTLs: A 1h, MX 1h, NS 1h. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
✓ No CNAME at the apex #33

The zone apex has no CNAME record.
✓ No wildcard #34

Names that don't exist return NXDOMAIN.
i

No CAA records

Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.

#35