openthesaurus.de

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

info

coco.bunny.net, kiki.bunny.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
coco.bunny.net, kiki.bunny.net
NS in the zone
coco.bunny.net, kiki.bunny.net
NameserverAddressesNetwork (AS)Glue
coco.bunny.net109.104.147.1 2400:52e0:fff2::1AS200325 BunnyCDN - BUNNYWAY, informacijske storitve d.o.o., SI AS200325 BunnyCDN - BUNNYWAY, informacijske storitve d.o.o., SI-
kiki.bunny.net91.200.176.1 2400:52e0:fff0::1AS200325 BunnyCDN - BUNNYWAY, informacijske storitve d.o.o., SI AS200325 BunnyCDN - BUNNYWAY, informacijske storitve d.o.o., SI-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: coco.bunny.net, kiki.bunny.net.
    #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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS200325 (BunnyCDN - BUNNYWAY, informacijske storitve d.o.o., SI): 4 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 .net
    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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
coco.bunny.net 109.104.147.1NOERROR, 3 ms, authoritativenoyes / yesrefused-
coco.bunny.net 2400:52e0:fff2::1NOERROR, 4 ms, authoritativenoyes / yesrefused-
kiki.bunny.net 91.200.176.1NOERROR, 17 ms, authoritativenoyes / yesrefused-
kiki.bunny.net 2400:52e0:fff0::1NOERROR, 19 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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 2022014792 · primary kiki.bunny.net

Found

Primary (MNAME)
kiki.bunny.net
Contact (RNAME)
hostmaster.bunny.net
Serial
2022014792
Refresh / retry
7200 s / 900 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
coco.bunny.net (109.104.147.1)2022014792
coco.bunny.net (2400:52e0:fff2::1)2022014792
kiki.bunny.net (91.200.176.1)2022014792
kiki.bunny.net (2400:52e0:fff0::1)2022014792

Checks

  • ✓ Serial 2022014792 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 15m, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver kiki.bunny.net is one of the listed nameservers.
  • ✓ Contact hostmaster@bunny.net #25
    The SOA RNAME hostmaster.bunny.net means hostmaster@bunny.net.
  • ✓ Timestamp serial #26
    The serial 2022014792 is a Unix timestamp (2034-01-27 22:46 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

warn

9 records at the apex

Found

Read from
109.104.147.1:53
TypeValueTTL
SOAkiki.bunny.net. hostmaster.bunny.net. 2022014792 7200 900 1209600 86400900
NSkiki.bunny.net.172800
NScoco.bunny.net.172800
A49.13.60.4930
MX20 mxext3.mailbox.org.300
MX10 mxext2.mailbox.org.300
MX10 mxext1.mailbox.org.300
TXT"v=spf1 include:mailbox.org include:spf.mailjet.com mx ?all"300
TXT"google-site-verification=8nhHDDqGkHw3reDHmGdZD_JH5aabWVh69SjxWbfbewE"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (30s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 2d; resolvers may use either.
    #32
  • ✓ 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