beabingo.be

Checked 22 October 2026, 06:10 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

nszero1.axc.nl, nszero2.axc.nl

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
nszero1.axc.nl, nszero2.axc.nl
NS in the zone
nszero1.axc.nl, nszero2.axc.nl
NameserverAddressesNetwork (AS)Glue
nszero1.axc.nl185.182.56.120 2a0b:7280:100:0:4e1:baff:fe00:20b2AS48635 CLDIN-NL - Your Hosting B.V., NL AS48635 CLDIN-NL - Your Hosting B.V., NL-
nszero2.axc.nl178.62.243.138 2a03:b0c0:2:d0::2087:c001AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: nszero1.axc.nl, nszero2.axc.nl.
    #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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US): 2 addresses; AS48635 (CLDIN-NL - Your Hosting B.V., NL): 2 addresses.
  • i
    All nameserver names under .nl
    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
nszero1.axc.nl 185.182.56.120NOERROR, 12 ms, authoritativenoyes / yesrefused-
nszero1.axc.nl 2a0b:7280:100:0:4e1:baff:fe00:20b2NOERROR, 15 ms, authoritativenoyes / yesrefused-
nszero2.axc.nl 178.62.243.138NOERROR, 17 ms, authoritativenoyes / yesrefused-
nszero2.axc.nl 2a03:b0c0:2:d0::2087:c001NOERROR, 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 2026102201 · primary nszero1.axc.nl

Found

Primary (MNAME)
nszero1.axc.nl
Contact (RNAME)
hostmaster.beabingo.be
Serial
2026102201
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
nszero1.axc.nl (185.182.56.120)2026102201
nszero1.axc.nl (2a0b:7280:100:0:4e1:baff:fe00:20b2)2026102201
nszero2.axc.nl (178.62.243.138)2026102201
nszero2.axc.nl (2a03:b0c0:2:d0::2087:c001)2026102201

Checks

  • ✓ Serial 2026102201 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver nszero1.axc.nl is one of the listed nameservers.
  • ✓ Contact hostmaster@beabingo.be #25
    The SOA RNAME hostmaster.beabingo.be means hostmaster@beabingo.be.
  • ✓ Date-based serial #26
    The serial 2026102201 follows the YYYYMMDDnn convention (2026-10-22).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
5 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
19741RSASHA256 (8)SHA256 753A6D45AF7C4447…yes

DNSKEY in the zone

Key tagRoleAlgorithm
48723ZSK (256)RSASHA256 (8)
19741KSK (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 19741 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

8 records at the apex

Found

Read from
185.182.56.120:53
TypeValueTTL
SOAnszero1.axc.nl. hostmaster.beabingo.be. 2026102201 10800 3600 604800 36003600
NSnszero1.axc.nl.3600
NSnszero2.axc.nl.3600
A79.137.74.29300
MX20 fallback.axc.eu.300
MX10 mail.beabingo.be.300
TXT"google-site-verification=nrs_-jkqCGnFvDuEV_VCQqL1MJn082zl0RZ8xdMsxTw"300
TXT"v=spf1 a mx ip4:79.137.74.29 a:spf.spamexperts.axc.nl ~all"300

Checks

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