protestantsekerk.nl

Checked 21 October 2026, 21:24 UTC · via 8.8.8.8
!Passed with warnings
23 passed 3 warnings 0 failed 9 info

Registration

info

.nl country-code · CSV Networks B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
CSV Networks B.V.
Registered
11 December 2001
Last changed
1 April 2025
Status
active
Registry nameservers
ns1.pknhosting.nl, ns2.pknhosting.nl
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

warn

ns1.pknhosting.nl, ns2.pknhosting.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.pknhosting.nl, ns2.pknhosting.nl
NS in the zone
ns1.pknhosting.nl, ns2.pknhosting.nl
NameserverAddressesNetwork (AS)Glue
ns1.pknhosting.nl185.33.117.45AS20495 WEDARE - We Dare B.V., NL185.33.117.45
ns2.pknhosting.nl84.244.149.204AS20495 WEDARE - We Dare B.V., NL84.244.149.204

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.pknhosting.nl, ns2.pknhosting.nl.
    #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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS20495 (WEDARE - We Dare B.V., NL): 2 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 .nl
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.pknhosting.nl 185.33.117.45NOERROR, 10 ms, authoritativenoyes / yesrefused9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.15
ns2.pknhosting.nl 84.244.149.204NOERROR, 10 ms, authoritativenoyes / yesrefused9.11.36-RedHat-9.11.36-11.el8_9

Checks

  • ✓ All respond #14
    All 2 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.pknhosting.nl: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.15"; ns2.pknhosting.nl: "9.11.36-RedHat-9.11.36-11.el8_9". 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

warn

serial 2026100101 · primary ns1.pknhosting.nl

Found

Primary (MNAME)
ns1.pknhosting.nl
Contact (RNAME)
hostmaster.protestantsekerk.nl
Serial
2026100101
Refresh / retry
3600 s / 3600 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.pknhosting.nl (185.33.117.45)2026100101
ns2.pknhosting.nl (84.244.149.204)2026100101

Checks

  • ✓ Serial 2026100101 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 14d, negative TTL 1d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.pknhosting.nl is one of the listed nameservers.
  • ✓ Contact hostmaster@protestantsekerk.nl #25
    The SOA RNAME hostmaster.protestantsekerk.nl means hostmaster@protestantsekerk.nl.
  • ✓ Date-based serial #26
    The serial 2026100101 follows the YYYYMMDDnn convention (2026-10-01).

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
8630ECDSAP256SHA256 (13)SHA256 ED867349BA537642…yes

DNSKEY in the zone

Key tagRoleAlgorithm
8630KSK (257)ECDSAP256SHA256 (13)
45193ZSK (256)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 8630 (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 01:20 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

14 records at the apex

Found

Read from
185.33.117.45:53
TypeValueTTL
SOAns1.pknhosting.nl. hostmaster.protestantsekerk.nl. 2026100101 3600 3600 1209600 864003600
NSns2.pknhosting.nl.3600
NSns1.pknhosting.nl.3600
A89.41.169.2273600
AAAA2a01:7c8:e001:f9::418d3600
MX0 protestantsekerk-nl.mail.protection.outlook.com.3600
TXT"google-site-verification=K2KlVD8E7w2eD9C_86qDF9mFFaPIBTFRyfGI4XxLku4"3600
TXT"MS=ms70356542"3600
TXT"sophos-domain-verification=825f34547a5703c10477931852557b0e3548338a"3600
TXT"1ZrMD0u/kr8LrepfsiE3XWSHzIfFej2LAK2ELPtVP3jlnxszCrh81YheGTyCGvYER11AipX2YwdTkkYLeY7N/A=="3600
TXT"google-site-verification=X8p6HSVaUvPW3JajNa0V5013zQorzPL5HvDJ5D5fVdc"3600
TXT"MS=ms59947719"3600
TXT"google-site-verification=JeMxPXH1x8r9KQ0fGK-aBvPIhOf2bHmk0daeN58qsc4"3600
TXT"v=spf1 include:spf.protection.outlook.com include:5yd8kyj3e3.powerspf.com include:spf.flowmailer.net include:sendgrid.net include:spf.afas.online ~al" "l"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, AAAA 1h, MX 1h, NS 1h.
  • ✓ 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