walloniebelgietoerisme.be

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

ns-157-b.gandi.net, ns-29-c.gandi.net, ns-82-a.gandi.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns-157-b.gandi.net, ns-29-c.gandi.net, ns-82-a.gandi.net
NS in the zone
ns-157-b.gandi.net, ns-29-c.gandi.net, ns-82-a.gandi.net
NameserverAddressesNetwork (AS)Glue
ns-157-b.gandi.net213.167.230.158 2001:4b98:aaab::9eAS209453 GANDI-LIVEDNS - GANDI SAS, FR AS209453 GANDI-LIVEDNS - GANDI SAS, FR-
ns-29-c.gandi.net217.70.187.30 2604:3400:aaac::1eAS209453 GANDI-LIVEDNS - GANDI SAS, FR AS209453 GANDI-LIVEDNS - GANDI SAS, FR-
ns-82-a.gandi.net173.246.100.83 2001:4b98:aaaa::53AS209453 GANDI-LIVEDNS - GANDI SAS, FR AS209453 GANDI-LIVEDNS - GANDI SAS, FR-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns-157-b.gandi.net, ns-29-c.gandi.net, ns-82-a.gandi.net.
  • ✓ 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 3 IPv4 /24s and 3 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS209453 (GANDI-LIVEDNS - GANDI SAS, FR): 6 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

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns-157-b.gandi.net 213.167.230.158NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns-157-b.gandi.net 2001:4b98:aaab::9eNOERROR, 4 ms, authoritativenoyes / yesrefused-
ns-29-c.gandi.net 217.70.187.30NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns-29-c.gandi.net 2604:3400:aaac::1eNOERROR, 7 ms, authoritativenoyes / yesrefused-
ns-82-a.gandi.net 173.246.100.83NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns-82-a.gandi.net 2001:4b98:aaaa::53NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 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

info

serial 1792627200 · primary ns1.gandi.net

Found

Primary (MNAME)
ns1.gandi.net
Contact (RNAME)
hostmaster.gandi.net
Serial
1792627200
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns-157-b.gandi.net (213.167.230.158)1792627200
ns-157-b.gandi.net (2001:4b98:aaab::9e)1792627200
ns-29-c.gandi.net (217.70.187.30)1792627200
ns-29-c.gandi.net (2604:3400:aaac::1e)1792627200
ns-82-a.gandi.net (173.246.100.83)1792627200
ns-82-a.gandi.net (2001:4b98:aaaa::53)1792627200

Checks

  • ✓ Serial 1792627200 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 3h.
  • i
    Hidden master
    The primary nameserver ns1.gandi.net is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact hostmaster@gandi.net #25
    The SOA RNAME hostmaster.gandi.net means hostmaster@gandi.net.
  • ✓ Timestamp serial #26
    The serial 1792627200 is a Unix timestamp (2026-10-22 00: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

12 records at the apex

Found

Read from
213.167.230.158:53
TypeValueTTL
SOAns1.gandi.net. hostmaster.gandi.net. 1792627200 10800 3600 604800 1080010800
NSns-82-a.gandi.net.10800
NSns-157-b.gandi.net.10800
NSns-29-c.gandi.net.10800
A154.52.48.4710800
MX10 esa1.hc1425-40.eu.iphmx.com.3600
MX20 esa2.hc1425-40.eu.iphmx.com.3600
TXT"MS=ms58568567"10800
TXT"_bzt55of0ciu5wf71yw5u27yjkkjm18j"10800
TXT"v=spf1 a mx ip4:213.181.52.96 ip4:213.246.198.132 ip4:213.246.198.130 ip4:23.90.119.222 ip4:23.90.122.208 include:servers.mcsv.net -all"10800
TXT"pn2817mm3vjhn56k0026t7kr2kdw0mnx"10800
TXT"atlassian-domain-verification=wAf/Hh3s2vPAsCDPIAzBZnrX/EDgQn1CyyujiYL54YNo/qZZ5xheyDiAo0MveFBp"10800

Checks

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