irceline.be

Checked 22 October 2026, 06:40 UTC · via 8.8.8.8
✗Problems found
18 passed 2 warnings 3 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

dnsext.irceline.be, ns1.belnet.be, ns2.belnet.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
dnsext.irceline.be, ns1.belnet.be, ns2.belnet.be
NS in the zone
dnsext.irceline.be, ns1.belnet.be, ns2.belnet.be
NameserverAddressesNetwork (AS)Glue
dnsext.irceline.be193.190.137.132AS2611 BELNET - BELNET, BE193.190.137.132
ns1.belnet.be193.190.198.14 2001:6a8:3c80::14AS2611 BELNET - BELNET, BE AS2611 BELNET - BELNET, BE193.190.198.14 2001:6a8:3c80::14
ns2.belnet.be193.190.182.40 2001:6a8:3c80:c000::40AS2611 BELNET - BELNET, BE AS2611 BELNET - BELNET, BE193.190.182.40 2001:6a8:3c80:c000::40

Checks

  • ✓ 3 nameservers #6
    Delegated to dnsext.irceline.be, ns1.belnet.be, ns2.belnet.be.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: dnsext.irceline.be.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • i
    One address family in one network
    all IPv6 addresses are in 2001:6a8:3c80::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS2611 (BELNET - BELNET, BE): 5 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: dnsext.irceline.be.
    #13

Nameservers

fail

3 of 5 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dnsext.irceline.be 193.190.137.132NOERROR, 14 ms, authoritativenoyes / yesALLOWED (163 records)9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.14
ns1.belnet.be 193.190.198.14NOERROR, 13 ms, authoritativenoyes / yesrefusedFor me to know, for you to guess!
ns1.belnet.be 2001:6a8:3c80::14NOERROR, 18 ms, authoritativenoyes / yesrefusedFor me to know, for you to guess!
ns2.belnet.be 193.190.182.40SERVFAIL, 17 ms, NOT authoritativenono / yesrefused-
ns2.belnet.be 2001:6a8:3c80:c000::40SERVFAIL, 17 ms, NOT authoritativenono / yesrefused-

Checks

  • ✓ All respond #14
    All 5 nameserver addresses answered.
  • ✗
    Lame delegation
    These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns2.belnet.be (193.190.182.40): SERVFAIL, authoritative=false; ns2.belnet.be (2001:6a8:3c80:c000::40): SERVFAIL, authoritative=false.
    #15
  • ✓ 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: dnsext.irceline.be: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.14". Hide or replace the version string.
    #17
  • ✗
    Zone transfer allowed
    These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: dnsext.irceline.be (193.190.137.132): 163 records. Restrict zone transfers to your secondary servers.
    #18
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns2.belnet.be (193.190.182.40): ; ns2.belnet.be (2001:6a8:3c80:c000::40): .
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2022032706 · primary dnsext.irceline.be

Found

Primary (MNAME)
dnsext.irceline.be
Contact (RNAME)
root.irceline.be
Serial
2022032706
Refresh / retry
3600 s / 120 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
dnsext.irceline.be (193.190.137.132)2022032706
ns1.belnet.be (193.190.198.14)2022032706
ns1.belnet.be (2001:6a8:3c80::14)2022032706

Checks

  • ✓ Serial 2022032706 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 2m, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dnsext.irceline.be is one of the listed nameservers.
  • ✓ Contact root@irceline.be #25
    The SOA RNAME root.irceline.be means root@irceline.be.
  • ✓ Date-based serial #26
    The serial 2022032706 follows the YYYYMMDDnn convention (2022-03-27).

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
193.190.137.132:53
TypeValueTTL
SOAdnsext.irceline.be. root.irceline.be. 2022032706 3600 120 604800 8640038400
NSns2.belnet.be.38400
NSdnsext.irceline.be.38400
NSns1.belnet.be.38400
A193.190.137.15838400
MX10 mail.irceline.be.38400
TXT"google-site-verification=1E_Hx8UfiEigmjPKFMs6ygm7Far4HC5jFx2z8fjFRoY"38400
TXT"v=spf1 ip4:193.190.137.129 include:spf.flexmail.eu -all"38400
CAA128 issue "letsencrypt.org"38400

Checks

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