kinderkrebsstiftung.de

Checked 21 October 2026, 23:02 UTC · via 8.8.8.8
!Passed with warnings
22 passed 3 warnings 0 failed 4 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.aurisp.de, ns2.aurisp.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.aurisp.de, ns2.aurisp.com
NS in the zone
ns1.aurisp.de, ns2.aurisp.com
NameserverAddressesNetwork (AS)Glue
ns1.aurisp.de35.207.139.203AS15169 GOOGLE - Google LLC, US35.207.139.203
ns2.aurisp.com3.126.64.147AS16509 AMAZON-02 - Amazon.com, Inc., US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.aurisp.de, ns2.aurisp.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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS15169 (GOOGLE - Google LLC, US): 1 address; AS16509 (AMAZON-02 - Amazon.com, Inc., US): 1 address.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .de.
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.aurisp.de 35.207.139.203NOERROR, 4 ms, authoritativenoyes / yesrefused9.20.29-1~deb13u1-Debian
ns2.aurisp.com 3.126.64.147NOERROR, 9 ms, authoritativenoyes / yesrefused9.20.29-1~deb13u1-Debian

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.aurisp.de: "9.20.29-1~deb13u1-Debian"; ns2.aurisp.com: "9.20.29-1~deb13u1-Debian". 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 2024020604 · primary ns1.aurisp.de

Found

Primary (MNAME)
ns1.aurisp.de
Contact (RNAME)
support.aurisp.de
Serial
2024020604
Refresh / retry
3600 s / 1800 s
Expire
1814400 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.aurisp.de (35.207.139.203)2024020604
ns2.aurisp.com (3.126.64.147)2024020604

Checks

  • ✓ Serial 2024020604 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 30m, expire 21d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.aurisp.de is one of the listed nameservers.
  • ✓ Contact support@aurisp.de #25
    The SOA RNAME support.aurisp.de means support@aurisp.de.
  • ✓ Date-based serial #26
    The serial 2024020604 follows the YYYYMMDDnn convention (2024-02-06).

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

8 records at the apex

Found

Read from
35.207.139.203:53
TypeValueTTL
SOAns1.aurisp.de. support.aurisp.de. 2024020604 3600 1800 1814400 360086400
NSns1.aurisp.de.14400
NSns2.aurisp.com.14400
A213.239.212.2314400
MX0 kinderkrebsstiftung-de.mail.protection.outlook.com.14400
TXT"v=spf1 include:spf.protection.outlook.com a:app-01.kinderkrebsstiftung.de include:spf.crsend.com include:spf.th.je -all"14400
TXT"1d/I0ah6IaxqKHhjAI+zoNlvaU+a/DIa4G/KTrCNbM7/njc1erKdCczuBG05If38A6jkqOdR3kooJoMvsyXkYQ=="14400
TXT"MS=ms18117458"14400

Checks

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