blzk.de

Checked 21 October 2026, 21:50 UTC · via 8.8.8.8
!Passed with warnings
19 passed 2 warnings 0 failed 8 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
ns5.kasserver.com, ns6.kasserver.com
NameserverAddressesNetwork (AS)Glue
ns5.kasserver.com85.13.128.3AS34788 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
  • ✓ 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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS34788 (NMM-AS - Neue Medien Muennich GmbH, DE): 2 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 .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

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns5.kasserver.com 85.13.128.3NOERROR, 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 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns5.kasserver.com: "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 2610211116 · primary ns5.kasserver.com

Found

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

Serial per nameserver

NameserverSerial
ns5.kasserver.com (85.13.128.3)2610211116
ns6.kasserver.com (85.13.159.101)2610211116

Checks

  • ✓ Serial 2610211116 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 2610211116 is a Unix timestamp (2052-09-17 18:38 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
85.13.128.3:53
TypeValueTTL
SOAns5.kasserver.com. hostmaster.kasserver.com. 2610211116 28800 7200 1209600 72007200
NSns6.kasserver.com.7200
NSns5.kasserver.com.7200
A116.202.5.207200
MX10 blzk-de.mail.protection.outlook.com.7200
TXT"v=spf1 ip4:91.99.19.86/32 ip4:2.29.27.206/32 mx ip4:80.72.142.162/32 ip4:80.72.142.163/32 ip4:85.158.142.120/32 ip4:85.158.142.9/32 ip4:85.158.142.121/32 ip4:85.158.142.1/32 ip4:85.158.142.2/32 ip4:85.158.142.113/32 ip4:85.158.142.112/32 ip4:10.10.10.152/" "32 ip4:10.10.10.61/32 ip4:212.114.201.59/32 ip4:85.13.144.175/32 ip4:178.77.121.172/32 include:spf.messagelabs.com include:Hosting.fdi.de include:spf.protection.outlook.com include:kasserver.com include:_spf.zimpel.de -all"7200
TXT"google-site-verification=55BjOs2DyWDIJXTgxE_kHP-lA5G1V5UzAjXYaWl_WTQ"7200
TXT"MS=ms44398505"7200
TXT"sophos-domain-verification=c787afb79e3435d44aeb5f247c4e13d5741658b16b845855691adfc4bc6ee67a"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
  • 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