Domain report: lrz.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

pass

dns1.lrz.de, dns2.lrz.bayern, dns3.lrz.eu

Found

Parent zone: de
Delegation from: a.nic.de (194.0.0.53)
NS at the parent: dns1.lrz.de, dns2.lrz.bayern, dns3.lrz.eu
NS in the zone: dns1.lrz.de, dns2.lrz.bayern, dns3.lrz.eu

Nameserver	Addresses	Network (AS)	Glue
dns1.lrz.de	129.187.19.183 2001:4ca0:0:100:0:53:1:1	AS12816 MWN-AS - Leibniz-Rechenzentrum, DE AS12816 MWN-AS - Leibniz-Rechenzentrum, DE	129.187.19.183 2001:4ca0:0:100:0:53:1:1
dns2.lrz.bayern	141.40.9.211 2001:4ca0:0:100:0:53:1:2	AS12816 MWN-AS - Leibniz-Rechenzentrum, DE AS12816 MWN-AS - Leibniz-Rechenzentrum, DE	-
dns3.lrz.eu	78.128.211.180 2001:718:1:1f:50:56ff:feee:180	AS2852 CESNET2 - CESNET z.s.p.o., CZ AS2852 CESNET2 - CESNET z.s.p.o., CZ	-

Checks

✓ 3 nameservers #6

Delegated to dns1.lrz.de, dns2.lrz.bayern, dns3.lrz.eu.
✓ Parent and zone agree #7

The parent delegation and the zone's NS records list the same nameservers.
✓ Glue present and correct #8

Glue is published for the nameservers inside the zone: dns1.lrz.de.
✓ 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 3 IPv4 /24s and 2 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS12816 (MWN-AS - Leibniz-Rechenzentrum, DE): 4 addresses; AS2852 (CESNET2 - CESNET z.s.p.o., CZ): 2 addresses.
✓ Nameserver names under 3 TLDs #12

Nameserver names use the TLDs .bayern, .de, .eu.
✓ All reachable over IPv6 #13

Every nameserver has an IPv6 address.

Nameservers

warn

6 of 6 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
dns1.lrz.de 129.187.19.183	NOERROR, 11 ms, authoritative	no	yes / yes	refused	9.20.29-1~deb13u1-Debian
dns1.lrz.de 2001:4ca0:0:100:0:53:1:1	NOERROR, 12 ms, authoritative	no	yes / yes	refused	9.20.29-1~deb13u1-Debian
dns2.lrz.bayern 141.40.9.211	NOERROR, 12 ms, authoritative	no	yes / yes	refused	9.20.29-1~deb13u1-Debian
dns2.lrz.bayern 2001:4ca0:0:100:0:53:1:2	NOERROR, 12 ms, authoritative	no	yes / yes	refused	9.20.29-1~deb13u1-Debian
dns3.lrz.eu 78.128.211.180	NOERROR, 8 ms, authoritative	no	yes / yes	refused	9.18.49-1~deb12u2-Debian
dns3.lrz.eu 2001:718:1:1f:50:56ff:feee:180	NOERROR, 8 ms, authoritative	no	yes / yes	refused	9.18.49-1~deb12u2-Debian

Checks

✓ All respond #14

All 6 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.
!

Software version disclosed

These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns1.lrz.de: "9.20.29-1~deb13u1-Debian"; dns2.lrz.bayern: "9.20.29-1~deb13u1-Debian"; dns3.lrz.eu: "9.18.49-1~deb12u2-Debian". Hide or replace the version string.

#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 2026101215 · primary dns1.lrz.de

Found

Primary (MNAME): dns1.lrz.de
Contact (RNAME): hostmaster.lrz.de
Serial: 2026101215
Refresh / retry: 21600 s / 1800 s
Expire: 3600000 s
Negative TTL: 86400 s

Serial per nameserver

Nameserver	Serial
dns1.lrz.de (129.187.19.183)	2026101215
dns1.lrz.de (2001:4ca0:0:100:0:53:1:1)	2026101215
dns2.lrz.bayern (141.40.9.211)	2026101215
dns2.lrz.bayern (2001:4ca0:0:100:0:53:1:2)	2026101215
dns3.lrz.eu (78.128.211.180)	2026101215
dns3.lrz.eu (2001:718:1:1f:50:56ff:feee:180)	2026101215

Checks

✓ Serial 2026101215 everywhere #22

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

SOA refresh 6h, retry 30m, expire 1000h, negative TTL 1d.
✓ Primary is a public nameserver #24

The primary nameserver dns1.lrz.de is one of the listed nameservers.
✓ Contact hostmaster@lrz.de #25

The SOA RNAME hostmaster.lrz.de means hostmaster@lrz.de.
✓ Date-based serial #26

The serial 2026101215 follows the YYYYMMDDnn convention (2026-10-12).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC
Signatures valid until: 17 December 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
42814	RSASHA256 (8)	SHA256 C2DB28705793D9DB…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
57448	ZSK (256)	RSASHA256 (8)
42814	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 42814 (SHA256).
✓ Modern algorithms #29

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

The earliest DNSKEY/SOA signature expires at 2026-12-17 12:42 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

pass

23 records at the apex

Found

Read from: 129.187.19.183:53

Type	Value	TTL
SOA	dns1.lrz.de. hostmaster.lrz.de. 2026101215 21600 1800 3600000 86400	86400
NS	dns3.lrz.eu.	86400
NS	dns2.lrz.bayern.	86400
NS	dns1.lrz.de.	86400
A	129.187.254.9	86400
AAAA	2001:4ca0:0:103::81bb:fe09	86400
MX	100 postrelay1.lrz.de.	86400
MX	100 postrelay2.lrz.de.	86400
TXT	"v=spf1 redirect=_spf.mail.lrz.de"	300
TXT	"apple-domain-verification=pv7vIHO8HI7wOb3h"	300
TXT	"HARICA-EZAWPzMWSFYR84lVnZM"	300
TXT	"adobe-idp-site-verification=e3cfd187f14222c3543809079d97034193253e92972ebb1319112d45522073e1"	300
TXT	"_telesec-domain-validation=342343_2025-04-09_4aBfZM59EiUBoZY1FjeG3bJESJjEvz5eiOMjYtWUtSTrgaSlHZ"	300
TXT	"_telesec-domain-validation=354726_2026-02-04_zSJyIi4tWMe32yF3pXU7ayGx6LVKJsLshMrwtAylL7IlSqQvWI"	300
TXT	"HARICA-BLoBBL4RVjxhtBKZMhQ"	300
TXT	"ZOOM_verify_U19bXiZbRpCHdlwiBU647w"	300
TXT	"MS=DE0B9CA4BB75DB02492F692CCC82F76F708512A5"	300
TXT	"sophos-domain-verification=1a4fcd30b32aa8612b04abdf18154cb0b3a2b246a0edbe98bcda3599f1ed9ce6"	300
TXT	"google-site-verification=aery99S4-qQNyQyHH2_P3UlwnXrfYgKa-BHwwKDRY1w"	300
CAA	0 issue "telesec.de"	86400
CAA	0 issue "pki.dfn.de"	86400
CAA	0 issue "harica.gr"	86400
CAA	0 issue "sectigo.com"	86400

Checks

✓ TTLs within range #32

TTLs: A 1d, AAAA 1d, MX 1d, NS 1d.
✓ No CNAME at the apex #33

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

Names that don't exist return NXDOMAIN.
✓ CAA restricts issuance #35

Certificates may be issued by: telesec.de, pki.dfn.de, harica.gr, sectigo.com.