afu-kiel.de

Checked 21 October 2026, 21:28 UTC · via 8.8.8.8
!Passed with warnings
21 passed 2 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

info

ns1.kserver.org, ns2.kserver.org, ns3.kserver.org

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.kserver.org, ns2.kserver.org, ns3.kserver.org
NS in the zone
ns1.kserver.org, ns2.kserver.org, ns3.kserver.org
NameserverAddressesNetwork (AS)Glue
ns1.kserver.org192.174.68.104 2001:67c:1bc::104AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns2.kserver.org176.97.158.104 2001:67c:10b8::104AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns3.kserver.org45.87.158.53 2a02:d500::53AS48596 INWX - InterNetworX Management GmbH, DE AS48596 INWX - InterNetworX Management GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.kserver.org, ns2.kserver.org, ns3.kserver.org.
  • ✓ 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 3 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 4 addresses; AS48596 (INWX - InterNetworX Management GmbH, DE): 2 addresses.
  • i
    All nameserver names under .org
    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

info

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.kserver.org 192.174.68.104NOERROR, 3 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.kserver.org 2001:67c:1bc::104NOERROR, 3 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.kserver.org 176.97.158.104NOERROR, 12 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.kserver.org 2001:67c:10b8::104NOERROR, 12 ms, authoritativenoyes / yesrefusedreg-wie1
ns3.kserver.org 45.87.158.53NOERROR, 12 ms, authoritativenoyes / yesrefusedINWX AXFR Server
ns3.kserver.org 2a02:d500::53NOERROR, 11 ms, authoritativenoyes / yesrefusedINWX AXFR Server

Checks

  • ✓ All respond #14
    All 6 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.kserver.org: "RcodeZero DNS"; ns2.kserver.org: "reg-wie1"; ns3.kserver.org: "INWX AXFR Server".
    #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 1792029607 · primary ns1.kserver.org

Found

Primary (MNAME)
ns1.kserver.org
Contact (RNAME)
dns.kserver.org
Serial
1792029607
Refresh / retry
1200 s / 1200 s
Expire
3600 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.kserver.org (192.174.68.104)1792029607
ns1.kserver.org (2001:67c:1bc::104)1792029607
ns2.kserver.org (176.97.158.104)1792029607
ns2.kserver.org (2001:67c:10b8::104)1792029607
ns3.kserver.org (45.87.158.53)1792029607
ns3.kserver.org (2a02:d500::53)1792029607

Checks

  • ✓ Serial 1792029607 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 20m should be shorter than refresh 20m; expire 1h is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 20m, retry 20m, expire 1h, negative TTL 10m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.kserver.org is one of the listed nameservers.
  • ✓ Contact dns@kserver.org #25
    The SOA RNAME dns.kserver.org means dns@kserver.org.
  • ✓ Timestamp serial #26
    The serial 1792029607 is a Unix timestamp (2026-10-15 02:00 UTC).

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

9 records at the apex

Found

Read from
192.174.68.104:53
TypeValueTTL
SOAns1.kserver.org. dns.kserver.org. 1792029607 1200 1200 3600 600600
NSns1.kserver.org.600
NSns2.kserver.org.600
NSns3.kserver.org.600
A85.13.136.20600
MX13 mx1.kserver.org.600
MX37 mx2.kserver.org.600
MX42 mx3.kserver.org.600
TXT"v=spf1 +a +mx include:_spf.kserver.org -all"600

Checks

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