fusion-festival.de

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

dns1.kulkos.net, dns2.kulkos.net, dns2.kulkos.org

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns1.kulkos.net, dns2.kulkos.net, dns2.kulkos.org
NS in the zone
dns1.kulkos.net, dns2.kulkos.net, dns2.kulkos.org
NameserverAddressesNetwork (AS)Glue
dns1.kulkos.net62.176.235.199AS9136 WOBCOM - Wobcom GmbH, DE-
dns2.kulkos.net94.16.115.50AS197540 netcup-AS - netcup GmbH, DE-
dns2.kulkos.org94.16.115.50AS197540 netcup-AS - netcup GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to dns1.kulkos.net, dns2.kulkos.net, dns2.kulkos.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 2 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS197540 (netcup-AS - netcup GmbH, DE): 2 addresses; AS9136 (WOBCOM - Wobcom GmbH, DE): 1 address.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .net, .org.
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.kulkos.net 62.176.235.199NOERROR, 14 ms, authoritativenoyes / yesrefused-
dns2.kulkos.net 94.16.115.50NOERROR, 1 ms, authoritativenoyes / yesrefused-
dns2.kulkos.org 94.16.115.50NOERROR, 2 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 3 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2019030357 · primary dns1.kulkos.net

Found

Primary (MNAME)
dns1.kulkos.net
Contact (RNAME)
hostmaster.kulturkosmos.de
Serial
2019030357
Refresh / retry
10800 s / 1350 s
Expire
1209300 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
dns1.kulkos.net (62.176.235.199)2019030357
dns2.kulkos.net (94.16.115.50)2019030357
dns2.kulkos.org (94.16.115.50)2019030357

Checks

  • ✓ Serial 2019030357 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 22m30s, expire 20155m, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.kulkos.net is one of the listed nameservers.
  • ✓ Contact hostmaster@kulturkosmos.de #25
    The SOA RNAME hostmaster.kulturkosmos.de means hostmaster@kulturkosmos.de.
  • ✓ Date-based serial #26
    The serial 2019030357 follows the YYYYMMDDnn convention (2019-03-03).

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
62.176.235.199:53
TypeValueTTL
SOAdns1.kulkos.net. hostmaster.kulturkosmos.de. 2019030357 10800 1350 1209300 300900
NSdns1.kulkos.net.300
NSdns2.kulkos.org.300
NSdns2.kulkos.net.300
A62.176.235.195300
AAAA2a01:581:1:36::195300
MX10 smtp.kulturkosmos.de.300
TXT"v=spf1 include:_spf.kulturkosmos.de ~all"300

Checks

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