die-partei.de

Checked 21 October 2026, 22:14 UTC · via 8.8.8.8
!Passed with warnings
20 passed 3 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

ns5.kasserver.com, ns6.kasserver.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns5.kasserver.com, ns6.kasserver.com
NS in the zone
ns3.ai-dns.de, ns5.kasserver.com, ns5.name-server-kas.de, ns6.kasserver.com
NameserverAddressesNetwork (AS)Glue
ns3.ai-dns.de (zone only)168.119.5.244AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns5.kasserver.com85.13.128.3AS34788 NMM-AS - Neue Medien Muennich GmbH, DE-
ns5.name-server-kas.de (zone only)85.13.181.181AS34788 NMM-AS - Neue Medien Muennich GmbH, DE-
ns6.kasserver.com85.13.159.101AS34788 NMM-AS - Neue Medien Muennich GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns5.kasserver.com, ns6.kasserver.com.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns3.ai-dns.de, ns5.name-server-kas.de. ns3.ai-dns.de, ns5.kasserver.com, ns5.name-server-kas.de, ns6.kasserver.com report NS ns3.ai-dns.de ns5.kasserver.com ns5.name-server-kas.de ns6.kasserver.com.
    #7
  • ✓ 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 4 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 1 address; AS34788 (NMM-AS - Neue Medien Muennich GmbH, DE): 3 addresses.
  • i
    All nameserver names under .com
    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

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.ai-dns.de 168.119.5.244NOERROR, 4 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns5.kasserver.com 85.13.128.3NOERROR, 12 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns5.name-server-kas.de 85.13.181.181NOERROR, 12 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns6.kasserver.com 85.13.159.101NOERROR, 12 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns3.ai-dns.de: "Served by PowerDNS - https://www.powerdns.com/"; ns5.kasserver.com: "Served by PowerDNS - https://www.powerdns.com/"; ns5.name-server-kas.de: "Served by PowerDNS - https://www.powerdns.com/"; ns6.kasserver.com: "Served by PowerDNS - https://www.powerdns.com/".
    #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 2605280416 · primary ns5.kasserver.com

Found

Primary (MNAME)
ns5.kasserver.com
Contact (RNAME)
hostmaster.kasserver.com
Serial
2605280416
Refresh / retry
28800 s / 7200 s
Expire
1209600 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
ns3.ai-dns.de (168.119.5.244)2605280416
ns5.kasserver.com (85.13.128.3)2605280416
ns5.name-server-kas.de (85.13.181.181)2605280416
ns6.kasserver.com (85.13.159.101)2605280416

Checks

  • ✓ Serial 2605280416 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 14d, negative TTL 2h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns5.kasserver.com is one of the listed nameservers.
  • ✓ Contact hostmaster@kasserver.com #25
    The SOA RNAME hostmaster.kasserver.com means hostmaster@kasserver.com.
  • ✓ Timestamp serial #26
    The serial 2605280416 is a Unix timestamp (2052-07-22 17: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

10 records at the apex

Found

Read from
168.119.5.244:53
TypeValueTTL
SOAns5.kasserver.com. hostmaster.kasserver.com. 2605280416 28800 7200 1209600 72007200
NSns5.name-server-kas.de.7200
NSns3.ai-dns.de.7200
NSns5.kasserver.com.7200
NSns6.kasserver.com.7200
A116.202.252.2347200
MX10 w0136508.kasserver.com.7200
TXT"v=spf1 a mx include:spf.kasserver.com ~all"7200
TXT"google-site-verification=Dl9M2C2STeOeZuJG9TCM0JjUyvlgmqTvY-_KpeRf3cw"7200
CAA0 issue "letsencrypt.org"7200

Checks

  • ✓ TTLs within range #32
    TTLs: A 2h, MX 2h, 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.
  • 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org.