elk-wue.de

Checked 21 October 2026, 22:18 UTC · via 8.8.8.8
!Passed with warnings
23 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

warn

ns1.elk-wue.de, ns2.elk-wue.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.elk-wue.de, ns2.elk-wue.de
NS in the zone
ns1.elk-wue.de, ns2.elk-wue.de, ns3.elk-wue.de, ns4.elk-wue.de
NameserverAddressesNetwork (AS)Glue
ns1.elk-wue.de194.59.169.3 2001:67c:5ec::8AS34172 ELK-BAWUE-AS - Evangelische Landeskirche Wuerttemberg, DE AS34172 ELK-BAWUE-AS - Evangelische Landeskirche Wuerttemberg, DE194.59.169.3 2001:67c:5ec::8
ns2.elk-wue.de194.59.169.4 2001:67c:5ec::9AS34172 ELK-BAWUE-AS - Evangelische Landeskirche Wuerttemberg, DE AS34172 ELK-BAWUE-AS - Evangelische Landeskirche Wuerttemberg, DE194.59.169.4 2001:67c:5ec::9
ns3.elk-wue.de (zone only)194.59.169.3 2001:67c:5ec::8AS34172 ELK-BAWUE-AS - Evangelische Landeskirche Wuerttemberg, DE AS34172 ELK-BAWUE-AS - Evangelische Landeskirche Wuerttemberg, DE-
ns4.elk-wue.de (zone only)194.59.169.4 2001:67c:5ec::9AS34172 ELK-BAWUE-AS - Evangelische Landeskirche Wuerttemberg, DE AS34172 ELK-BAWUE-AS - Evangelische Landeskirche Wuerttemberg, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.elk-wue.de, ns2.elk-wue.de.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns3.elk-wue.de, ns4.elk-wue.de. ns1.elk-wue.de, ns2.elk-wue.de, ns3.elk-wue.de, ns4.elk-wue.de report NS ns1.elk-wue.de ns2.elk-wue.de ns3.elk-wue.de ns4.elk-wue.de.
    #7
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.elk-wue.de, ns2.elk-wue.de.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 194.59.169.0/24; all IPv6 addresses are in 2001:67c:5ec::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS34172 (ELK-BAWUE-AS - Evangelische Landeskirche Wuerttemberg, DE): 8 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

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.elk-wue.de 194.59.169.3NOERROR, 7 ms, authoritativenoyes / yesrefused9.16.48-Ubuntu
ns1.elk-wue.de 2001:67c:5ec::8NOERROR, 7 ms, authoritativenoyes / yesrefused9.16.48-Ubuntu
ns2.elk-wue.de 194.59.169.4NOERROR, 7 ms, authoritativenoyes / yesrefused9.16.48-Ubuntu
ns2.elk-wue.de 2001:67c:5ec::9NOERROR, 7 ms, authoritativenoyes / yesrefused9.16.48-Ubuntu
ns3.elk-wue.de 194.59.169.3NOERROR, 7 ms, authoritativenoyes / yesrefused9.16.48-Ubuntu
ns3.elk-wue.de 2001:67c:5ec::8NOERROR, 7 ms, authoritativenoyes / yesrefused9.16.48-Ubuntu
ns4.elk-wue.de 194.59.169.4NOERROR, 7 ms, authoritativenoyes / yesrefused9.16.48-Ubuntu
ns4.elk-wue.de 2001:67c:5ec::9NOERROR, 6 ms, authoritativenoyes / yesrefused9.16.48-Ubuntu

Checks

  • ✓ All respond #14
    All 8 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.elk-wue.de: "9.16.48-Ubuntu"; ns2.elk-wue.de: "9.16.48-Ubuntu"; ns3.elk-wue.de: "9.16.48-Ubuntu"; ns4.elk-wue.de: "9.16.48-Ubuntu". 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 2021144156 · primary ns1.elk-wue.de

Found

Primary (MNAME)
ns1.elk-wue.de
Contact (RNAME)
dnsadmin.elk-wue.de
Serial
2021144156
Refresh / retry
21600 s / 1800 s
Expire
1209600 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
ns1.elk-wue.de (194.59.169.3)2021144156
ns1.elk-wue.de (2001:67c:5ec::8)2021144156
ns2.elk-wue.de (194.59.169.4)2021144156
ns2.elk-wue.de (2001:67c:5ec::9)2021144156
ns3.elk-wue.de (194.59.169.3)2021144156
ns3.elk-wue.de (2001:67c:5ec::8)2021144156
ns4.elk-wue.de (194.59.169.4)2021144156
ns4.elk-wue.de (2001:67c:5ec::9)2021144156

Checks

  • ✓ Serial 2021144156 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 30m, expire 14d, negative TTL 2h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.elk-wue.de is one of the listed nameservers.
  • ✓ Contact dnsadmin@elk-wue.de #25
    The SOA RNAME dnsadmin.elk-wue.de means dnsadmin@elk-wue.de.
  • ✓ Timestamp serial #26
    The serial 2021144156 is a Unix timestamp (2034-01-17 20:55 UTC).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
7 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
28657RSASHA256 (8)SHA256 B6160146DC5F13E6…yes

DNSKEY in the zone

Key tagRoleAlgorithm
38634ZSK (256)RSASHA256 (8)
28657KSK (257)RSASHA256 (8)

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 28657 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-07 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-07 18:00 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

11 records at the apex

Found

Read from
194.59.169.3:53
TypeValueTTL
SOAns1.elk-wue.de. dnsadmin.elk-wue.de. 2021144156 21600 1800 1209600 72007200
NSns1.elk-wue.de.7200
NSns2.elk-wue.de.7200
NSns3.elk-wue.de.7200
NSns4.elk-wue.de.7200
A49.13.88.287200
MX100 elkwue-de0i.mail.protection.outlook.com.300
TXT"v=spf1 a ip4:81.169.248.75 ip4:194.145.234.113 ip4:194.145.234.114 ip4:194.145.234.115 ip4:134.119.18.24 include:spf.protection.outlook.com include:spf.crsend.com include:_spf.rexx-suite.com include:spf.sendinblue.com -all"7200
TXT"uHBh14SH745AQUBQeBz6dsrUqh7ATDgX6aXFQvbyZ8aHAOqRj0Nl/DwD0osQTBnJGDcCL/jcfY4ihCUIRulriA=="7200
TXT"brevo-code:c5447f1105acd0175fe4410d2afcb311"7200
TXT"google-site-verification=QQAKNzAKQaJ5w1HKqh-gyfLHXv2vGc-_wBbUKNnUeBU"7200

Checks

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