Domain report: mumm.ac.be

Registration

info

.be country-code

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. Domains are registered under the public suffix .ac.be.

#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

info

ns1.belnet.be, ns2.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	-
ns2.belnet.be	193.190.182.40 2001:6a8:3c80:c000::40	AS2611 BELNET - BELNET, BE AS2611 BELNET - BELNET, BE	-

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.belnet.be, ns2.belnet.be.

#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.
i

One address family in one network

all IPv6 addresses are in 2001:6a8:3c80::/48, while the other address family is spread over several networks.

#10
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS2611 (BELNET - BELNET, BE): 4 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 .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.

fail

0 of 4 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.belnet.be 193.190.198.14	SERVFAIL, 17 ms, NOT authoritative	no	no / yes	refused	For me to know, for you to guess!
ns1.belnet.be 2001:6a8:3c80::14	SERVFAIL, 13 ms, NOT authoritative	no	no / yes	refused	For me to know, for you to guess!
ns2.belnet.be 193.190.182.40	SERVFAIL, 13 ms, NOT authoritative	no	no / yes	refused	-
ns2.belnet.be 2001:6a8:3c80:c000::40	SERVFAIL, 18 ms, NOT authoritative	no	no / yes	refused	-

✓ All respond #14

All 4 nameserver addresses answered.
✗

Lame delegation

These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns1.belnet.be (193.190.198.14): SERVFAIL, authoritative=false; ns1.belnet.be (2001:6a8:3c80::14): SERVFAIL, authoritative=false; ns2.belnet.be (193.190.182.40): SERVFAIL, authoritative=false; ns2.belnet.be (2001:6a8:3c80:c000::40): SERVFAIL, authoritative=false.

#15
✓ 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!".

#17
✓ Zone transfers refused #18

No nameserver allows a zone transfer to the public.
✗

No DNS over TCP

DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.belnet.be (193.190.198.14): ; ns1.belnet.be (2001:6a8:3c80::14): ; ns2.belnet.be (193.190.182.40): ; ns2.belnet.be (2001:6a8:3c80:c000::40): .

#19
✓ EDNS supported #20

All nameservers support EDNS(0).
✓ Public addresses #21

All nameserver addresses are publicly routable.

warn

Not signed