ibgebim.be

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

warn

ns.ibgebim.be, ns2.ibgebim.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns.ibgebim.be, ns2.ibgebim.be
NS in the zone
ns.ibgebim.be, ns2.ibgebim.be
NameserverAddressesNetwork (AS)Glue
ns.ibgebim.be195.244.180.163AS15383 UNSPECIFIED - Paradigm, BE195.244.180.163
ns2.ibgebim.be195.244.167.238AS15383 UNSPECIFIED - Paradigm, BE195.244.167.238

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.ibgebim.be, ns2.ibgebim.be.
    #6
  • ✓ 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: ns.ibgebim.be, ns2.ibgebim.be.
  • ✓ 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 (AS15383 (UNSPECIFIED - Paradigm, BE): 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

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.ibgebim.be 195.244.180.163NOERROR, 21 ms, authoritativenoyes / yesrefused-
ns2.ibgebim.be 195.244.167.238NOERROR, 24 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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 330171830 · primary ns.ibgebim.be

Found

Primary (MNAME)
ns.ibgebim.be
Contact (RNAME)
administrator.ibgebim.be
Serial
330171830
Refresh / retry
10800 s / 3600 s
Expire
2419200 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns.ibgebim.be (195.244.180.163)330171830
ns2.ibgebim.be (195.244.167.238)330171830

Checks

  • ✓ Serial 330171830 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 28d, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.ibgebim.be is one of the listed nameservers.
  • ✓ Contact administrator@ibgebim.be #25
    The SOA RNAME administrator.ibgebim.be means administrator@ibgebim.be.
  • ✓ Counter serial #26
    The serial 330171830 is a plain counter.

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

7 records at the apex

Found

Read from
195.244.180.163:53
TypeValueTTL
SOAns.ibgebim.be. administrator.ibgebim.be. 330171830 10800 3600 2419200 9003600
NSns2.ibgebim.be.3600
NSns.ibgebim.be.3600
A185.3.217.2013600
MX0 ibgebim-be.mail.protection.outlook.com.38400
TXT"MS=ms14949563"3600
TXT"v=spf1 include:spf.protection.outlook.com ip4:195.244.180.164 ip4:195.244.170.249 ip4:195.244.170.250 ip4:195.244.170.251 ip4:195.244.170.252 -all"3600

Checks

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