luxen.be

Checked 22 October 2026, 06:50 UTC · via 8.8.8.8
!Passed with warnings
21 passed 1 warning 0 failed 7 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.ydomain.com, ns2.ydomain.com

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.ydomain.com, ns2.ydomain.com
NS in the zone
ns1.ydomain.com, ns2.ydomain.com
NameserverAddressesNetwork (AS)Glue
ns1.ydomain.com37.27.254.174AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns2.ydomain.com2a01:4f9:c014:efb::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.ydomain.com, ns2.ydomain.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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 1 IPv4 /24 and 1 IPv6 /48.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 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 .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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.ydomain.com.
    #13

Nameservers

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.ydomain.com 37.27.254.174NOERROR, 25 ms, authoritativenoyes / yesrefused-
ns2.ydomain.com 2a01:4f9:c014:efb::1NOERROR, 25 ms, authoritativenoyes / yesrefused-

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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2026100701 · primary ns1.ydomain.com

Found

Primary (MNAME)
ns1.ydomain.com
Contact (RNAME)
hostmaster.ydomain.com
Serial
2026100701
Refresh / retry
3600 s / 900 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.ydomain.com (37.27.254.174)2026100701
ns2.ydomain.com (2a01:4f9:c014:efb::1)2026100701

Checks

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

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

9 records at the apex

Found

Read from
37.27.254.174:53
TypeValueTTL
SOAns1.ydomain.com. hostmaster.ydomain.com. 2026100701 3600 900 604800 3003600
NSns1.ydomain.com.3600
NSns2.ydomain.com.3600
A37.27.254.1743600
AAAA2a01:4f9:c014:efb::13600
MX10 luxen.be.3600
TXT"v=spf1 ip4:37.27.254.174 ip6:2a01:4f9:c014:efb::1 -all"3600
CAA0 issue "letsencrypt.org"3600
CAA0 issue "sectigo.com"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, AAAA 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org, sectigo.com.