kassel.de

Checked 21 October 2026, 23:02 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

warn

ns1.kassel.de, ns2.kassel.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.kassel.de, ns2.kassel.de
NS in the zone
ns1.kassel.de, ns2.kassel.de
NameserverAddressesNetwork (AS)Glue
ns1.kassel.de45.138.56.11AS20810 Netcom-Kassel - Netcom Kassel Gesellschaft fuer Telekommunikation mbH, DE45.138.56.11
ns2.kassel.de104.151.107.143AS8881 VERSATEL - 1&1 Versatel GmbH, DE104.151.107.143

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.kassel.de, ns2.kassel.de.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.kassel.de, ns2.kassel.de.
  • ✓ 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: AS20810 (Netcom-Kassel - Netcom Kassel Gesellschaft fuer Telekommunikation mbH, DE): 1 address; AS8881 (VERSATEL - 1&1 Versatel 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

info

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.kassel.de 45.138.56.11NOERROR, 7 ms, authoritativenoyes / yesrefusedBIND
ns2.kassel.de 104.151.107.143NOERROR, 11 ms, authoritativenoyes / yesrefusedBIND

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: ns1.kassel.de: "BIND"; ns2.kassel.de: "BIND".
    #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 2026102003 · primary ns1.kassel.de

Found

Primary (MNAME)
ns1.kassel.de
Contact (RNAME)
asladmin.kassel.de
Serial
2026102003
Refresh / retry
10800 s / 1800 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.kassel.de (45.138.56.11)2026102003
ns2.kassel.de (104.151.107.143)2026102003

Checks

  • ✓ Serial 2026102003 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 30m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.kassel.de is one of the listed nameservers.
  • ✓ Contact asladmin@kassel.de #25
    The SOA RNAME asladmin.kassel.de means asladmin@kassel.de.
  • ✓ Date-based serial #26
    The serial 2026102003 follows the YYYYMMDDnn convention (2026-10-20).

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

21 records at the apex

Found

Read from
45.138.56.11:53
TypeValueTTL
SOAns1.kassel.de. asladmin.kassel.de. 2026102003 10800 1800 1209600 36003600
NSns2.kassel.de.10800
NSns1.kassel.de.10800
A104.151.107.143300
MX50 mail3.kassel.de.10800
MX20 mail2.kassel.de.10800
MX10 mail1.kassel.de.10800
TXT"v=DMARC1;p=none"10800
TXT"MS=ms12124634"10800
TXT"cisco-ci-domain-verification=8b7b2af7111339127471f29f89f780088fd60ea7fab0ae5fb65ab95bfa60cf0"10800
TXT"_d19r1a843s2jbjtupk9hsaguk8la5bj"10800
TXT"w0xfs9plccbjjr8y40340h8w20xt2kt0"10800
TXT"202211080411351c97xob1pwm90ngovqtomae7nn382brcmkqucgq6cj0duqqval"10800
TXT"apple-domain-verification=7LtXckHJrN7cvVy3"10800
TXT"google-site-verification=0l-po0flI0VPxNjf1LQa5SMbemYsn4VV2Lwt9Y7BvZs"10800
TXT"v=spf1 ip4:45.138.56.6 ip4:45.138.56.7 ip4:45.138.56.8 ip4:45.138.56.14 ip4:45.138.56.41 -all"10800
CAA0 issue "geotrust.com"10800
CAA0 issue "digicert.com"10800
CAA0 issue "letsencrypt.org"10800
CAA0 issuewild "digicert.com"10800
CAA0 issuewild "geotrust.com"10800

Checks

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