Domain report: spoo-design.de

Registration

info

.de country-code

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

info

coco.bunny.net, kiki.bunny.net

Nameserver	Addresses	Network (AS)	Glue
coco.bunny.net	109.104.147.1 2400:52e0:fff2::1	AS200325 BunnyCDN - BUNNYWAY, informacijske storitve d.o.o., SI AS200325 BunnyCDN - BUNNYWAY, informacijske storitve d.o.o., SI	-
kiki.bunny.net	91.200.176.1 2400:52e0:fff0::1	AS200325 BunnyCDN - BUNNYWAY, informacijske storitve d.o.o., SI AS200325 BunnyCDN - BUNNYWAY, informacijske storitve d.o.o., SI	-

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.

pass

4 of 4 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
coco.bunny.net 109.104.147.1	NOERROR, 3 ms, authoritative	no	yes / yes	refused	-
coco.bunny.net 2400:52e0:fff2::1	NOERROR, 4 ms, authoritative	no	yes / yes	refused	-
kiki.bunny.net 91.200.176.1	NOERROR, 11 ms, authoritative	no	yes / yes	refused	-
kiki.bunny.net 2400:52e0:fff0::1	NOERROR, 18 ms, authoritative	no	yes / yes	refused	-

✓ 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.

pass

serial 2021995852 · primary kiki.bunny.net

✓ Serial 2021995852 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 2021995852 is a Unix timestamp (2034-01-27 17:30 UTC).

warn

Not signed

warn

8 records at the apex

Type	Value	TTL
SOA	kiki.bunny.net. hostmaster.bunny.net. 2021995852 7200 900 1209600 86400	900
NS	kiki.bunny.net.	172800
NS	coco.bunny.net.	172800
A	185.111.111.157	35
AAAA	2400:52e0:1e00:2::1331:1	35
MX	10 mx03.secure-mailgate.com.	300
MX	10 mx04.secure-mailgate.com.	300
TXT	"v=spf1 a mx include:secure-mailgate.com -all"	300