namurtourisme.be

Checked 22 October 2026, 06:51 UTC · via 8.8.8.8
!Passed with warnings
21 passed 3 warnings 0 failed 5 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

warn

ns1.devpig.be, ns2.devpig.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.devpig.be, ns2.devpig.be
NS in the zone
ns1.devpig.be, ns2.devpig.be
NameserverAddressesNetwork (AS)Glue
ns1.devpig.be176.31.149.32AS16276 OVH - OVH SAS, FR-
ns2.devpig.be51.75.151.132AS16276 OVH - OVH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.devpig.be, ns2.devpig.be.
    #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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16276 (OVH - OVH SAS, FR): 2 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 .be
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.devpig.be 176.31.149.32NOERROR, 16 ms, authoritativenoyes / yesrefused9.11.3-1ubuntu1.18-Ubuntu
ns2.devpig.be 51.75.151.132NOERROR, 4 ms, authoritativenoyes / yesrefused9.11.3-1ubuntu1.18-Ubuntu

Checks

  • ✓ All respond #14
    All 2 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.devpig.be: "9.11.3-1ubuntu1.18-Ubuntu"; ns2.devpig.be: "9.11.3-1ubuntu1.18-Ubuntu". Hide or replace the version string.
    #17
  • ✓ 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 1599658196 · primary ns1.devpig.be

Found

Primary (MNAME)
ns1.devpig.be
Contact (RNAME)
root.ns1.devpig.be
Serial
1599658196
Refresh / retry
3600 s / 600 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.devpig.be (176.31.149.32)1599658196
ns2.devpig.be (51.75.151.132)1599658196

Checks

  • ✓ Serial 1599658196 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 10m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.devpig.be is one of the listed nameservers.
  • ✓ Contact root@ns1.devpig.be #25
    The SOA RNAME root.ns1.devpig.be means root@ns1.devpig.be.
  • ✓ Timestamp serial #26
    The serial 1599658196 is a Unix timestamp (2020-09-09 13:29 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

pass

9 records at the apex

Found

Read from
176.31.149.32:53
TypeValueTTL
SOAns1.devpig.be. root.ns1.devpig.be. 1599658196 3600 600 1209600 36003600
NSns2.devpig.be.3600
NSns1.devpig.be.3600
A185.162.31.1973600
AAAA2a00:1c98:1000:1092:0:4:6796:77f83600
MX50 mx.backup.mailprotect.be.3600
MX10 mx.mailprotect.be.3600
TXT"v=spf1 a mx a:namurtourisme.be include:mailpig.be include:_spf.relay.mailprotect.be ~all"3600
CAA0 issuewild "letsencrypt.org"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, AAAA 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.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org.