musicalworld.nl

Checked 22 October 2026, 14:40 UTC · via 8.8.8.8
✗Problems found
24 passed 1 warning 1 failed 7 info

Registration

info

.nl country-code

Found

TLD
.nl (country-code)
ICANN policies apply
no
Lookup error: https://rdap.sidn.nl/domain/musicalworld.nl returned HTTP 429

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
    Could not be checked
    The RDAP lookup failed, so this could not be checked: https://rdap.sidn.nl/domain/musicalworld.nl returned HTTP 429
    #3

Delegation

info

ns1.tikklik.nl, ns2.tikklik.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.tikklik.nl, ns2.tikklik.com
NS in the zone
ns1.tikklik.nl, ns2.tikklik.com
NameserverAddressesNetwork (AS)Glue
ns1.tikklik.nl5.22.255.2 2a00:1bd0:740:1:2::2AS39704 CJ2-AS - CJ2 Hosting B.V., NL AS39704 CJ2-AS - CJ2 Hosting B.V., NL5.22.255.2 2a00:1bd0:740:1:2::2
ns2.tikklik.com46.182.222.162 2a00:1bd0:740:1:46::162AS39704 CJ2-AS - CJ2 Hosting B.V., NL AS39704 CJ2-AS - CJ2 Hosting B.V., NL-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.tikklik.nl, ns2.tikklik.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.
  • i
    One address family in one network
    all IPv6 addresses are in 2a00:1bd0:740::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS39704 (CJ2-AS - CJ2 Hosting B.V., NL): 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
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .nl.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.tikklik.nl 5.22.255.2NOERROR, 18 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns1.tikklik.nl 2a00:1bd0:740:1:2::2NOERROR, 18 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns2.tikklik.com 46.182.222.162NOERROR, 14 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns2.tikklik.com 2a00:1bd0:740:1:46::162NOERROR, 15 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.tikklik.nl: "PowerDNS Authoritative Server 4.7.3"; ns2.tikklik.com: "PowerDNS Authoritative Server 4.7.3". 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

fail

serial 2020010302 · primary ns1.tikklik.nl

Found

Primary (MNAME)
ns1.tikklik.nl
Contact (RNAME)
reg\@tikklik.nl
Serial
2020010302
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.tikklik.nl (5.22.255.2)2020010302
ns1.tikklik.nl (2a00:1bd0:740:1:2::2)2020010302
ns2.tikklik.com (46.182.222.162)2020010302
ns2.tikklik.com (2a00:1bd0:740:1:46::162)2020010302

Checks

  • ✓ Serial 2020010302 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.tikklik.nl is one of the listed nameservers.
  • ✗
    Invalid contact address
    The SOA RNAME "reg\\@tikklik.nl" contains an @; it must be written with a dot instead (hostmaster.example.com).
    #25
  • ✓ Date-based serial #26
    The serial 2020010302 follows the YYYYMMDDnn convention (2020-01-03).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
5 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
9455ECDSAP256SHA256 (13)SHA256 8B106147524F8CCE…yes

DNSKEY in the zone

Key tagRoleAlgorithm
9455KSK (257)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 9455 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 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

info

7 records at the apex

Found

Read from
5.22.255.2:53
TypeValueTTL
SOAns1.tikklik.nl. reg\@Tikklik.nl. 2020010302 10800 3600 1209600 360086400
NSns2.tikklik.com.86400
NSns1.tikklik.nl.86400
A20.126.90.23686400
MX0 musicalworld-nl.mail.protection.outlook.com.86400
TXT"v=spf1 include:spf.protection.outlook.com include:spf.tkservers.com -all"86400
TXT"MS=ms22686531"86400

Checks

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