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

dns112.ovh.net, ns112.ovh.net

Found

Parent zone: be
Delegation from: a.nsset.be (194.0.6.1)
NS at the parent: dns112.ovh.net, ns112.ovh.net
NS in the zone: dns112.ovh.net, ns112.ovh.net

Nameserver	Addresses	Network (AS)	Glue
dns112.ovh.net	5.196.45.209 2001:41d0:d01:600::2	AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR	-
ns112.ovh.net	5.135.80.109 2001:41d0:b01::2	AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR	-

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns112.ovh.net, ns112.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.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
dns112.ovh.net 5.196.45.209	NOERROR, 16 ms, authoritative	no	yes / yes	refused	-
dns112.ovh.net 2001:41d0:d01:600::2	NOERROR, 16 ms, authoritative	no	yes / yes	refused	-
ns112.ovh.net 5.135.80.109	NOERROR, 15 ms, authoritative	no	yes / yes	refused	-
ns112.ovh.net 2001:41d0:b01::2	NOERROR, 19 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 2092591214 · primary dns112.ovh.net

Found

Primary (MNAME): dns112.ovh.net
Contact (RNAME): tech.ovh.net
Serial: 2092591214
Refresh / retry: 86400 s / 3600 s
Expire: 3600000 s
Negative TTL: 300 s

Serial per nameserver

Nameserver	Serial
dns112.ovh.net (5.196.45.209)	2092591214
dns112.ovh.net (2001:41d0:d01:600::2)	2092591214
ns112.ovh.net (5.135.80.109)	2092591214
ns112.ovh.net (2001:41d0:b01::2)	2092591214

Checks

✓ Serial 2092591214 everywhere #22

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

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

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

The SOA RNAME tech.ovh.net means tech@ovh.net.
✓ Timestamp serial #26

The serial 2092591214 is a Unix timestamp (2036-04-23 19:20 UTC).

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: 20 November 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
7676	RSASHA256 (8)	SHA256 28291BD360E5DADC…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
16348	ZSK (256)	RSASHA256 (8)
27955	ZSK (256)	RSASHA256 (8)
7676	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 7676 (SHA256).
✓ Modern algorithms #29

Key algorithms: RSASHA256 (8).
✓ Signatures valid until 2026-11-20 #30

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

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

Records

info

9 records at the apex

Found

Read from: 5.196.45.209:53

Type	Value	TTL
SOA	dns112.ovh.net. tech.ovh.net. 2092591214 86400 3600 3600000 300	3600
NS	dns112.ovh.net.	3600
NS	ns112.ovh.net.	3600
A	87.98.154.146	3600
MX	100 mx3.mail.ovh.net.	3600
MX	5 mx2.mail.ovh.net.	3600
MX	1 mx1.mail.ovh.net.	3600
TXT	"v=spf1 include:mx.ovh.com ~all"	600
TXT	"1\|www.be-peps.be"	600

Checks

✓ 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