ftm.nl

Checked 21 October 2026, 21:15 UTC · via 8.8.8.8
!Passed with warnings
24 passed 2 warnings 0 failed 8 info

Registration

info

.nl country-code · team.blue nl B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
team.blue nl B.V.
Registered
20 January 2003
Last changed
19 May 2026
Status
active
Registry nameservers
coco.bunny.net, kiki.bunny.net
RDAP server
https://rdap.sidn.nl/

Checks

  • i
    .nl 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
    .nl is delegated in the root zone and DNSSEC-signed.
  • i
    Expiry date not published
    The registry does not publish the expiry date in RDAP. Check it with your registrar.
    #3
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

coco.bunny.net, kiki.bunny.net

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.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, 6 ms, authoritativenoyes / yesrefused-
kiki.bunny.net 91.200.176.1NOERROR, 13 ms, authoritativenoyes / yesrefused-
kiki.bunny.net 2400:52e0:fff0::1NOERROR, 18 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 2021999918 · primary kiki.bunny.net

Found

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

Serial per nameserver

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

Checks

  • ✓ Serial 2021999918 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 2021999918 is a Unix timestamp (2034-01-27 18:38 UTC).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC
Signatures valid until
18 November 2026

DNSKEY in the zone

Key tagRoleAlgorithm
59234ZSK (256)ECDSAP256SHA256 (13)
43038KSK (257)ECDSAP256SHA256 (13)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-18 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-18 21:10 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

warn

17 records at the apex

Found

Read from
109.104.147.1:53
TypeValueTTL
SOAkiki.bunny.net. hostmaster.bunny.net. 2021999918 7200 900 1209600 86400900
NSkiki.bunny.net.172800
NScoco.bunny.net.172800
A185.111.111.15835
AAAA2400:52e0:1e00:2::1329:135
MX10 aspmx.l.google.com.300
MX20 alt1.aspmx.l.google.com.300
MX20 alt2.aspmx.l.google.com.300
MX30 aspmx2.googlemail.com.300
MX30 aspmx3.googlemail.com.300
MX30 aspmx4.googlemail.com.300
MX30 aspmx5.googlemail.com.300
TXT"keybase-site-verification=lOLNn52gDjvycbnOMDjfLN7nDxFmdJJ2Uhf9HbnoYDw"300
TXT"google-site-verification=IxQRX9WuUOCIWbU9FJ6ZkFtFFJ4qvMv4qq9Ak37lCDc"300
TXT"google-site-verification=28qea3AS1GkiWYYJX-v433rGu1cDO_89KOYYoQQJ0ns"300
TXT"stripe-verification=1f49b3c324d2703b7983bfb764d4248a1b228ca26298455fc04707112692ec10"300
TXT"v=spf1 a mx include:spf.mandrillapp.com include:_spf.google.com include:shops.shopify.com include:smtp-ext.protagio.nl include:_spf.tem.scaleway.com -all"300

Checks

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