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

info

dns100.ovh.net, ns100.ovh.net

Nameserver	Addresses	Network (AS)	Glue
dns100.ovh.net	5.135.250.177 2001:41d0:d00:fa00::2	AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR	-
ns100.ovh.net	5.135.44.185 2001:41d0:b00:f400::2	AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR	-

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns100.ovh.net, ns100.ovh.net.

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

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS16276 (OVH - OVH SAS, FR): 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 .net

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.

pass

4 of 4 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
dns100.ovh.net 5.135.250.177	NOERROR, 16 ms, authoritative	no	yes / yes	refused	-
dns100.ovh.net 2001:41d0:d00:fa00::2	NOERROR, 16 ms, authoritative	no	yes / yes	refused	-
ns100.ovh.net 5.135.44.185	NOERROR, 15 ms, authoritative	no	yes / yes	refused	-
ns100.ovh.net 2001:41d0:b00:f400::2	NOERROR, 15 ms, authoritative	no	yes / yes	refused	-

✓ 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.

warn

serial 2025062903 · primary dns100.ovh.net

✓ Serial 2025062903 everywhere #22

All nameservers serve the same version of the zone.
!

Unusual SOA timers

negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 1h, expire 1000h, negative TTL 1m.

#23
✓ Primary is a public nameserver #24

The primary nameserver dns100.ovh.net is one of the listed nameservers.
✓ Contact tech@ovh.net #25

The SOA RNAME tech.ovh.net means tech@ovh.net.
✓ Date-based serial #26

The serial 2025062903 follows the YYYYMMDDnn convention (2025-06-29).

warn

Not signed

info

5 records at the apex

✓ TTLs within range #32

TTLs: A 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