Domain report: iweps.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

warn

ns1.belnet.be, ns2.belnet.be, nsmaster.belnet.be

Found

Parent zone: be
Delegation from: a.nsset.be (194.0.6.1)
NS at the parent: ns1.belnet.be, ns2.belnet.be, nsmaster.belnet.be
NS in the zone: ns1.belnet.be, ns2.belnet.be, ns3.belnet.be, nsmaster.belnet.be

Nameserver	Addresses	Network (AS)	Glue
ns1.belnet.be	193.190.198.14 2001:6a8:3c80::14	AS2611 BELNET - BELNET, BE AS2611 BELNET - BELNET, BE	193.190.198.14 2001:6a8:3c80::14
ns2.belnet.be	193.190.182.40 2001:6a8:3c80:c000::40	AS2611 BELNET - BELNET, BE AS2611 BELNET - BELNET, BE	193.190.182.40 2001:6a8:3c80:c000::40
ns3.belnet.be (zone only)	194.58.196.32 2a01:3f1:832::53	AS8674 NETNOD-IX - Netnod AB, SE AS8674 NETNOD-IX - Netnod AB, SE	-
nsmaster.belnet.be	193.190.198.14 2001:6a8:3c80::14	AS2611 BELNET - BELNET, BE AS2611 BELNET - BELNET, BE	-

Checks

✓ 3 nameservers #6

Delegated to ns1.belnet.be, ns2.belnet.be, nsmaster.belnet.be.
!

NS sets differ

The nameservers at the parent and in the zone should be the same. Only in the zone: ns3.belnet.be. ns1.belnet.be, ns2.belnet.be, ns3.belnet.be, nsmaster.belnet.be report NS ns1.belnet.be ns2.belnet.be ns3.belnet.be nsmaster.belnet.be.

#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 3 IPv4 /24s and 2 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS2611 (BELNET - BELNET, BE): 6 addresses; AS8674 (NETNOD-IX - Netnod AB, SE): 2 addresses.
i

All nameserver names under .be

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

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.belnet.be 193.190.198.14	NOERROR, 13 ms, authoritative	no	yes / yes	refused	For me to know, for you to guess!
ns1.belnet.be 2001:6a8:3c80::14	NOERROR, 17 ms, authoritative	no	yes / yes	refused	For me to know, for you to guess!
ns2.belnet.be 193.190.182.40	NOERROR, 13 ms, authoritative	no	yes / yes	refused	-
ns2.belnet.be 2001:6a8:3c80:c000::40	NOERROR, 13 ms, authoritative	no	yes / yes	refused	-
ns3.belnet.be 194.58.196.32	NOERROR, 9 ms, authoritative	no	yes / yes	refused	-
ns3.belnet.be 2a01:3f1:832::53	NOERROR, 9 ms, authoritative	no	yes / yes	refused	-
nsmaster.belnet.be 193.190.198.14	NOERROR, 13 ms, authoritative	no	yes / yes	refused	For me to know, for you to guess!
nsmaster.belnet.be 2001:6a8:3c80::14	NOERROR, 13 ms, authoritative	no	yes / yes	refused	For me to know, for you to guess!

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.belnet.be: "For me to know, for you to guess!"; nsmaster.belnet.be: "For me to know, for you to guess!".

#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 2026102201 · primary nsmaster.belnet.be

Found

Primary (MNAME): nsmaster.belnet.be
Contact (RNAME): hostmaster.iweps.be
Serial: 2026102201
Refresh / retry: 7200 s / 7200 s
Expire: 1209600 s
Negative TTL: 3600 s

Serial per nameserver

Nameserver	Serial
ns1.belnet.be (193.190.198.14)	2026102201
ns1.belnet.be (2001:6a8:3c80::14)	2026102201
ns2.belnet.be (193.190.182.40)	2026102201
ns2.belnet.be (2001:6a8:3c80:c000::40)	2026102201
ns3.belnet.be (194.58.196.32)	2026102201
ns3.belnet.be (2a01:3f1:832::53)	2026102201
nsmaster.belnet.be (193.190.198.14)	2026102201
nsmaster.belnet.be (2001:6a8:3c80::14)	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 1h.

#23
✓ Primary is a public nameserver #24

The primary nameserver nsmaster.belnet.be is one of the listed nameservers.
✓ Contact hostmaster@iweps.be #25

The SOA RNAME hostmaster.iweps.be means hostmaster@iweps.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
63427	RSASHA256 (8)	SHA256 B8F24C3A26BE08BE…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
35724	ZSK (256)	RSASHA256 (8)
63427	KSK (257)	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 63427 (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

info

11 records at the apex

Found

Read from: 193.190.198.14:53

Type	Value	TTL
SOA	nsmaster.belnet.be. hostmaster.iweps.be. 2026102201 7200 7200 1209600 3600	3600
NS	ns1.belnet.be.	300
NS	ns2.belnet.be.	300
NS	ns3.belnet.be.	300
NS	nsmaster.belnet.be.	300
A	34.128.147.192	3600
AAAA	2600:1901:0:7c26::	3600
MX	0 iweps-be.mail.protection.outlook.com.	3600
TXT	"brevo-code:ef029079c60826aa828b699d1ee73d53"	3600
TXT	"v=spf1 include:spf.protection.outlook.com ip4:193.191.178.33 ip4:193.191.178.34 ip6:2001:6a8:3980:10::80:41 include:spf.brevo.com ~all"	3600
TXT	"MS=ms76002163"	3600

Checks

✓ TTLs within range #32

TTLs: A 1h, AAAA 1h, MX 1h, NS 5m. The NS TTL at the parent is 1d and in the zone 5m; 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