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

a1-130.akam.net, a11-67.akam.net, a14-64.akam.net, a16-65.akam.net, a6-66.akam.net, a7-67.akam.net

Found

Parent zone: de
Delegation from: a.nic.de (194.0.0.53)
NS at the parent: a1-130.akam.net, a11-67.akam.net, a14-64.akam.net, a16-65.akam.net, a6-66.akam.net, a7-67.akam.net
NS in the zone: a1-130.akam.net, a11-67.akam.net, a14-64.akam.net, a16-65.akam.net, a6-66.akam.net, a7-67.akam.net

Nameserver	Addresses	Network (AS)	Glue
a1-130.akam.net	193.108.91.130 2600:1401:2::82	AS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL	-
a11-67.akam.net	84.53.139.67 2600:1480:1::43	AS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL	-
a14-64.akam.net	184.26.161.64 2600:1480:1800::40	AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL	-
a16-65.akam.net	23.211.132.65 2600:1406:1b::41	AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL	-
a6-66.akam.net	23.211.133.66 2600:1401:1::42	AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL	-
a7-67.akam.net	23.61.199.67 2600:1406:32::43	AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL	-

Checks

✓ 6 nameservers #6

Delegated to a1-130.akam.net, a11-67.akam.net, a14-64.akam.net, a16-65.akam.net, a6-66.akam.net, a7-67.akam.net.
✓ 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 6 IPv4 /24s and 6 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS20940 (AKAMAI-ASN1 - Akamai International B.V., NL): 2 addresses; AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 10 addresses.
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

warn

12 of 12 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
a1-130.akam.net 193.108.91.130	NOERROR, 3 ms, authoritative	no	yes / yes	refused	41824.11
a1-130.akam.net 2600:1401:2::82	NOERROR, 3 ms, authoritative	no	yes / yes	refused	41824.8
a11-67.akam.net 84.53.139.67	NOERROR, 3 ms, authoritative	no	yes / yes	refused	41824.10
a11-67.akam.net 2600:1480:1::43	NOERROR, 6 ms, authoritative	no	yes / yes	refused	41824.4
a14-64.akam.net 184.26.161.64	NOERROR, 6 ms, authoritative	no	yes / yes	refused	48878.26
a14-64.akam.net 2600:1480:1800::40	NOERROR, 7 ms, authoritative	no	yes / yes	refused	48878.29
a16-65.akam.net 23.211.132.65	NOERROR, 7 ms, authoritative	no	yes / yes	refused	48878.29
a16-65.akam.net 2600:1406:1b::41	NOERROR, 7 ms, authoritative	no	yes / yes	refused	48878.30
a6-66.akam.net 23.211.133.66	NOERROR, 5 ms, authoritative	no	yes / yes	refused	48878.31
a6-66.akam.net 2600:1401:1::42	NOERROR, 5 ms, authoritative	no	yes / yes	refused	48878.26
a7-67.akam.net 23.61.199.67	NOERROR, 7 ms, authoritative	no	yes / yes	refused	41824.9
a7-67.akam.net 2600:1406:32::43	NOERROR, 7 ms, authoritative	no	yes / yes	refused	41824.6

Checks

✓ All respond #14

All 12 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: a1-130.akam.net: "41824.11"; a1-130.akam.net: "41824.8"; a11-67.akam.net: "41824.10"; a11-67.akam.net: "41824.4"; a14-64.akam.net: "48878.26"; a14-64.akam.net: "48878.29"; a16-65.akam.net: "48878.29"; a16-65.akam.net: "48878.30"; a6-66.akam.net: "48878.31"; a6-66.akam.net: "48878.26"; a7-67.akam.net: "41824.9"; a7-67.akam.net: "41824.6". 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.

SOA

pass

serial 2026102100 · primary a1-130.akam.net

Found

Primary (MNAME): a1-130.akam.net
Contact (RNAME): hostmaster.netuse.de
Serial: 2026102100
Refresh / retry: 3600 s / 1200 s
Expire: 3600000 s
Negative TTL: 600 s

Serial per nameserver

Nameserver	Serial
a1-130.akam.net (193.108.91.130)	2026102100
a1-130.akam.net (2600:1401:2::82)	2026102100
a11-67.akam.net (84.53.139.67)	2026102100
a11-67.akam.net (2600:1480:1::43)	2026102100
a14-64.akam.net (184.26.161.64)	2026102100
a14-64.akam.net (2600:1480:1800::40)	2026102100
a16-65.akam.net (23.211.132.65)	2026102100
a16-65.akam.net (2600:1406:1b::41)	2026102100
a6-66.akam.net (23.211.133.66)	2026102100
a6-66.akam.net (2600:1401:1::42)	2026102100
a7-67.akam.net (23.61.199.67)	2026102100
a7-67.akam.net (2600:1406:32::43)	2026102100

Checks

✓ Serial 2026102100 everywhere #22

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

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

The primary nameserver a1-130.akam.net is one of the listed nameservers.
✓ Contact hostmaster@netuse.de #25

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

The serial 2026102100 follows the YYYYMMDDnn convention (2026-10-21).

DNSSEC

warn

Signed, but no DS at parent

Found

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

DNSKEY in the zone

Key tag	Role	Algorithm
33736	ZSK (256)	RSASHA256 (8)
62569	KSK (257)	RSASHA256 (8)
58969	KSK (257)	RSASHA256 (8)
5211	ZSK (256)	RSASHA256 (8)

Checks

!

Signed but not delegated securely

The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.

#27
✓ Modern algorithms #29

Key algorithms: RSASHA256 (8).
✓ Short-lived signatures (online signing) #30

Signatures are valid for 73h0m0s and created on demand; the current one was made at 2026-10-21 19:55 UTC and expires at 2026-10-24 20:55 UTC.
✓ NSEC3 as recommended #31

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

Records

warn

13 records at the apex

Found

Read from: 193.108.91.130:53

Type	Value	TTL
SOA	a1-130.akam.net. hostmaster.netuse.de. 2026102100 3600 1200 3600000 600	3600
NS	a16-65.akam.net.	3600
NS	a1-130.akam.net.	3600
NS	a11-67.akam.net.	3600
NS	a7-67.akam.net.	3600
NS	a6-66.akam.net.	3600
NS	a14-64.akam.net.	3600
A	23.55.161.172	20
A	23.55.161.194	20
MX	0 stylebook-de.mail.protection.outlook.com.	86400
TXT	"v=spf1 include:spf.asv.de include:spf.protection.outlook.com ?all"	300
TXT	"MS=ms69685796"	300
TXT	"google-site-verification=KI0lKq2Ip_UHwMjYPFPppgX6OU2iFwDLZtHF4jV6fXs"	300

Checks

!

Very low TTLs

These records have a TTL below 5m, causing extra queries and slower lookups: A (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.

#32
✓ 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