Domain report: handshake.de

Registration

info

.de country-code

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

info

ns.handshake.de, robotns2.second-ns.de

Nameserver	Addresses	Network (AS)	Glue
ns.handshake.de	88.198.35.2	AS24940 HETZNER-AS - Hetzner Online GmbH, DE	88.198.35.2
robotns2.second-ns.de	213.133.100.103 2a01:4f8:0:1::5ddc:2	AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE	-

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.handshake.de, robotns2.second-ns.de.

#6
✓ 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: ns.handshake.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 2 IPv4 /24s and 1 IPv6 /48.
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 3 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

#11
i

All nameserver names under .de

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
i

Partly IPv6

These nameservers have no IPv6 address: ns.handshake.de.

#13

warn

3 of 3 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns.handshake.de 88.198.35.2	NOERROR, 0 ms, authoritative	no	yes / yes	refused	9.9.5-9+deb8u5-Debian
robotns2.second-ns.de 213.133.100.103	NOERROR, 0 ms, authoritative	no	yes / yes	refused	-
robotns2.second-ns.de 2a01:4f8:0:1::5ddc:2	NOERROR, 0 ms, authoritative	no	yes / yes	refused	-

✓ All respond #14

All 3 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: ns.handshake.de: "9.9.5-9+deb8u5-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.

warn

serial 2025021002 · primary ns.handshake.de

✓ Serial 2025021002 everywhere #22

All nameservers serve the same version of the zone.
!

Unusual SOA timers

retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 7d, negative TTL 1d.

#23
✓ Primary is a public nameserver #24

The primary nameserver ns.handshake.de is one of the listed nameservers.
✓ Contact root@handshake.de #25

The SOA RNAME root.handshake.de means root@handshake.de.
✓ Date-based serial #26

The serial 2025021002 follows the YYYYMMDDnn convention (2025-02-10).

warn

Not signed

info

6 records at the apex

Type	Value	TTL
SOA	ns.handshake.de. root.handshake.de. 2025021002 3600 3600 604800 86400	86400
NS	ns.handshake.de.	86400
NS	robotns2.second-ns.de.	86400
MX	50 cloud6.handshake.de.	86400
MX	40 dbsmtp.handshake.de.	86400
TXT	"v=spf1 mx mx:cloud3.handshake.de mx:cloud6.handshake.de mx:dbsmtpd.handshake.de ~all"	86400