silicon-saxony.de

Checked 22 October 2026, 00:10 UTC · via 8.8.8.8
!Passed with warnings
20 passed 4 warnings 0 failed 5 info

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

warn

ns1.ddaz.de, ns2.ddaz.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.ddaz.de, ns2.ddaz.de
NS in the zone
ns1.ddaz.de, ns2.ddaz.de
NameserverAddressesNetwork (AS)Glue
ns1.ddaz.de91.151.16.5AS47692 NESSUS - Nessus GmbH, AT-
ns2.ddaz.de85.215.203.60AS8560 IONOS-AS - IONOS SE, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.ddaz.de, ns2.ddaz.de.
    #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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS47692 (NESSUS - Nessus GmbH, AT): 1 address; AS8560 (IONOS-AS - IONOS SE, DE): 1 address.
  • 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

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.ddaz.de 91.151.16.5NOERROR, 17 ms, authoritativenoyes / yesrefused9.18.28-1~deb12u2-Debian
ns2.ddaz.de 85.215.203.60NOERROR, 14 ms, authoritativenoyes / yesrefused9.18.49-1~deb12u2-Debian

Checks

  • ✓ All respond #14
    All 2 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: ns1.ddaz.de: "9.18.28-1~deb12u2-Debian"; ns2.ddaz.de: "9.18.49-1~deb12u2-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.

SOA

pass

serial 2025111203 · primary ns2.ddaz.de

Found

Primary (MNAME)
ns2.ddaz.de
Contact (RNAME)
hostmaster.ddaz.de
Serial
2025111203
Refresh / retry
86400 s / 7200 s
Expire
2592000 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.ddaz.de (91.151.16.5)2025111203
ns2.ddaz.de (85.215.203.60)2025111203

Checks

  • ✓ Serial 2025111203 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 30d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns2.ddaz.de is one of the listed nameservers.
  • ✓ Contact hostmaster@ddaz.de #25
    The SOA RNAME hostmaster.ddaz.de means hostmaster@ddaz.de.
  • ✓ Date-based serial #26
    The serial 2025111203 follows the YYYYMMDDnn convention (2025-11-12).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

warn

10 records at the apex

Found

Read from
91.151.16.5:53
TypeValueTTL
SOAns2.ddaz.de. hostmaster.ddaz.de. 2025111203 86400 7200 2592000 8640060
NSns2.ddaz.de.60
NSns1.ddaz.de.60
A85.13.151.8860
MX0 siliconsaxony-de01i.mail.protection.outlook.com.60
TXT"brevo-code:1574bcdc948baa2f686e3ed14e689214"60
TXT"google-site-verification=sJ_sV4y9k-UoLmodqa9_SbQwoztAlIO1LRJaPt3CRwk"60
TXT"v=spf1 include:spf.protection.outlook.com ip4:212.111.231.198 ip4:85.13.139.195 ip4:85.13.151.88 include:spf.nl2go.com include:7789754.spf04.hubspotemail.net -all"60
TXT"v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC07+dID3QOYGrRCsKkY7Ia8WWnoL2rF8vtzJTHtFn/EZPtD/a4hq1DnH4ldDxGala12fxf+wsYzAYm+4xLtfNzinWdaq86hECnm1gF4jVSqjXYFwZV3syVWthMjJNbQKPzx4LXJSj9qyuIFEOZ7stCm+GbXAWBNdeaikEumYoPnwIDAQAB;"60
TXT"MS=ms97966169"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1m; 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