Domain report: oudenburg.be

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

Nameserver	Addresses	Network (AS)	Glue
ns53.be	94.237.57.255 49.13.15.43 2a04:3541:1000:500:f43f:26ff:fe87:58f4 2a01:4f8:c17:e57b::1	AS202053 UPCLOUD - UpCloud Ltd, FI AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS202053 UPCLOUD - UpCloud Ltd, FI AS24940 HETZNER-AS - Hetzner Online GmbH, DE	-
ns53.io	194.62.98.213 185.70.198.56 2a04:3542:8000:1000:f43f:26ff:fe87:67d1 2a04:3544:8000:1000:f43f:26ff:fe87:3d42	AS202053 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

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns53.be 94.237.57.255	NOERROR, 24 ms, authoritative	no	yes / yes	refused	-
ns53.be 49.13.15.43	NOERROR, 4 ms, authoritative	no	yes / yes	refused	-
ns53.be 2a04:3541:1000:500:f43f:26ff:fe87:58f4	NOERROR, 32 ms, authoritative	no	yes / yes	refused	-
ns53.be 2a01:4f8:c17:e57b::1	NOERROR, 5 ms, authoritative	no	yes / yes	refused	-
ns53.io 194.62.98.213	NOERROR, 33 ms, authoritative	no	yes / yes	refused	-
ns53.io 185.70.198.56	NOERROR, 58 ms, authoritative	no	yes / yes	refused	-
ns53.io 2a04:3542:8000:1000:f43f:26ff:fe87:67d1	NOERROR, 34 ms, authoritative	no	yes / yes	refused	-
ns53.io 2a04:3544:8000:1000:f43f:26ff:fe87:3d42	NOERROR, 123 ms, authoritative	no	yes / yes	refused	-

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 2026102201 · primary ns53.be

Found

Primary (MNAME): ns53.be
Contact (RNAME): hostmaster.oudenburg.be
Serial: 2026102201
Refresh / retry: 7200 s / 7200 s
Expire: 1209600 s
Negative TTL: 300 s

Serial per nameserver

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

Checks

✓ Serial 2026102201 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 5m.

#23
✓ Primary is a public nameserver #24

The primary nameserver ns53.be is one of the listed nameservers.
✓ Contact hostmaster@oudenburg.be #25

The SOA RNAME hostmaster.oudenburg.be means hostmaster@oudenburg.be.
✓ Date-based serial #26

The serial 2026102201 follows the YYYYMMDDnn convention (2026-10-22).

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC3
NSEC3: 1 iterations, 4-byte salt
Signatures valid until: 5 November 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
52181	RSASHA256 (8)	SHA256 E1DDE4E54A78053E…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
52181	KSK (257)	RSASHA256 (8)
52815	ZSK (256)	RSASHA256 (8)

Checks

✓ Signed and validated #27

The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
✓ DS matches a key #28

The DS record at the parent matches a key in the zone: key tag 52181 (SHA256).
✓ Modern algorithms #29

Key algorithms: RSASHA256 (8).
✓ Signatures valid until 2026-11-05 #30

The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
!

NSEC3 with extra iterations or salt

NSEC3 uses 1 iteration and a 4-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.

#31

Records

warn

12 records at the apex

Found

Read from: 94.237.57.255:53

Type	Value	TTL
SOA	ns53.be. hostmaster.oudenburg.be. 2026102201 7200 7200 1209600 300	299
NS	ns53.io.	299
NS	ns53.be.	299
A	193.110.252.76	300
AAAA	2a02:5940:4001::200	300
MX	10 oudenburg-be.mail.protection.outlook.com.	300
TXT	"MS=ms77761100"	300
TXT	"MS=3C1436FB2E60D368139EDF42C2851C3B13D2204B"	300
TXT	"mandrill_verify.9SNRd9v99Be5z9biCq5D0Q"	300
TXT	"google-site-verification=FoulGIQrvEs-CvVAjbqZGr5nQyApmV-MK0XnUotse_8"	300
TXT	"v=spf1 a mx ip4:78.24.169.220/32 a:mail.twikey.com include:spf.lcp.be include:spf.protection.outlook.com include:oclcspf3.oclc.org include:spf.facilitator.e2e.be include:_spf.bibliotheek.be -all"	300
TXT	"cbtpltvviobkv5aoel05ll1cpa"	300

Checks

!

Very low TTLs

These records have a TTL below 5m, causing extra queries and slower lookups: NS (4m59s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 4m59s; resolvers may use either.

#32
✓ 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