veurne.be

Checked 22 October 2026, 07:21 UTC · via 8.8.8.8
!Passed with warnings
23 passed 2 warnings 0 failed 4 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

ns53.be, ns53.io

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns53.be, ns53.io
NS in the zone
ns53.be, ns53.io
NameserverAddressesNetwork (AS)Glue
ns53.be94.237.57.255 49.13.15.43 2a04:3541:1000:500:f43f:26ff:fe87:58f4 2a01:4f8:c17:e57b::1AS202053 UPCLOUD - UpCloud Ltd, FI AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS202053 UPCLOUD - UpCloud Ltd, FI AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns53.io185.70.198.56 194.62.98.213 2a04:3544:8000:1000:f43f:26ff:fe87:3d42 2a04:3542:8000:1000:f43f:26ff:fe87:67d1AS202053 UPCLOUD - UpCloud Ltd, FI AS202053 UPCLOUD - UpCloud Ltd, FI AS202053 UPCLOUD - UpCloud Ltd, FI AS202053 UPCLOUD - UpCloud Ltd, FI-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns53.be, ns53.io.
    #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 4 IPv4 /24s and 4 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS202053 (UPCLOUD - UpCloud Ltd, FI): 6 addresses; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .be, .io.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns53.be 94.237.57.255NOERROR, 90 ms, authoritativenoyes / yesrefused-
ns53.be 49.13.15.43NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns53.be 2a04:3541:1000:500:f43f:26ff:fe87:58f4NOERROR, 24 ms, authoritativenoyes / yesrefused-
ns53.be 2a01:4f8:c17:e57b::1NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns53.io 185.70.198.56NOERROR, 122 ms, authoritativenoyes / yesrefused-
ns53.io 194.62.98.213NOERROR, 33 ms, authoritativenoyes / yesrefused-
ns53.io 2a04:3544:8000:1000:f43f:26ff:fe87:3d42NOERROR, 230 ms, authoritativenoyes / yesrefused-
ns53.io 2a04:3542:8000:1000:f43f:26ff:fe87:67d1NOERROR, 33 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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

warn

serial 2026070204 · primary ns53.be

Found

Primary (MNAME)
ns53.be
Contact (RNAME)
hostmaster.veurne.be
Serial
2026070204
Refresh / retry
7200 s / 7200 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns53.be (94.237.57.255)2026070204
ns53.be (49.13.15.43)2026070204
ns53.be (2a04:3541:1000:500:f43f:26ff:fe87:58f4)2026070204
ns53.be (2a01:4f8:c17:e57b::1)2026070204
ns53.io (185.70.198.56)2026070204
ns53.io (194.62.98.213)2026070204
ns53.io (2a04:3544:8000:1000:f43f:26ff:fe87:3d42)2026070204
ns53.io (2a04:3542:8000:1000:f43f:26ff:fe87:67d1)2026070204

Checks

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

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

10 records at the apex

Found

Read from
94.237.57.255:53
TypeValueTTL
SOAns53.be. hostmaster.veurne.be. 2026070204 7200 7200 1209600 36003600
NSns53.be.3600
NSns53.io.3600
A185.3.217.1773600
MX100 avas-backup.cloudemail.be.3600
MX10 avas.cloudemail.be.3600
TXT"brevo-code:3ff469f7d4862443a10fe4fd47070b3c"3600
TXT"MS=2EA339B28DFE390315FBFB95AA4715838504C012"3600
TXT"logmein-verification-code=f181eba1-f579-4f3d-885d-16a4dbb721d3"3600
TXT"v=spf1 mx a ip4:176.62.136.1 ip4:176.62.136.2 ip4:81.82.230.203 ip4:212.72.62.129/27 include:oclcspf3.oclc.org include:_spf.paddle.be include:spf.cloudemail.be 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.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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