lifepartner.be

Checked 22 October 2026, 06:50 UTC · via 8.8.8.8
!Passed with warnings
17 passed 6 warnings 0 failed 6 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

warn

ns1.value-domain.com, ns2.value-domain.com, ns3.value-domain.com

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.value-domain.com, ns2.value-domain.com, ns3.value-domain.com
NS in the zone
ns1.value-domain.com, ns2.value-domain.com
NameserverAddressesNetwork (AS)Glue
ns1.value-domain.com172.64.52.38AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
ns2.value-domain.com172.64.53.3AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
ns3.value-domain.com (parent only)172.64.52.38AS13335 CLOUDFLARENET - Cloudflare, Inc., US-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.value-domain.com, ns2.value-domain.com, ns3.value-domain.com.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns3.value-domain.com. ns1.value-domain.com, ns2.value-domain.com, ns3.value-domain.com report NS ns1.value-domain.com ns2.value-domain.com.
    #7
  • ✓ 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 (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 3 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 .com
    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

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.value-domain.com 172.64.52.38NOERROR, 298 ms, authoritativenoyes / yesrefused2026.10.8
ns2.value-domain.com 172.64.53.3NOERROR, 293 ms, authoritativenoyes / yesrefused2026.10.8
ns3.value-domain.com 172.64.52.38NOERROR, 294 ms, authoritativenoyes / yesrefused2026.10.8

Checks

  • ✓ All respond #14
    All 3 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.value-domain.com: "2026.10.8"; ns2.value-domain.com: "2026.10.8"; ns3.value-domain.com: "2026.10.8". 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 2020082618 · primary ns1.value-domain.com

Found

Primary (MNAME)
ns1.value-domain.com
Contact (RNAME)
hostmaster.lifepartner.be
Serial
2020082618
Refresh / retry
3600 s / 900 s
Expire
604800 s
Negative TTL
120 s

Serial per nameserver

NameserverSerial
ns1.value-domain.com (172.64.52.38)2020082618
ns2.value-domain.com (172.64.53.3)2020082618
ns3.value-domain.com (172.64.52.38)2020082618

Checks

  • ✓ Serial 2020082618 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 2m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 15m, expire 7d, negative TTL 2m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.value-domain.com is one of the listed nameservers.
  • ✓ Contact hostmaster@lifepartner.be #25
    The SOA RNAME hostmaster.lifepartner.be means hostmaster@lifepartner.be.
  • ✓ Date-based serial #26
    The serial 2020082618 follows the YYYYMMDDnn convention (2020-08-26).

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

5 records at the apex

Found

Read from
172.64.52.38:53
TypeValueTTL
SOAns1.value-domain.com. hostmaster.lifepartner.be. 2020082618 3600 900 604800 120120
NSns1.value-domain.com.120
NSns2.value-domain.com.120
A160.251.151.57120
MX10 lifepartner.be.120

Checks

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