kiel-sailing-city.de

Checked 21 October 2026, 23:02 UTC · via 8.8.8.8
!Passed with warnings
19 passed 3 warnings 0 failed 7 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

info

ns1.addix.de, ns2.addix.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.addix.de, ns2.addix.de
NS in the zone
ns1.addix.de, ns2.addix.de
NameserverAddressesNetwork (AS)Glue
ns1.addix.de212.51.16.255 2a01:780:c000:1::2AS25415 ADDIX-AS - ADDIX GmbH, DE AS25415 ADDIX-AS - ADDIX GmbH, DE212.51.16.255 2a01:780:c000:1::2
ns2.addix.de212.51.17.255 2a01:780:c000:2::2AS25415 ADDIX-AS - ADDIX GmbH, DE AS25415 ADDIX-AS - ADDIX GmbH, DE212.51.17.255 2a01:780:c000:2::2

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.addix.de, ns2.addix.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.
  • i
    One address family in one network
    all IPv6 addresses are in 2a01:780:c000::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS25415 (ADDIX-AS - ADDIX GmbH, DE): 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 .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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.addix.de 212.51.16.255NOERROR, 18 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.14
ns1.addix.de 2a01:780:c000:1::2NOERROR, 19 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.14
ns2.addix.de 212.51.17.255NOERROR, 17 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.14
ns2.addix.de 2a01:780:c000:2::2NOERROR, 18 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.14

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.addix.de: "PowerDNS Authoritative Server 4.1.14"; ns2.addix.de: "PowerDNS Authoritative Server 4.1.14". 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 2025092405 · primary ns1.addix.de

Found

Primary (MNAME)
ns1.addix.de
Contact (RNAME)
j\.boeckmann.kiel-marketing.de
Serial
2025092405
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns1.addix.de (212.51.16.255)2025092405
ns1.addix.de (2a01:780:c000:1::2)2025092405
ns2.addix.de (212.51.17.255)2025092405
ns2.addix.de (2a01:780:c000:2::2)2025092405

Checks

  • ✓ Serial 2025092405 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 3h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.addix.de is one of the listed nameservers.
  • ✓ Contact j.boeckmann@kiel-marketing.de #25
    The SOA RNAME j\.boeckmann.kiel-marketing.de means j.boeckmann@kiel-marketing.de.
  • ✓ Date-based serial #26
    The serial 2025092405 follows the YYYYMMDDnn convention (2025-09-24).

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

7 records at the apex

Found

Read from
212.51.16.255:53
TypeValueTTL
SOAns1.addix.de. j\.boeckmann.kiel-marketing.de. 2025092405 10800 3600 604800 1080060
NSns2.addix.de.60
NSns1.addix.de.60
A212.51.30.9060
MX10 mail.kiel-sailing-city.de.60
TXT"v=spf1 include:spf.protection.outlook.com include:mail.networkteam.com a:mx02.wlk-ems.com a:mx01.wlk-ems.com a:mail.wilken.de a:mail1.wilken.de a:relay01.wlk-ems.com include:emarsys.net include:emsmtp.com ip4:212.51.16.42 ~all"60
TXT"google-site-verification=Kkxr6bywiOeKQUt-wfpgxGcDAesAAWEKsrokwKh5U8c"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