parentia.be

Checked 22 October 2026, 07:01 UTC · via 8.8.8.8
✗Problems found
22 passed 2 warnings 1 failed 4 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

ns3.nrb.be, ns4.nrb.be, ns5.nrb.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns3.nrb.be, ns4.nrb.be, ns5.nrb.be
NS in the zone
ns3.nrb.be, ns4.nrb.be, ns5.nrb.be
NameserverAddressesNetwork (AS)Glue
ns3.nrb.be217.117.34.74 2a02:7100:0:301::100AS204013 NRB - Network Research Belgium S.A., BE AS204013 NRB - Network Research Belgium S.A., BE217.117.34.74 2a02:7100:0:301::100
ns4.nrb.be217.117.34.75 2a02:7100:0:301::101AS204013 NRB - Network Research Belgium S.A., BE AS204013 NRB - Network Research Belgium S.A., BE217.117.34.75 2a02:7100:0:301::101
ns5.nrb.be20.107.17.246 2603:1020:201:9::d4AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US20.107.17.246 2603:1020:201:9::d4

Checks

  • ✓ 3 nameservers #6
    Delegated to ns3.nrb.be, ns4.nrb.be, ns5.nrb.be.
  • ✓ 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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS204013 (NRB - Network Research Belgium S.A., BE): 4 addresses; AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 2 addresses.
  • 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

5 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.nrb.be 217.117.34.74NOERROR, 26 ms, authoritativenoyes / yesrefused-
ns3.nrb.be 2a02:7100:0:301::100NOERROR, 27 ms, authoritativenoyes / yesrefused-
ns4.nrb.be 217.117.34.75NOERROR, 27 ms, authoritativenoyes / yesrefused-
ns4.nrb.be 2a02:7100:0:301::101no responsenono / no--
ns5.nrb.be 20.107.17.246NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns5.nrb.be 2603:1020:201:9::d4NOERROR, 12 ms, authoritativenoyes / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns4.nrb.be (2a02:7100:0:301::101): read udp [2a01:4f8:1c1c:eebf::1]:34049->[2a02:7100:0:301::101]:53: i/o timeout.
    #14
  • ✓ 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

warn

serial 2021092906 · primary ns3.nrb.be

Found

Primary (MNAME)
ns3.nrb.be
Contact (RNAME)
nobody.invalid
Serial
2021092906
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns3.nrb.be (217.117.34.74)2021092906
ns3.nrb.be (2a02:7100:0:301::100)2021092906
ns4.nrb.be (217.117.34.75)2021092906
ns5.nrb.be (20.107.17.246)2021092906
ns5.nrb.be (2603:1020:201:9::d4)2021092906

Checks

  • ✓ Serial 2021092906 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns3.nrb.be is one of the listed nameservers.
  • !
    Invalid contact address
    The SOA RNAME "nobody.invalid" is not a valid mailbox (expected e.g. hostmaster.example.com).
    #25
  • ✓ Date-based serial #26
    The serial 2021092906 follows the YYYYMMDDnn convention (2021-09-29).

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
217.117.34.74:53
TypeValueTTL
SOAns3.nrb.be. nobody.invalid. 2021092906 10800 3600 1209600 360010800
NSns4.nrb.be.10800
NSns5.nrb.be.10800
NSns3.nrb.be.10800
A99.81.150.571200
MX10 parentia-be.mail.protection.outlook.com.300
TXT"MS=ms53753719"300
TXT"google-site-verification=P3Nv6aj6E56wo03qHZ4J-t0kLgUtqhrSRF2jSsnWRPU"300
TXT"v=spf1 mx ip4:193.149.241.10 ip4:193.149.241.9 a:mail.parentia.be include:spf.protection.outlook.com include:sendgrid.net ip4:108.175.18.0/24" " ip4:108.175.30.0/24 ip4:108.175.19.0/24 ip4:108.175.31.0/24 include:sv1.parentia.be include:_spf.psm.knowbe4.com -all"300
TXT"google-site-verification=ftE6XSfPdRyvdYXsgsb427n7NkyDMeywuSAAM5i_yGM"300
TXT"knowbe4-site-verification=4c8df19a81187907ed06e2f091e98b61"300
TXT"include:_spf.psm.knowbe4.com"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 20m, MX 5m, 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.
  • ✓ 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