Domain report: soya.be

Registration

info

.be country-code

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

warn

ns1.bluehost.com, ns2.bluehost.com

Nameserver	Addresses	Network (AS)	Glue
ns1.bluehost.com	162.159.24.80	AS13335 CLOUDFLARENET - Cloudflare, Inc., US	-
ns2.bluehost.com	162.159.25.175	AS13335 CLOUDFLARENET - Cloudflare, Inc., US	-

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.bluehost.com, ns2.bluehost.com.

#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 0 IPv6 /48s.
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 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 .com

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

warn

2 of 2 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.bluehost.com 162.159.24.80	NOERROR, 27 ms, authoritative	no	yes / yes	refused	2026.10.8
ns2.bluehost.com 162.159.25.175	NOERROR, 42 ms, authoritative	no	yes / yes	refused	2026.10.8

✓ 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.
!

Software version disclosed

These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.bluehost.com: "2026.10.8"; ns2.bluehost.com: "2026.10.8". Hide or replace the version string.

#17
✓ 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.

pass

serial 2020111008 · primary ns1.bluehost.com

Nameserver	Serial
ns1.bluehost.com (162.159.24.80)	2020111008
ns2.bluehost.com (162.159.25.175)	2020111008

✓ Serial 2020111008 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 1d, retry 2h, expire 1000h, negative TTL 5m.
✓ Primary is a public nameserver #24

The primary nameserver ns1.bluehost.com is one of the listed nameservers.
✓ Contact root@box5135.bluehost.com #25

The SOA RNAME root.box5135.bluehost.com means root@box5135.bluehost.com.
✓ Date-based serial #26

The serial 2020111008 follows the YYYYMMDDnn convention (2020-11-10).

warn

Not signed

info

6 records at the apex

Type	Value	TTL
SOA	ns1.bluehost.com. root.box5135.bluehost.com. 2020111008 86400 7200 3600000 300	86400
NS	ns2.bluehost.com.	86400
NS	ns1.bluehost.com.	86400
A	162.241.244.115	14400
MX	0 mail.soya.be.	14400
TXT	"v=spf1 ip4:162.241.244.115 a mx include:websitewelcome.com ~all"	14400