jazzhalo.be

Checked 22 October 2026, 06:40 UTC · via 8.8.8.8
!Passed with warnings
19 passed 2 warnings 0 failed 8 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.mijnhostingpartner.nl, ns2.mijnhostingpartner.nl, ns3.mijnhostingpartner.nl, ns4.mijnhostingpartner.nl

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.mijnhostingpartner.nl, ns2.mijnhostingpartner.nl, ns3.mijnhostingpartner.nl, ns4.mijnhostingpartner.nl
NS in the zone
ns1.mijnhostingpartner.nl, ns2.mijnhostingpartner.nl, ns3.mijnhostingpartner.nl, ns4.mijnhostingpartner.nl
NameserverAddressesNetwork (AS)Glue
ns1.mijnhostingpartner.nl185.136.96.66 2a06:fb00:1::1:66AS203391 CLOUDNSNET - Cloud DNS Ltd, BG AS203391 CLOUDNSNET - Cloud DNS Ltd, BG-
ns2.mijnhostingpartner.nl185.136.97.66 2a06:fb00:1::2:66AS203391 CLOUDNSNET - Cloud DNS Ltd, BG AS203391 CLOUDNSNET - Cloud DNS Ltd, BG-
ns3.mijnhostingpartner.nl185.136.98.66 2a06:fb00:1::3:66AS203391 CLOUDNSNET - Cloud DNS Ltd, BG AS203391 CLOUDNSNET - Cloud DNS Ltd, BG-
ns4.mijnhostingpartner.nl185.136.99.66 2a06:fb00:1::4:66AS203391 CLOUDNSNET - Cloud DNS Ltd, BG AS203391 CLOUDNSNET - Cloud DNS Ltd, BG-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.mijnhostingpartner.nl, ns2.mijnhostingpartner.nl, ns3.mijnhostingpartner.nl, ns4.mijnhostingpartner.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.
  • i
    One address family in one network
    all IPv6 addresses are in 2a06:fb00:1::/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 (AS203391 (CLOUDNSNET - Cloud DNS Ltd, BG): 8 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.mijnhostingpartner.nl 185.136.96.66NOERROR, 3 ms, authoritativenoyes / yesrefusedde3-1
ns1.mijnhostingpartner.nl 2a06:fb00:1::1:66NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-1
ns2.mijnhostingpartner.nl 185.136.97.66NOERROR, 3 ms, authoritativenoyes / yesrefusedde3-1
ns2.mijnhostingpartner.nl 2a06:fb00:1::2:66NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-1
ns3.mijnhostingpartner.nl 185.136.98.66NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-1
ns3.mijnhostingpartner.nl 2a06:fb00:1::3:66NOERROR, 7 ms, authoritativenoyes / yesrefusedde3-1
ns4.mijnhostingpartner.nl 185.136.99.66NOERROR, 3 ms, authoritativenoyes / yesrefusedde3-1
ns4.mijnhostingpartner.nl 2a06:fb00:1::4:66NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-1

Checks

  • ✓ All respond #14
    All 8 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.mijnhostingpartner.nl: "de3-1"; ns2.mijnhostingpartner.nl: "de3-1"; ns3.mijnhostingpartner.nl: "de3-1"; ns4.mijnhostingpartner.nl: "de3-1".
    #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 2026050301 · primary ns1.mijnhostingpartner.nl

Found

Primary (MNAME)
ns1.mijnhostingpartner.nl
Contact (RNAME)
hostmaster.mijnpartnergroep.nl
Serial
2026050301
Refresh / retry
10800 s / 3600 s
Expire
777600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.mijnhostingpartner.nl (185.136.96.66)2026050301
ns1.mijnhostingpartner.nl (2a06:fb00:1::1:66)2026050301
ns2.mijnhostingpartner.nl (185.136.97.66)2026050301
ns2.mijnhostingpartner.nl (2a06:fb00:1::2:66)2026050301
ns3.mijnhostingpartner.nl (185.136.98.66)2026050301
ns3.mijnhostingpartner.nl (2a06:fb00:1::3:66)2026050301
ns4.mijnhostingpartner.nl (185.136.99.66)2026050301
ns4.mijnhostingpartner.nl (2a06:fb00:1::4:66)2026050301

Checks

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

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

warn

13 records at the apex

Found

Read from
185.136.96.66:53
TypeValueTTL
SOAns1.mijnhostingpartner.nl. hostmaster.mijnpartnergroep.nl. 2026050301 10800 3600 777600 36003600
NSns4.mijnhostingpartner.nl.3600
NSns3.mijnhostingpartner.nl.3600
NSns1.mijnhostingpartner.nl.3600
NSns2.mijnhostingpartner.nl.3600
A185.41.125.1330
MX5 mx3.mijnhostingpartner.nl.3600
MX5 mx2.mijnhostingpartner.nl.3600
MX20 mx1.mijnhostingpartner.nl.3600
MX10 mx4.mijnhostingpartner.nl.3600
MX10 mx5.mijnhostingpartner.nl.3600
TXT"dyn"3600
TXT"v=spf1 a include:spf.mijnhostingpartner.nl ~all"3600

Checks

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