Domain report: kuketz-blog.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.desec.io, ns2.desec.org

Found

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

Nameserver	Addresses	Network (AS)	Glue
ns1.desec.io	45.54.76.1 2607:f740:e633:deec::2	AS63911 NETACTUATE-AS-AP - NetActuate, Inc, US AS63911 NETACTUATE-AS-AP - NetActuate, Inc, US	-
ns2.desec.org	157.53.224.1 2607:f740:e00a:deec::2	AS36217 IRONPATH - NetActuate, Inc, US AS36217 IRONPATH - NetActuate, Inc, US	-

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.desec.io, ns2.desec.org.

#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.
✓ 2 autonomous systems #11

The nameservers are spread over: AS36217 (IRONPATH - NetActuate, Inc, US): 2 addresses; AS63911 (NETACTUATE-AS-AP - NetActuate, Inc, US): 2 addresses.
✓ Nameserver names under 2 TLDs #12

Nameserver names use the TLDs .io, .org.
✓ 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
ns1.desec.io 45.54.76.1	NOERROR, 10 ms, authoritative	no	yes / yes	refused	-
ns1.desec.io 2607:f740:e633:deec::2	NOERROR, 10 ms, authoritative	no	yes / yes	refused	-
ns2.desec.org 157.53.224.1	NOERROR, 9 ms, authoritative	no	yes / yes	refused	-
ns2.desec.org 2607:f740:e00a:deec::2	NOERROR, 10 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

info

serial 2026094669 · primary get.desec.io

Found

Primary (MNAME): get.desec.io
Contact (RNAME): get.desec.io
Serial: 2026094669
Refresh / retry: 86400 s / 3600 s
Expire: 2419200 s
Negative TTL: 3600 s

Serial per nameserver

Nameserver	Serial
ns1.desec.io (45.54.76.1)	2026094669
ns1.desec.io (2607:f740:e633:deec::2)	2026094669
ns2.desec.org (157.53.224.1)	2026094669
ns2.desec.org (2607:f740:e00a:deec::2)	2026094669

Checks

✓ Serial 2026094669 everywhere #22

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

SOA refresh 1d, retry 1h, expire 28d, negative TTL 1h.
i

Hidden master

The primary nameserver get.desec.io is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.

#24
✓ Contact get@desec.io #25

The SOA RNAME get.desec.io means get@desec.io.
✓ Timestamp serial #26

The serial 2026094669 is a Unix timestamp (2034-03-16 04:04 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
35137	ECDSAP256SHA256 (13)	SHA256 86E583B9377398DE…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
35137	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 35137 (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

info

11 records at the apex

Found

Read from: 45.54.76.1:53

Type	Value	TTL
SOA	get.desec.io. get.desec.io. 2026094669 86400 3600 2419200 3600	300
NS	ns1.desec.io.	3600
NS	ns2.desec.org.	3600
A	46.38.242.112	86400
AAAA	2a03:4000:7:33:94cf:91ff:fe6a:b3e0	86400
MX	10 mxext1.mailbox.org.	86400
MX	10 mxext2.mailbox.org.	86400
MX	10 mxext3.mailbox.org.	86400
MX	10 mxext4.mailbox.org.	86400
TXT	"v=spf1 include:mailbox.org mx ip4:46.38.242.112 ip6:2a03:4000:7:33:94cf:91ff:fe6a:b3e0 ~all"	86400
CAA	0 issue "letsencrypt.org"	86400

Checks

✓ TTLs within range #32

TTLs: A 1d, AAAA 1d, MX 1d, 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
✓ CAA restricts issuance #35

Certificates may be issued by: letsencrypt.org.