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

dns19.ovh.net, ns19.ovh.net

Found

Parent zone: de
Delegation from: a.nic.de (194.0.0.53)
NS at the parent: dns19.ovh.net, ns19.ovh.net
NS in the zone: dns19.ovh.net, ns19.ovh.net

Nameserver	Addresses	Network (AS)	Glue
dns19.ovh.net	5.135.216.9 2001:41d0:d00:f800::2	AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR	-
ns19.ovh.net	5.135.36.129 2001:41d0:b00:f200::2	AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR	-

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns19.ovh.net, ns19.ovh.net.

#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 (AS16276 (OVH - OVH SAS, FR): 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
i

All nameserver names under .net

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

pass

4 of 4 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
dns19.ovh.net 5.135.216.9	NOERROR, 16 ms, authoritative	no	yes / yes	refused	-
dns19.ovh.net 2001:41d0:d00:f800::2	NOERROR, 16 ms, authoritative	no	yes / yes	refused	-
ns19.ovh.net 5.135.36.129	NOERROR, 15 ms, authoritative	no	yes / yes	refused	-
ns19.ovh.net 2001:41d0:b00:f200::2	NOERROR, 15 ms, authoritative	no	yes / yes	refused	-

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.
✓ No version disclosed #17

The nameservers don't reveal their software version.
✓ 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 2091246799 · primary dns19.ovh.net

Found

Primary (MNAME): dns19.ovh.net
Contact (RNAME): tech.ovh.net
Serial: 2091246799
Refresh / retry: 86400 s / 3600 s
Expire: 3600000 s
Negative TTL: 300 s

Serial per nameserver

Nameserver	Serial
dns19.ovh.net (5.135.216.9)	2091246799
dns19.ovh.net (2001:41d0:d00:f800::2)	2091246799
ns19.ovh.net (5.135.36.129)	2091246799
ns19.ovh.net (2001:41d0:b00:f200::2)	2091246799

Checks

✓ Serial 2091246799 everywhere #22

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

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

The primary nameserver dns19.ovh.net is one of the listed nameservers.
✓ Contact tech@ovh.net #25

The SOA RNAME tech.ovh.net means tech@ovh.net.
✓ Timestamp serial #26

The serial 2091246799 is a Unix timestamp (2036-04-08 05:53 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: 4 November 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
42494	RSASHA256 (8)	SHA256 B42E7632D83A1272…	yes

DNSKEY in the zone

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

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

The earliest DNSKEY/SOA signature expires at 2026-11-04 23:33 UTC.
✓ NSEC3 as recommended #31

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

Records

info

4 records at the apex

Found

Read from: 5.135.216.9:53

Type	Value	TTL
SOA	dns19.ovh.net. tech.ovh.net. 2091246799 86400 3600 3600000 300	3600
NS	ns19.ovh.net.	3600
NS	dns19.ovh.net.	3600
A	167.86.89.149	3600

Checks

✓ TTLs within range #32

TTLs: A 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.
i

Wildcard record

A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.

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