parclaclusure.be

Checked 22 October 2026, 07:01 UTC · via 8.8.8.8
!Passed with warnings
22 passed 2 warnings 0 failed 5 info

Registration

info

.be country-code

Found

TLD
.be (country-code)
ICANN policies apply
no

Checks

  • i
    .be 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
    .be is delegated in the root zone and DNSSEC-signed.
  • i
    Registration data not available
    No registration data via RDAP: the registry of .be offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.
    #3

Delegation

info

ns1.instantxs.nl, ns2.instantxs.nl, ns3.instantxs.nl

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.instantxs.nl, ns2.instantxs.nl, ns3.instantxs.nl
NS in the zone
ns1.instantxs.nl, ns2.instantxs.nl, ns3.instantxs.nl
NameserverAddressesNetwork (AS)Glue
ns1.instantxs.nl195.60.215.66 2001:67c:78:391:195:60:215:66AS20847 PREVIDER-AS - Previder B.V., NL AS20847 PREVIDER-AS - Previder B.V., NL-
ns2.instantxs.nl195.60.214.20 2001:67c:78:351:195:60:214:20AS20847 PREVIDER-AS - Previder B.V., NL AS20847 PREVIDER-AS - Previder B.V., NL-
ns3.instantxs.nl178.22.60.26 2a00:1e28:3:4382::1AS12859 NL-BIT - BIT BV, NL AS12859 NL-BIT - BIT BV, NL-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.instantxs.nl, ns2.instantxs.nl, ns3.instantxs.nl.
  • ✓ 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 3 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS12859 (NL-BIT - BIT BV, NL): 2 addresses; AS20847 (PREVIDER-AS - Previder B.V., NL): 4 addresses.
  • 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.instantxs.nl 195.60.215.66NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1
ns1.instantxs.nl 2001:67c:78:391:195:60:215:66NOERROR, 10 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1
ns2.instantxs.nl 195.60.214.20NOERROR, 10 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1
ns2.instantxs.nl 2001:67c:78:351:195:60:214:20NOERROR, 10 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1
ns3.instantxs.nl 178.22.60.26NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1
ns3.instantxs.nl 2a00:1e28:3:4382::1NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1

Checks

  • ✓ All respond #14
    All 6 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.instantxs.nl: "PowerDNS Authoritative Server 4.4.1"; ns2.instantxs.nl: "PowerDNS Authoritative Server 4.4.1"; ns3.instantxs.nl: "PowerDNS Authoritative Server 4.4.1". 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

pass

serial 2022111500 · primary ns1.instantxs.nl

Found

Primary (MNAME)
ns1.instantxs.nl
Contact (RNAME)
hostmaster.instantxs.nl
Serial
2022111500
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.instantxs.nl (195.60.215.66)2022111500
ns1.instantxs.nl (2001:67c:78:391:195:60:215:66)2022111500
ns2.instantxs.nl (195.60.214.20)2022111500
ns2.instantxs.nl (2001:67c:78:351:195:60:214:20)2022111500
ns3.instantxs.nl (178.22.60.26)2022111500
ns3.instantxs.nl (2a00:1e28:3:4382::1)2022111500

Checks

  • ✓ Serial 2022111500 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.instantxs.nl is one of the listed nameservers.
  • ✓ Contact hostmaster@instantxs.nl #25
    The SOA RNAME hostmaster.instantxs.nl means hostmaster@instantxs.nl.
  • ✓ Date-based serial #26
    The serial 2022111500 follows the YYYYMMDDnn convention (2022-11-15).

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

info

8 records at the apex

Found

Read from
195.60.215.66:53
TypeValueTTL
SOAns1.instantxs.nl. hostmaster.instantxs.nl. 2022111500 10800 3600 604800 36003600
NSns2.instantxs.nl.3600
NSns3.instantxs.nl.3600
NSns1.instantxs.nl.3600
A195.60.212.433600
MX20 mail02.spamenvirusfilter.nl.3600
MX10 mail01.spamenvirusfilter.nl.3600
TXT"v=spf1 a mx ip4:188.118.17.45 ip4:188.118.7.94 ip4:62.197.81.116 ip4:185.3.161.7 ip4:185.3.161.8 include:sendgrid.net include:spf.protection.outlook.com ~all"3600

Checks

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