maartenbaert.be

Checked 22 October 2026, 06:50 UTC · via 8.8.8.8
!Passed with warnings
20 passed 2 warnings 0 failed 7 info

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

dns101.ovh.net, ns101.ovh.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
dns101.ovh.net, ns101.ovh.net
NS in the zone
dns101.ovh.net, ns101.ovh.net
NameserverAddressesNetwork (AS)Glue
dns101.ovh.net5.196.38.125 2001:41d0:d00:fb00::2AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
ns101.ovh.net5.135.53.37 2001:41d0:b00:f500::2AS16276 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: dns101.ovh.net, ns101.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

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns101.ovh.net 5.196.38.125NOERROR, 17 ms, authoritativenoyes / yesrefused-
dns101.ovh.net 2001:41d0:d00:fb00::2NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns101.ovh.net 5.135.53.37NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns101.ovh.net 2001:41d0:b00:f500::2NOERROR, 16 ms, authoritativenoyes / yesrefused-

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

warn

serial 2092622450 · primary dns101.ovh.net

Found

Primary (MNAME)
dns101.ovh.net
Contact (RNAME)
tech.ovh.net
Serial
2092622450
Refresh / retry
86400 s / 3600 s
Expire
3600000 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
dns101.ovh.net (5.196.38.125)2092622450
dns101.ovh.net (2001:41d0:d00:fb00::2)2092622450
ns101.ovh.net (5.135.53.37)2092622450
ns101.ovh.net (2001:41d0:b00:f500::2)2092622450

Checks

  • ✓ Serial 2092622450 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 dns101.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 2092622450 is a Unix timestamp (2036-04-24 04:00 UTC).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

info

11 records at the apex

Found

Read from
5.196.38.125:53
TypeValueTTL
SOAdns101.ovh.net. tech.ovh.net. 2092622450 86400 3600 3600000 60300
NSdns101.ovh.net.300
NSns101.ovh.net.300
A159.173.134.12300
AAAA2001:41d0:20a:800::18b2300
MX5 alt1.aspmx.l.google.com.300
MX10 alt3.aspmx.l.google.com.300
MX1 aspmx.l.google.com.300
MX5 alt2.aspmx.l.google.com.300
MX10 alt4.aspmx.l.google.com.300
TXT"v=spf1 include:_spf.google.com ~all"600

Checks

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