wikeo.be

Checked 22 October 2026, 07:30 UTC · via 8.8.8.8
iAll checks passed
27 passed 0 warnings 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

dns100.ovh.net, ns100.ovh.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
dns100.ovh.net, ns100.ovh.net
NS in the zone
dns100.ovh.net, ns100.ovh.net
NameserverAddressesNetwork (AS)Glue
dns100.ovh.net5.135.250.177 2001:41d0:d00:fa00::2AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
ns100.ovh.net5.135.44.185 2001:41d0:b00:f400::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: dns100.ovh.net, ns100.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
dns100.ovh.net 5.135.250.177NOERROR, 20 ms, authoritativenoyes / yesrefused-
dns100.ovh.net 2001:41d0:d00:fa00::2NOERROR, 20 ms, authoritativenoyes / yesrefused-
ns100.ovh.net 5.135.44.185NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns100.ovh.net 2001:41d0:b00:f400::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 2092585987 · primary dns100.ovh.net

Found

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

Serial per nameserver

NameserverSerial
dns100.ovh.net (5.135.250.177)2092585987
dns100.ovh.net (2001:41d0:d00:fa00::2)2092585987
ns100.ovh.net (5.135.44.185)2092585987
ns100.ovh.net (2001:41d0:b00:f400::2)2092585987

Checks

  • ✓ Serial 2092585987 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 dns100.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 2092585987 is a Unix timestamp (2036-04-23 17:53 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
20 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
36197RSASHA256 (8)SHA256 C8C0B8A1705B8C0D…yes

DNSKEY in the zone

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

Records

info

10 records at the apex

Found

Read from
5.135.250.177:53
TypeValueTTL
SOAdns100.ovh.net. tech.ovh.net. 2092585987 86400 3600 3600000 30043200
NSdns100.ovh.net.43200
NSns100.ovh.net.43200
A51.77.221.17843200
AAAA2001:41d0:305:2100::75fa43200
MX5 smtp.wikeo.be.43200
TXT"v=spf1 include:spf.mailjet.com mx include:_spf.mailersend.net ~all"600
TXT"stripe-verification=6ed02b832440338fe82c5be607e8de23d78130bebf6a6ec1174be3bf12af6ca0"600
TXT"google-site-verification=KhT1AjyRzH7USCahUcEr5Tph34JhXeDpiXATT7LFED4"600
CAA0 issue "letsencrypt.org"43200

Checks

  • ✓ TTLs within range #32
    TTLs: A 12h, AAAA 12h, MX 12h, NS 12h. The NS TTL at the parent is 1d and in the zone 12h; 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org.