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

nsauth.myrootnet.com, nsauth.myrootnet.nl

Found

Parent zone: be
Delegation from: a.nsset.be (194.0.6.1)
NS at the parent: nsauth.myrootnet.com, nsauth.myrootnet.nl
NS in the zone: nsauth.myrootnet.com, nsauth.myrootnet.nl

Nameserver	Addresses	Network (AS)	Glue
nsauth.myrootnet.com	81.85.60.5 2a0b:3100:200::5	AS8455 ATOM86-AS - atom86 BV, NL AS8455 ATOM86-AS - atom86 BV, NL	-
nsauth.myrootnet.nl	185.173.20.5 2a0b:3100:53::10	AS12859 NL-BIT - BIT BV, NL AS12859 NL-BIT - BIT BV, NL	-

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: nsauth.myrootnet.com, nsauth.myrootnet.nl.

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

The nameservers are spread over: AS12859 (NL-BIT - BIT BV, NL): 2 addresses; AS8455 (ATOM86-AS - atom86 BV, NL): 2 addresses.
✓ Nameserver names under 2 TLDs #12

Nameserver names use the TLDs .com, .nl.
✓ All reachable over IPv6 #13

Every nameserver has an IPv6 address.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
nsauth.myrootnet.com 81.85.60.5	NOERROR, 10 ms, authoritative	no	yes / yes	refused	-
nsauth.myrootnet.com 2a0b:3100:200::5	NOERROR, 10 ms, authoritative	no	yes / yes	refused	-
nsauth.myrootnet.nl 185.173.20.5	NOERROR, 12 ms, authoritative	no	yes / yes	refused	-
nsauth.myrootnet.nl 2a0b:3100:53::10	NOERROR, 11 ms, authoritative	no	yes / yes	refused	-

Checks

✓ All respond #14

All 4 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 2026102201 · primary nsauth.myrootnet.com

Found

Primary (MNAME): nsauth.myrootnet.com
Contact (RNAME): root.rootnet.nl
Serial: 2026102201
Refresh / retry: 14400 s / 3600 s
Expire: 1209600 s
Negative TTL: 3600 s

Serial per nameserver

Nameserver	Serial
nsauth.myrootnet.com (81.85.60.5)	2026102201
nsauth.myrootnet.com (2a0b:3100:200::5)	2026102201
nsauth.myrootnet.nl (185.173.20.5)	2026102201
nsauth.myrootnet.nl (2a0b:3100:53::10)	2026102201

Checks

✓ Serial 2026102201 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 4h, retry 1h, expire 14d, negative TTL 1h.
✓ Primary is a public nameserver #24

The primary nameserver nsauth.myrootnet.com is one of the listed nameservers.
✓ Contact root@rootnet.nl #25

The SOA RNAME root.rootnet.nl means root@rootnet.nl.
✓ Date-based serial #26

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

DNSSEC

pass

Signed, DS published at parent

Found

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

DS at the parent

Key tag	Algorithm	Digest	Matches a key
9072	ECDSAP256SHA256 (13)	SHA256 86A7721A195B4A05…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
9072	KSK (257)	ECDSAP256SHA256 (13)

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 9072 (SHA256).
✓ Modern algorithms #29

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

The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
✓ NSEC3 as recommended #31

The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

8 records at the apex

Found

Read from: 81.85.60.5:53

Type	Value	TTL
SOA	nsauth.myrootnet.com. root.rootnet.nl. 2026102201 14400 3600 1209600 3600	600
NS	nsauth.myrootnet.nl.	600
NS	nsauth.myrootnet.com.	600
A	185.173.21.101	300
AAAA	2a0b:3100:20::66	300
MX	10 mailfilter01.myrootnet.nl.	600
MX	20 mailfilter02.myrootnet.nl.	600
TXT	"v=spf1 a mx ip4:185.173.21.101 ip6:2a0b:3100:20::66 include:mailfilter.myrootnet.nl ~all"	300

Checks

✓ TTLs within range #32

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