tuna.be

Checked 22 October 2026, 07:20 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

ns1.gslb4.sakura.ne.jp, ns2.gslb4.sakura.ne.jp

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.gslb4.sakura.ne.jp, ns2.gslb4.sakura.ne.jp
NS in the zone
ns1.gslb4.sakura.ne.jp, ns2.gslb4.sakura.ne.jp
NameserverAddressesNetwork (AS)Glue
ns1.gslb4.sakura.ne.jp133.242.28.20AS7684 SAKURA-A - SAKURA Internet Inc., JP-
ns2.gslb4.sakura.ne.jp163.43.127.196AS9370 SAKURA-B - SAKURA Internet Inc., JP-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.gslb4.sakura.ne.jp, ns2.gslb4.sakura.ne.jp.
    #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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS7684 (SAKURA-A - SAKURA Internet Inc., JP): 1 address; AS9370 (SAKURA-B - SAKURA Internet Inc., JP): 1 address.
  • i
    All nameserver names under .jp
    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
ns1.gslb4.sakura.ne.jp 133.242.28.20NOERROR, 255 ms, authoritativenoyes / yesrefused-
ns2.gslb4.sakura.ne.jp 163.43.127.196NOERROR, 245 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 1 · primary ns1.gslb4.sakura.ne.jp

Found

Primary (MNAME)
ns1.gslb4.sakura.ne.jp
Contact (RNAME)
noc.sakura.ad.jp
Serial
1
Refresh / retry
3600 s / 900 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.gslb4.sakura.ne.jp (133.242.28.20)1
ns2.gslb4.sakura.ne.jp (163.43.127.196)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 15m, expire 28d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.gslb4.sakura.ne.jp is one of the listed nameservers.
  • ✓ Contact noc@sakura.ad.jp #25
    The SOA RNAME noc.sakura.ad.jp means noc@sakura.ad.jp.
  • ✓ Counter serial #26
    The serial 1 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
133.242.28.20:53
TypeValueTTL
SOAns1.gslb4.sakura.ne.jp. noc.sakura.ad.jp. 1 3600 900 2419200 3003600
NSns2.gslb4.sakura.ne.jp.259200
NSns1.gslb4.sakura.ne.jp.259200
A153.120.171.206300
MX10 tuna.be.300
TXT"v=spf1 +ip4:153.120.171.206 mx ~all"300
TXT"google-site-verification=OoraLLrB2aY7OtKGpUYtzf6A9WlKl2ZyArYCNamjOQA"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 3d. The NS TTL at the parent is 1d and in the zone 3d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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