visittournai.be

Checked 22 October 2026, 07:21 UTC · via 8.8.8.8
!Passed with warnings
26 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

dns104.ovh.net, ns104.ovh.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
dns104.ovh.net, ns104.ovh.net
NS in the zone
dns104.ovh.net, ns104.ovh.net
NameserverAddressesNetwork (AS)Glue
dns104.ovh.net5.196.39.113 2001:41d0:d00:fe00::2AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
ns104.ovh.net5.135.60.17 2001:41d0:b00:f800::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: dns104.ovh.net, ns104.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
dns104.ovh.net 5.196.39.113NOERROR, 16 ms, authoritativenoyes / yesrefused-
dns104.ovh.net 2001:41d0:d00:fe00::2NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns104.ovh.net 5.135.60.17NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns104.ovh.net 2001:41d0:b00:f800::2NOERROR, 19 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 2092004593 · primary dns104.ovh.net

Found

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

Serial per nameserver

NameserverSerial
dns104.ovh.net (5.196.39.113)2092004593
dns104.ovh.net (2001:41d0:d00:fe00::2)2092004593
ns104.ovh.net (5.135.60.17)2092004593
ns104.ovh.net (2001:41d0:b00:f800::2)2092004593

Checks

  • ✓ Serial 2092004593 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 dns104.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 2092004593 is a Unix timestamp (2036-04-17 00:23 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
13 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
46709RSASHA256 (8)SHA256 550C0A481F86B9A7…yes

DNSKEY in the zone

Key tagRoleAlgorithm
21850ZSK (256)RSASHA256 (8)
46709KSK (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 46709 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-13 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-13 18:03 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

warn

25 records at the apex

Found

Read from
5.196.39.113:53
TypeValueTTL
SOAdns104.ovh.net. tech.ovh.net. 2092004593 86400 3600 3600000 300600
NSns104.ovh.net.600
NSdns104.ovh.net.600
A149.202.245.17660
MX1 mx1.ovh.net.600
MX100 mxb.ovh.net.600
MX5 mx2.ovh.net.600
TXT"globalsign-domain-verification=Pd-eIzlw284gAYzgVLlPRVuTFmhtTB9TBiyu8JBK8H"600
TXT"google-site-verification=wsfoDXt5-64tLMKsEOLGzW_cJzrhMPCcnih5kMMJb38"600
TXT"globalsign-domain-verification=D2tKGaOC7Gtc0thRFaT0BQxx6eCcrr4z6VV8T9fihK"600
TXT"google-site-verification=2DO8FJ0Upm0kKxplwQqNNJ71f1oBl5e7UvEcpdN1_NM"600
TXT"v=spf1 include:mx.ovh.com ~all"600
TXT"705r+LwX1S4v2jU79TkTSWwZ371Ar+tPXKG3x+xs738="600
TXT"_globalsign-domain-verification=wSGCFSBOSQOnktqiGFbT2xn9_N4KGuegGk_uUX3hXx"600
TXT"_globalsign-domain-verification=v1N17oPR36vW10wszI7z9U2tzF62rMbt0q7gs7_KUG"600
TXT"_globalsign-domain-verification=bQZ2B0uqZGu58q76KMyYuGEUhYZo0wwBaoLsDAKZs5"600
TXT"4|https://www.visittournai.be"600
TXT"google-site-verification=bQmaCelzZDCGxsIZDp_e2m7Zua-JNW_kyZXHMzZ3W3E"600
TXT"_globalsign-domain-verification=BSwUihjkSCATQOj3UkDLhXYGdYKmMvbQ_RHWMkAHOh"600
TXT"globalsign-domain-verification=MM915nUvFNTUkXA4x9lZYjsyeIQ2wTSQQF4vTMnd-M"600
TXT"globalsign-domain-verification=05_AVBbK6-p0rsKzhsoQx-DyXkP531K003NNTG7mE8"600
TXT"_globalsign-domain-verification=8GuqqWDfbfmbVR_BELOPrLhAEys8I2qXox3kK6EG22"600
TXT"yR7SbMlFE7Sg1Ux7ZPd7vhFRoCphNPWE"600
TXT"_globalsign-domain-verification=AlVu04tvS5xvz0fooPc_lnFermWlaX_CwaK2EiYIPS"600
TXT"facebook-domain-verification=5oncn4oc1d44qx9aya7ftwtis8j0vh"600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 10m; resolvers may use either.
    #32
  • ✓ 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