Domain report: mtu.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.nodesecure.com, ns2.nodesecure.de

Found

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

Nameserver	Addresses	Network (AS)	Glue
ns1.nodesecure.com	192.174.68.102 2001:67c:1bc::102	AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT	-
ns2.nodesecure.de	176.97.158.102 2001:67c:10b8::102	AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT	-

Checks

i

2 nameservers

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

#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.
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

#11
✓ Nameserver names under 2 TLDs #12

Nameserver names use the TLDs .com, .de.
✓ 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.nodesecure.com 192.174.68.102	NOERROR, 4 ms, authoritative	no	yes / yes	refused	RcodeZero DNS
ns1.nodesecure.com 2001:67c:1bc::102	NOERROR, 4 ms, authoritative	no	yes / yes	refused	RcodeZero DNS
ns2.nodesecure.de 176.97.158.102	NOERROR, 14 ms, authoritative	no	yes / yes	refused	reg-wie1
ns2.nodesecure.de 2001:67c:10b8::102	NOERROR, 12 ms, authoritative	no	yes / yes	refused	reg-wie1

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.nodesecure.com: "RcodeZero DNS"; ns2.nodesecure.de: "reg-wie1".

#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 2026105064 · primary ns1.nodesecure.com

Found

Primary (MNAME): ns1.nodesecure.com
Contact (RNAME): hostmaster.mtu.de
Serial: 2026105064
Refresh / retry: 43200 s / 7200 s
Expire: 1209600 s
Negative TTL: 600 s

Serial per nameserver

Nameserver	Serial
ns1.nodesecure.com (192.174.68.102)	2026105064
ns1.nodesecure.com (2001:67c:1bc::102)	2026105064
ns2.nodesecure.de (176.97.158.102)	2026105064
ns2.nodesecure.de (2001:67c:10b8::102)	2026105064

Checks

✓ Serial 2026105064 everywhere #22

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

SOA refresh 12h, retry 2h, expire 14d, negative TTL 10m.
✓ Primary is a public nameserver #24

The primary nameserver ns1.nodesecure.com is one of the listed nameservers.
✓ Contact hostmaster@mtu.de #25

The SOA RNAME hostmaster.mtu.de means hostmaster@mtu.de.
✓ Timestamp serial #26

The serial 2026105064 is a Unix timestamp (2034-03-16 06:57 UTC).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC3
NSEC3: 0 iterations, 0-byte salt
Signatures valid until: 29 October 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
33124	ECDSAP256SHA256 (13)	SHA256 66DA86C4086C551A…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
45318	ZSK (256)	ECDSAP256SHA256 (13)
33124	KSK (257)	ECDSAP256SHA256 (13)

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 33124 (SHA256).
✓ Modern algorithms #29

Key algorithms: ECDSAP256SHA256 (13).
✓ Signatures valid until 2026-10-29 #30

The earliest DNSKEY/SOA signature expires at 2026-10-29 00:00 UTC.
✓ NSEC3 as recommended #31

The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

pass

22 records at the apex

Found

Read from: 192.174.68.102:53

Type	Value	TTL
SOA	ns1.nodesecure.com. hostmaster.mtu.de. 2026105064 43200 7200 1209600 600	600
NS	ns1.nodesecure.com.	600
NS	ns2.nodesecure.de.	600
A	3.33.173.236	300
A	15.197.179.195	300
MX	10 mx0-61.mtu.de.	3600
MX	10 mx1-63.mtu.de.	3600
MX	10 mx2-63.mtu.de.	3600
TXT	"MS=ms97733255"	600
TXT	"ZOOM_verify_74om2qO1RyGPwiaAOXuHuw"	600
TXT	"smartsheet-site-validation=ULvoGhxNRQreawZt2aQsGnHVnRuohTBZ"	600
TXT	"v=spf1 a:mx2-63.mtu.de a:mx0-61.mtu.de a:mx1-63.mtu.de -all"	600
TXT	"e08e8bb6d1e1f469fe054ae12ce6edf98f89a7451822243fa696c80d93227a6"	600
TXT	"1Pb/KqjZTwtQaRMkbakkChw6KRQ1E/we3Slm0F1cf/pnzfnkjib3tEXa0kOkVK1Uq87/mXkKo+6MY4zpSV1nUQ=="	600
TXT	"dell-technologies-domain-verification=mtu.de_2e550163-3439-438b-8135-846d5e50702b_1726637836"	600
TXT	"atlassian-domain-verification=zc9WeCijeQzLbO7GZpXbRyc2/SqB7vE9e0EvCcD37CnbaXDOT9UzhNqAawfR40gF"	600
CAA	0 issue "amazonaws.com"	600
CAA	0 issue "certum.pl"	600
CAA	0 issue "digicert.com"	600
CAA	0 issue "letsencrypt.org"	600
CAA	0 issue "sectigo.com"	600
CAA	0 issuewild "letsencrypt.org"	600

Checks

✓ TTLs within range #32

TTLs: A 5m, MX 1h, NS 10m. The NS TTL at the parent is 1d and in the zone 10m; 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.
✓ CAA restricts issuance #35

Certificates may be issued by: amazonaws.com, certum.pl, digicert.com, letsencrypt.org, sectigo.com.