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

#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

warn

ns1.belfla.be, ns2.belfla.be

Nameserver	Addresses	Network (AS)	Glue
ns1.belfla.be	185.105.158.35	AS204182 AWV-TELEMATICA - Ministeries van de Vlaamse Gemeenschap, BE	185.105.158.35
ns2.belfla.be	185.105.158.67	AS204182 AWV-TELEMATICA - Ministeries van de Vlaamse Gemeenschap, BE	185.105.158.67

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.belfla.be, ns2.belfla.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.
!

Nameservers in one network

all IPv4 addresses are in 185.105.158.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).

#10
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS204182 (AWV-TELEMATICA - Ministeries van de Vlaamse Gemeenschap, BE): 2 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
!

No IPv6

None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

#13

pass

2 of 2 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.belfla.be 185.105.158.35	NOERROR, 22 ms, authoritative	no	yes / yes	refused	-
ns2.belfla.be 185.105.158.67	NOERROR, 23 ms, authoritative	no	yes / yes	refused	-

✓ All respond #14

All 2 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.

pass

serial 2026082400 · primary ns1.belfla.be

Nameserver	Serial
ns1.belfla.be (185.105.158.35)	2026082400
ns2.belfla.be (185.105.158.67)	2026082400

✓ Serial 2026082400 everywhere #22

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

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

The primary nameserver ns1.belfla.be is one of the listed nameservers.
✓ Contact admin@belfla.be #25

The SOA RNAME admin.belfla.be means admin@belfla.be.
✓ Date-based serial #26

The serial 2026082400 follows the YYYYMMDDnn convention (2026-08-24).

warn

Not signed

info

9 records at the apex

✓ 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