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

warn

ns1.cht.de, ns2.cht.de, ns3.cht.de

Nameserver	Addresses	Network (AS)	Glue
ns1.cht.de	213.179.128.90	AS8767 MNET-AS - M-net Telekommunikations GmbH, DE	213.179.128.90
ns2.cht.de	213.179.128.91	AS8767 MNET-AS - M-net Telekommunikations GmbH, DE	213.179.128.91
ns3.cht.de	168.119.120.166	AS24940 HETZNER-AS - Hetzner Online GmbH, DE	168.119.120.166

✓ 3 nameservers #6

Delegated to ns1.cht.de, ns2.cht.de, ns3.cht.de.
✓ 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 0 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 1 address; AS8767 (MNET-AS - M-net Telekommunikations GmbH, DE): 2 addresses.
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
!

No IPv6

None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

#13

info

3 of 3 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.cht.de 213.179.128.90	NOERROR, 9 ms, authoritative	no	yes / yes	refused	unknown
ns2.cht.de 213.179.128.91	NOERROR, 11 ms, authoritative	no	yes / yes	refused	unknown
ns3.cht.de 168.119.120.166	NOERROR, 1 ms, authoritative	no	yes / yes	refused	unknown

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

Identifying string disclosed

These nameservers answer version queries with a string that is not a version number: ns1.cht.de: "unknown"; ns2.cht.de: "unknown"; ns3.cht.de: "unknown".

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

pass

serial 2026082910 · primary ns1.cht.de

✓ Serial 2026082910 everywhere #22

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

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

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

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

The serial 2026082910 follows the YYYYMMDDnn convention (2026-08-29).

warn

Not signed

info

7 records at the apex

✓ 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