bundderversicherten.de

Checked 21 October 2026, 22:00 UTC · via 8.8.8.8
!Passed with warnings
19 passed 4 warnings 0 failed 6 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.kcs-netz.de, ns2.kcs-netz.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.kcs-netz.de, ns2.kcs-netz.de
NS in the zone
ns1.kcs-netz.de, ns2.kcs-netz.de
NameserverAddressesNetwork (AS)Glue
ns1.kcs-netz.de212.162.56.27AS3356 LEVEL3 - Level 3 Parent, LLC, US-
ns2.kcs-netz.de213.203.243.202AS61157 PLUSSERVER-ASN1 - PlusServer GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.kcs-netz.de, ns2.kcs-netz.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: AS3356 (LEVEL3 - Level 3 Parent, LLC, US): 1 address; AS61157 (PLUSSERVER-ASN1 - PlusServer GmbH, 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.kcs-netz.de 212.162.56.27NOERROR, 8 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 5 2026 13:21:12 by root@localhost)
ns2.kcs-netz.de 213.203.243.202NOERROR, 15 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.5 (built Feb 7 2025 09:28:41 by root@localhost)

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.kcs-netz.de: "PowerDNS Authoritative Server 5.1.4 (built Aug 5 2026 13:21:12 by root@localhost)"; ns2.kcs-netz.de: "PowerDNS Authoritative Server 4.8.5 (built Feb 7 2025 09:28:41 by root@localhost)". 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

warn

serial 2017012600 · primary ns1.kcs-netz.de

Found

Primary (MNAME)
ns1.kcs-netz.de
Contact (RNAME)
hostmaster.bundderversicherten.de
Serial
2017012600
Refresh / retry
86400 s / 7200 s
Expire
3600000 s
Negative TTL
172800 s

Serial per nameserver

NameserverSerial
ns1.kcs-netz.de (212.162.56.27)2017012600
ns2.kcs-netz.de (213.203.243.202)2017012600

Checks

  • ✓ Serial 2017012600 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 2h, expire 1000h, negative TTL 2d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.kcs-netz.de is one of the listed nameservers.
  • ✓ Contact hostmaster@bundderversicherten.de #25
    The SOA RNAME hostmaster.bundderversicherten.de means hostmaster@bundderversicherten.de.
  • ✓ Date-based serial #26
    The serial 2017012600 follows the YYYYMMDDnn convention (2017-01-26).

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

info

11 records at the apex

Found

Read from
212.162.56.27:53
TypeValueTTL
SOAns1.kcs-netz.de. hostmaster.bundderversicherten.de. 2017012600 86400 7200 3600000 172800300
NSns2.kcs-netz.de.300
NSns1.kcs-netz.de.300
A185.249.118.16300
MX10 mx01.nsp.vater-it.com.300
MX20 mx02.nsp.vater-it.com.300
TXT"v=spf1 a:mail.bundderversicherten.de include:_spf.smtp.com include:spf1.x-mailer.de include:spf2.x-mailer.de ip4:217.29.40.208 ip6:2a00:b580:8000:12:e87b:5c88:90f1:bec2 include:_spf.rexx-suite.com include:_spf.nsp.vater-it.com -all"300
TXT"brevo-code:eafa614bb7fdfaa6b51dce8faf8fc1d9"300
TXT"11.12.2024"300
TXT"MS=BDA81C58242EA8ED2F66B82C939BEAB2FE184482"300
TXT"google-site-verification=apyFMT0o6jXNx2TVWpqy78noyBP0PyQKdR-GYgqpwIQ"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 5m. The NS TTL at the parent is 1d and in the zone 5m; 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