visitmons.be

Checked 22 October 2026, 07:21 UTC · via 8.8.8.8
!Passed with warnings
22 passed 1 warning 0 failed 6 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

dns14.ovh.net, ns14.ovh.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
dns14.ovh.net, ns14.ovh.net
NS in the zone
dns14.ovh.net, ns14.ovh.net
NameserverAddressesNetwork (AS)Glue
dns14.ovh.net5.135.99.133 2001:41d0:d00:f300::2AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
ns14.ovh.net5.39.113.141 2001:41d0:b00:ed00::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: dns14.ovh.net, ns14.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
dns14.ovh.net 5.135.99.133NOERROR, 16 ms, authoritativenoyes / yesrefused-
dns14.ovh.net 2001:41d0:d00:f300::2NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns14.ovh.net 5.39.113.141NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns14.ovh.net 2001:41d0:b00:ed00::2NOERROR, 15 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

pass

serial 2025091110 · primary dns14.ovh.net

Found

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

Serial per nameserver

NameserverSerial
dns14.ovh.net (5.135.99.133)2025091110
dns14.ovh.net (2001:41d0:d00:f300::2)2025091110
ns14.ovh.net (5.39.113.141)2025091110
ns14.ovh.net (2001:41d0:b00:ed00::2)2025091110

Checks

  • ✓ Serial 2025091110 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 dns14.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 2025091110 follows the YYYYMMDDnn convention (2025-09-11).

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

9 records at the apex

Found

Read from
5.135.99.133:53
TypeValueTTL
SOAdns14.ovh.net. tech.ovh.net. 2025091110 86400 3600 3600000 3003600
NSns14.ovh.net.3600
NSdns14.ovh.net.3600
A76.76.21.213600
MX10 visitmons-be.mail.protection.outlook.com.3600
TXT"v=spf1 include:spf.protection.outlook.com -all"3600
TXT"MS=ms40772467"3600
TXT"google-site-verification=LXlMg8EhZ-qtvh4O0uFegVO2mwcM7tQyE5-50XHT2X4"3600
TXT"google-site-verification=LOC463hO81-O9fgABSh4tifyyelNMQs4NjAni72VINg"3600

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